topic "Custom" kernel HOWTO anywhere? in i.MX Processors

"Custom" kernel HOWTO anywhere?

Don_ng — Thu, 22 Sep 2011 15:48:58 GMT

Running into a problem that I cannot find a solution too.

Starting with the IMX25PDK source as a jumping off point. I can build the "stock" kernel, utils etc just fine. However I am needing to add files to the kernel for our custom board we are developing. When I rebuild the kernel with the new files, LTIB deletes the linux-2.6.31 directory and decompresses the original kernel - hence wiping out our custom board files(source). I tried adding the command line option "--leavesrc" but it appears to have no effect. It always wipes out the linux kernel source.

I'm contemplating using the "custom" kernel feature but the LTIB documentation is kinda sparse on how to do this.

I did find this thread :

http://lists.gnu.org/archive/html/ltib/2010-05/msg00014.html

but it didn't help...our custom files keep getting deleted.

I also found this :

http://www.bitshrine.org/autodocs/LtibFaq.html#ref_24

I'm investigating this attempt, but if anyone has any advice/links, etc, it would be MUCH appreciated.

Re: "Custom" kernel HOWTO anywhere?

daiane_angolini — Fri, 23 Sep 2011 14:12:43 GMT

should be a way to fix LTIB, but I don´t know it know.

YOu can copy your kernel source code to somewhere else:

cp <ltib>/rpm/BUILD/linux /home/me/my_kernel

and configure LTIB to use your new location:

./ltib -c

---Choose your Kernel

( /home/me/my_kernel ) Local Linux directory build

Re: "Custom" kernel HOWTO anywhere?

Don_ng — Fri, 23 Sep 2011 14:18:41 GMT

Thanks Daiane -- I'm looking into that.

I'm looking into the route of running ltib to build all the package, build the kernel (stock), THEN add my files and then do a "ltib -m scbuild -p kernel". That way I can (re)configure the kernel, and build it without it wiping all my changes out.

Our pinout is still fluctuating, and we may need to add or remove ports (like I2C, SPI) and I don't want to have to keep copying my changes in every time we have a very minor kernel tweek.

Daiane Angolini said:

should be a way to fix LTIB, but I don´t know it know.

YOu can copy your kernel source code to somewhere else:
cp <ltib>/rpm/BUILD/linux /home/me/my_kernel

and configure LTIB to use your new location:

./ltib -c

---Choose your Kernel
( /home/me/my_kernel ) Local Linux directory build