ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltib] Problems updating kernel on MPC8377EWLAN


From: Francesco
Subject: Re: [Ltib] Problems updating kernel on MPC8377EWLAN
Date: Fri, 25 Sep 2009 16:41:28 +0200

Hi Stuart,
I did followed the guide (interpolating :) ) and I get the kernel to start compiling.
Unfortunately it exit with error complaining wrong arch: it looks for ppc instead of powerpc.
Honestly I don't know whether it is a problem of ltib or gcc...
Did anyone experienced same problem and managed to solve?

On Fri, Sep 25, 2009 at 11:30 AM, Stuart Hughes <address@hidden> wrote:
Hi Francesco,

I've attached a guide/example, you'll need to interpolate.

Regards, Stuart

Francesco wrote:
Thanks Stuart,
but where do I put new kernel source, and how do I configure ltib to work with new kernel source?

On Fri, Sep 25, 2009 at 11:12 AM, Stuart Hughes <address@hidden <mailto:address@hidden>> wrote:

   Hi Francesco,

   To re-configure the kernel:

   $ ./ltib -p kernel -c -f

   -c : configure
   -f : force (as the package is up to date).

   Regards, Stuart


--
Francesco Cappuccio


---+++ Example: adding a new kernel

Here is an example that shows the addition of a new kernel to a target.

First, here's the patch of the main.lkc file.  I've snipped it back
to remove the hunks we're not interested in:

<verbatim>
$ cvs diff -r 1.2 -r1.3 config/platform/qs875s/main.lkc
Index: config/platform/qs875s/main.lkc
===================================================================
RCS file: /sources/ltib/ltib/config/platform/qs875s/main.lkc,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- config/platform/qs875s/main.lkc     27 Feb 2007 14:43:16 -0000      1.2
+++ config/platform/qs875s/main.lkc     6 Mar 2007 17:20:39 -0000       1.3
@@ -121,6 +121,8 @@
        bool "2.4.27 (Analogue Micro Ltd)"
    config KERNEL3
        bool "2.6.16 (Analogue Micro Ltd)"
+    config KERNEL4
+        bool "kernel-8xx"
    config KERNEL_DIR_BUILD
        bool "Local Linux directory build"
        help
@@ -135,6 +137,7 @@
    string
    default "kernel-2.4.27-875"               if KERNEL1
    default "kernel-2.6.16-875"               if KERNEL3
+    default "kernel-8xx"                      if KERNEL4
    default "kernel26-dir-build"              if KERNEL_DIR_BUILD

 source ../../userspace/kernel_dir_build.lkc
@@ -153,6 +156,7 @@
    string "kernel config"
    default "linux-2.4.x-am_adder_87x.config" if KERNEL1
    default "linux-2.6.16-am_adder_87x.config" if KERNEL3 || KERNEL_DIR_BUILD
+    default "linux-8xx-am_adder_87x.config" if KERNEL4

 config PKG_KERNEL_WANT_CF
    depends ! KERNEL_NONE
</verbatim>

Here's an explanation:

  * Hunk '@@ -121,6 +121,8 @@' shows the new menu prompt under the kernel
  choice list selection "kernel-8xx"

  * Hunk '@@ -135,6 +137,7 @@' Shows that the new kernel (#4) will select
  the spec file who's base name is "kernel-8xx" as the rpm spec file
  that will be used in order to build the kernel.  It is this spec file
  that references the source tarball and patches that belong to this kernel

  * Hunk '@@ -153,6 +156,7 @@' Shows that the new kernel (#4) will select
  the new linux .config file "linux-8xx-am_adder_87x.config"

In addition to changing this main.lkc for this example I needed do the
following:

  * Create a the kernel config file (maybe based on a copy) the file:
  config/platform/qs875s/linux-8xx-am_adder_87x.config

  * Create (maybe based on a copy of another) the file:
  dist/lfs-5.1/kernel/kernel-8xx.spec.in
  NOTE: I think it's better to place the spec file in config/platform/_target_

  * Put you source tarball and patches into /opt/ltib|freescale/pkgs


---+ Testing

Run: ./ltib -m config select the new kernel and then: build: ./ltib
If you want to re-configure the kernel and build:
./ltib -p kernel -c -f





--
Francesco Cappuccio


reply via email to

[Prev in Thread] Current Thread [Next in Thread]