[Buildroot] Applying custom kernel patches

[Buildroot] Applying custom kernel patches

[bruce bushby]

Hi

I'm having some trouble applying kernel patches.

I manually copied the kernel tar ball
into: /opt/buildroot/dl/linux-2.6.38-rc5.tar.bz2 and using "make menuconfig"
I specified the kernel version


.....however I'm having some problems applying my patches. Everything
compiles 100% if I patch "/opt/buildroot/output/toolchain/linux-2.6.38-rc5",
however I would
like it to apply my patches after extracting the tar ball from
"/opt/buildroot/dl/linux-2.6.38-rc5.tar.bz2" when I run "make"

I've tried placing my patches in:
/opt/buildroot/linux/kernel-patches/0001-linux-2.6.38-rc5.patch

I also tried putting them in
/opt/buildroot/package/linux/kernel-patches/0001-linux-2.6.38-rc5.patch

Using "make menuconfig" under specified custom patches I added:
linux/kernel-patches/0001-linux-2.6.38-rc5.patch

...but it won't apply the patch.

Any ideas?


Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110304/e872e8c9/attachment.html>

[Buildroot] Applying custom kernel patches

[ANDY KENNEDY]

> if I patch "/opt/buildroot/output/toolchain/linux-2.6.38-rc5"

that is the Linux-headers directory.  The _kernel_ gets compiled
under buildroot/output/build/linux-$(LINUX_VERSION).

So, are you having problems building the kernel-headers or the
kernel?

Andy

[Buildroot] Applying custom kernel patches

[bruce bushby]

Hi Andy

I'm attempting to do a full build (uImage and rootfs)

I've got 6 kernel patches which I need to apply before running the "full
build", they add "board support" for my module and various other "nand"
related bits. One of the patches adds
"arch/arm/configs/telit_ge863_defconfig"









On Fri, Mar 4, 2011 at 9:52 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com>wrote:

> > if I patch "/opt/buildroot/output/toolchain/linux-2.6.38-rc5"
>
> that is the Linux-headers directory.  The _kernel_ gets compiled
> under buildroot/output/build/linux-$(LINUX_VERSION).
>
> So, are you having problems building the kernel-headers or the
> kernel?
>
> Andy
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110304/190bdb25/attachment.html>

[Buildroot] Applying custom kernel patches

[ANDY KENNEDY]

> Hi Andy
> 
> I'm attempting to do a full build (uImage and rootfs)?
> 
> I've got 6 kernel patches which I need to apply before running the
> "full build", they add "board support" for my module and various other
> "nand" related bits. One of the patches adds
> "arch/arm/configs/telit_ge863_defconfig"?
> 

<list rules>  Plain Text (wrap at 72 chars), bottom post.  </list rules>

You should create a directory OUTSIDE the scope of the BuildRoot dirs
for your patches.  It didn't occur to me until I went looking for 
something else just now that buildroot/linux is a known directory.
Your patches could exist in buildroot/mylinux if you wanted, but you
shouldn't put stuff into dirs that BuildRoot knows.

So, you'll put your patches in mylinux then config the kernel patches
to the unqualified path starting in buildroot (or you could do something
along the lines of $(TOPDIR)/mylinux to be more BuildRoot friendly ;).

Andy

[Buildroot] Applying custom kernel patches

[Steve Calfee]

>From: bruce bushby <bruce.bushby@gmail.com>

>I've tried placing my patches in:
>/opt/buildroot/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
>
>
>I also tried putting them in
>/opt/buildroot/package/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
>
Hi,

You may have a path problem for your patches. The path should be given in your 
*_defconfig. 


And buildroot will automatically apply patches at the appropriate time if they 
are named in the form linux*patch. See the makefile.

so 0001-linux-2.6.38-rc5.patch should be linux-001-2.6.38-rc5.patch

Regards, Steve



      

[Buildroot] [OT?] Re: Applying custom kernel patches

[W.P.]

U?ytkownik Steve Calfee napisa?:
>> From: bruce bushby <bruce.bushby@gmail.com>
>>     
>
>   
>> I've tried placing my patches in:
>> /opt/buildroot/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
>>
>>
>> I also tried putting them in
>> /opt/buildroot/package/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
>>
>>     
> Hi,
>
> You may have a path problem for your patches. The path should be given in your 
> *_defconfig. 
>
>
> And buildroot will automatically apply patches at the appropriate time if they 
> are named in the form linux*patch. See the makefile.
>
> so 0001-linux-2.6.38-rc5.patch should be linux-001-2.6.38-rc5.patch
>
> Regards, Steve
>
>   
Could someone write a HOWTO?
I mean:
step 0): "I have kernel.xxx.yy.zzz directory unpacked AND a set of
patches (that applies correctly from kernel root) patch.00xx.patch"
step 1): where should I put (link?) kernel source?,
step 2): where should I put patches?.
step 3): how do I inform buildroot about patches?

W.P.
>
>       
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>   

[Buildroot] [OT?] Re: Applying custom kernel patches

[ANDY KENNEDY]

> Could someone write a HOWTO?
> I mean:
> step 0): "I have kernel.xxx.yy.zzz directory unpacked AND a set of
> patches (that applies correctly from kernel root) patch.00xx.patch"
> step 1): where should I put (link?) kernel source?,
> step 2): where should I put patches?.
> step 3): how do I inform buildroot about patches?

It isn't that "dumbed down" but how about:

buildroot/docs/patches.html  <Linux kernel section>?

Andy

[Buildroot] [OT?] Re: Applying custom kernel patches

[Steve Calfee]

----- Original Message ----

> From: W.P. <laurentp@wp.pl>
> To: buildroot at uclibc.org
> Sent: Fri, March 4, 2011 2:39:19 PM
> Subject: [Buildroot] [OT?] Re:  Applying custom kernel patches
> 
> U?ytkownik Steve Calfee napisa?:
> >> From: bruce bushby <bruce.bushby@gmail.com>
> >>     
> >
> >  
> >> I've tried placing my patches  in:
> >>  /opt/buildroot/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
> >>
> >>
> >>  I also tried putting them in
> >>  /opt/buildroot/package/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
> >>
> >>     
> > Hi,
> >
> > You may have a path problem for your  patches. The path should be given in 
>your 
>
> > *_defconfig. 
> >
> >
> > And buildroot will automatically apply patches at the  appropriate time if 
>they 
>
> > are named in the form linux*patch. See the  makefile.
> >
> > so 0001-linux-2.6.38-rc5.patch should be  linux-001-2.6.38-rc5.patch
> >
> > Regards, Steve
> >
> >  
> Could someone write a HOWTO?
> I mean:
> step 0): "I have  kernel.xxx.yy.zzz directory unpacked AND a set of
> patches (that applies  correctly from kernel root) patch.00xx.patch"
> step 1): where should I put  (link?) kernel source?,
> step 2): where should I put patches?.
> step 3): how  do I inform buildroot about patches?
> 
> W.P.

Hi W.P.
Yes, Docs are always nice. For now though from my boards defconfig:

#
# Kernel
#
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_2_6_36=y
# BR2_LINUX_KERNEL_CUSTOM_VERSION is not set
# BR2_LINUX_KERNEL_CUSTOM_TARBALL is not set
BR2_LINUX_KERNEL_VERSION="2.6.36.1"
BR2_LINUX_KERNEL_PATCH="$(TOPDIR)/target/device/beagleboard/kernel-patches/"
# BR2_LINUX_KERNEL_USE_DEFCONFIG is not set
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(TOPDIR)/target/device/beagleboard/beagleboard-linux-2.6.36.1.config"

BR2_LINUX_KERNEL_UIMAGE=y
# BR2_LINUX_KERNEL_ZIMAGE is not set

and the files I have put in target/device:


~/buildroot/bbkernel/target/device$ tree beagleboard/
beagleboard/
|-- Config.in
|-- Makefile.in
|-- README
|-- beagleboard-busybox-1.17.x.config
|-- beagleboard-linux-2.6.36.1.config
|-- beagleboard_defconfig
|-- beagleboard_external_toolchain_defconfig
|-- dropbear
|   |-- dropbear_dss_host_key
|   `-- dropbear_rsa_host_key
|-- kernel-patches
|   `-- linux-kernel-2.6.36-bb-xm-usb-pwr.patch
|-- patchrootfs.sh
|-- shadow
`-- skeleton
    `-- etc
        |-- dropbear
        |   |-- dropbear_dss_host_key
        |   `-- dropbear_rsa_host_key
        |-- network
        |   `-- interfaces
        `-- shadow

6 directories, 16 files


You can put these kinds of files anywhere, but it seems to be the natural home 
for board support packages.

Regards, Steve


      

[Buildroot] [OT?] Re: Applying custom kernel patches

[Yann E. MORIN]

All,

On Friday 04 March 2011 23:45:07 ANDY KENNEDY wrote:
> > Could someone write a HOWTO?
> > I mean:
> > step 0): "I have kernel.xxx.yy.zzz directory unpacked AND a set of
> > patches (that applies correctly from kernel root) patch.00xx.patch"
> > step 1): where should I put (link?) kernel source?,
> > step 2): where should I put patches?.
> > step 3): how do I inform buildroot about patches?
> 
> It isn't that "dumbed down" but how about:
> buildroot/docs/patches.html  <Linux kernel section>?

Not sure it will answer the question, but what about:
  http://buildroot.org/downloads/buildroot.html#board_support

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] [OT?] Re: Applying custom kernel patches

[bruce bushby]

I think I've got it working....doing a full build now.

This is what I did:

1. mkdir /opt/buildroot/linux/kernel-patches

2. name patches in the order that you want them applied, for example:
root at prodvarm:/opt/buildroot/linux/kernel-patches# ls -1
linux-2.6.38-rc5-0001.patch
linux-2.6.38-rc5-0002.patch
linux-2.6.38-rc5-0003.patch
linux-2.6.38-rc5-0004.patch
linux-2.6.38-rc5-0005.patch
linux-2.6.38-rc5-0006.patch

3. Create a list of patches to paste into the "Custom patches" option when
running "make menuconfig":
root at prodvarm:/opt/buildroot# find linux/kernel-patches/ | grep "\.patch" |
sort -n | xargs
linux/kernel-patches/linux-2.6.38-rc5-0001.patch
linux/kernel-patches/linux-2.6.38-rc5-0002.patch
linux/kernel-patches/linux-2.6.38-rc5-0003.patch
linux/kernel-patches/linux-2.6.38-rc5-0004.patch
linux/kernel-patches/linux-2.6.38-rc5-0005.patch
linux/kernel-patches/linux-2.6.38-rc5-0006.patch
root at prodvarm:/opt/buildroot#

4. run "make menuconfig", then go to kernel/custom patches option and paste
the "patch list" like so:
linux/kernel-patches/linux-2.6.38-rc5-0001.patch
linux/kernel-patches/linux-2.6.38-rc5-0002.patch
linux/kernel-patches/linux-2.6.38-rc5-0003.patch
linux/kernel-patches/linux-2.6.38-rc5-0004.patch
linux/kernel-patches/linux-2.6.38-rc5-0005.patch
linux/kernel-patches/linux-2.6.38-rc5-0006.patch

5. Make sure previous kernel bits have been removed:
rm -rf  output/toolchain/linux-2.6.38-rc5 ; rm
-rf output/build/linux-2.6.38-rc5

6. "make"


After a while you'll see it extracting the kernel and then applying the
patches....although I've not tried to boot the resulting uImage yet....but
my boards ".._defconfig" was there and the build appeared to go through.


Thanks for the help!!!



On Fri, Mar 4, 2011 at 10:45 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com>wrote:

> > Could someone write a HOWTO?
> > I mean:
> > step 0): "I have kernel.xxx.yy.zzz directory unpacked AND a set of
> > patches (that applies correctly from kernel root) patch.00xx.patch"
> > step 1): where should I put (link?) kernel source?,
> > step 2): where should I put patches?.
> > step 3): how do I inform buildroot about patches?
>
> It isn't that "dumbed down" but how about:
>
> buildroot/docs/patches.html  <Linux kernel section>?
>
> Andy
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110304/9496d28d/attachment.html>

[Buildroot] [OT?] Re: Applying custom kernel patches

[bruce bushby]

I'm new to buildroot so probably don't understand it all yet.

From my perspective, my board is not supported, so my patches are more then
adding a "defconfig"

Perhaps: /opt/buildroot/linux/kernel-patches/<kernel
version>/<number-ordered-patch-details.patch>

would be easier then pasting patches into "make menuconfig"




On Fri, Mar 4, 2011 at 10:59 PM, Yann E. MORIN <
yann.morin.1998@anciens.enib.fr> wrote:

> All,
>
> On Friday 04 March 2011 23:45:07 ANDY KENNEDY wrote:
> > > Could someone write a HOWTO?
> > > I mean:
> > > step 0): "I have kernel.xxx.yy.zzz directory unpacked AND a set of
> > > patches (that applies correctly from kernel root) patch.00xx.patch"
> > > step 1): where should I put (link?) kernel source?,
> > > step 2): where should I put patches?.
> > > step 3): how do I inform buildroot about patches?
> >
> > It isn't that "dumbed down" but how about:
> > buildroot/docs/patches.html  <Linux kernel section>?
>
> Not sure it will answer the question, but what about:
>  http://buildroot.org/downloads/buildroot.html#board_support
>
> Regards,
> Yann E. MORIN.
>
> --
>
> .-----------------.--------------------.------------------.--------------------.
> |  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics'
> conspiracy: |
> | +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___
>     |
> | +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is
> no  |
> | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v
> conspiracy.  |
>
> '------------------------------^-------^------------------^--------------------'
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20110304/b52558ce/attachment-0001.html>

[Buildroot] [OT?] Re: Applying custom kernel patches

[W.P.]

U?ytkownik bruce bushby napisa?:
> I think I've got it working....doing a full build now.
>
> This is what I did:
>
> 1. mkdir /opt/buildroot/linux/kernel-patches
>
> 2. name patches in the order that you want them applied, for example:
> root at prodvarm:/opt/buildroot/linux/kernel-patches# ls -1
> linux-2.6.38-rc5-0001.patch
> linux-2.6.38-rc5-0002.patch
> linux-2.6.38-rc5-0003.patch
> linux-2.6.38-rc5-0004.patch
> linux-2.6.38-rc5-0005.patch
> linux-2.6.38-rc5-0006.patch
>
> 3. Create a list of patches to paste into the "Custom patches" option when
> running "make menuconfig":
> root at prodvarm:/opt/buildroot# find linux/kernel-patches/ | grep "\.patch" |
> sort -n | xargs
> linux/kernel-patches/linux-2.6.38-rc5-0001.patch
> linux/kernel-patches/linux-2.6.38-rc5-0002.patch
> linux/kernel-patches/linux-2.6.38-rc5-0003.patch
> linux/kernel-patches/linux-2.6.38-rc5-0004.patch
> linux/kernel-patches/linux-2.6.38-rc5-0005.patch
> linux/kernel-patches/linux-2.6.38-rc5-0006.patch
> root at prodvarm:/opt/buildroot#
>
> 4. run "make menuconfig", then go to kernel/custom patches option and paste
> the "patch list" like so:
> linux/kernel-patches/linux-2.6.38-rc5-0001.patch
> linux/kernel-patches/linux-2.6.38-rc5-0002.patch
> linux/kernel-patches/linux-2.6.38-rc5-0003.patch
> linux/kernel-patches/linux-2.6.38-rc5-0004.patch
> linux/kernel-patches/linux-2.6.38-rc5-0005.patch
> linux/kernel-patches/linux-2.6.38-rc5-0006.patch
>
> 5. Make sure previous kernel bits have been removed:
> rm -rf  output/toolchain/linux-2.6.38-rc5 ; rm
> -rf output/build/linux-2.6.38-rc5
>
> 6. "make"
>
>
> After a while you'll see it extracting the kernel and then applying the
> patches....although I've not tried to boot the resulting uImage yet....but
> my boards ".._defconfig" was there and the build appeared to go through.
>
>
> Thanks for the help!!!
>
>
>   
This (for me) definitely indicates need of some HOWTO:
I find myself experienced Linux user/admen (but not a programmer), and
*.patch is still a mystery for me :(

W.P.
> On Fri, Mar 4, 2011 at 10:45 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com>wrote:
>
>   
>>> Could someone write a HOWTO?
>>> I mean:
>>> step 0): "I have kernel.xxx.yy.zzz directory unpacked AND a set of
>>> patches (that applies correctly from kernel root) patch.00xx.patch"
>>> step 1): where should I put (link?) kernel source?,
>>> step 2): where should I put patches?.
>>> step 3): how do I inform buildroot about patches?
>>>       
>> It isn't that "dumbed down" but how about:
>>
>> buildroot/docs/patches.html  <Linux kernel section>?
>>
>> Andy
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>>     
>
>   

[Buildroot] Applying custom kernel patches

[Thomas Petazzoni]

On Fri, 4 Mar 2011 16:13:42 -0600
ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:

> You should create a directory OUTSIDE the scope of the BuildRoot dirs
> for your patches.

Not necessarly. When I have board/project specific patches, I just put
them into :

	board/<manufacturer>/<boardname>/

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Applying custom kernel patches

[Thomas Petazzoni]

Hello Bruce,

On Fri, 4 Mar 2011 21:15:30 +0000
bruce bushby <bruce.bushby@gmail.com> wrote:

> .....however I'm having some problems applying my patches. Everything
> compiles 100% if I patch "/opt/buildroot/output/toolchain/linux-2.6.38-rc5",
> however I would
> like it to apply my patches after extracting the tar ball from
> "/opt/buildroot/dl/linux-2.6.38-rc5.tar.bz2" when I run "make"
> 
> I've tried placing my patches in:
> /opt/buildroot/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
> 
> I also tried putting them in
> /opt/buildroot/package/linux/kernel-patches/0001-linux-2.6.38-rc5.patch
> 
> Using "make menuconfig" under specified custom patches I added:
> linux/kernel-patches/0001-linux-2.6.38-rc5.patch
> 
> ...but it won't apply the patch.
> 
> Any ideas?

Do the following :

	mkdir board/bruce_company/bruce_product/linux
	cp ALL_YOUR_PATCHES board/bruce_company/bruce_product/linux

All patches must have filenames that start with "linux-".

Then, run make menuconfig, and use the following options :

	Kernel
		-> Linux Kernel
			-> Kernel version (Custom version)
			-> (2.6.XX) Kernel version
			-> (board/bruce_company/bruce_product/linux) Custom kernel patches

Of course, make sure your patches match the selected kernel version.

Then, in order to save your configuration and make it a default :

	make savedefconfig
	mv defconfig configs/bruce_product_defconfig

Now, you can build Buildroot with:

	make bruce_product_defconfig
	make

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] [OT?] Re: Applying custom kernel patches

[Thomas Petazzoni]

Hello Steeve,

On Fri, 4 Mar 2011 14:56:28 -0800 (PST)
Steve Calfee <nospamcalfee@yahoo.com> wrote:

> Yes, Docs are always nice. For now though from my boards defconfig:
> 
> #
> # Kernel
> #
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_2_6_36=y
> # BR2_LINUX_KERNEL_CUSTOM_VERSION is not set
> # BR2_LINUX_KERNEL_CUSTOM_TARBALL is not set
> BR2_LINUX_KERNEL_VERSION="2.6.36.1"
> BR2_LINUX_KERNEL_PATCH="$(TOPDIR)/target/device/beagleboard/kernel-patches/"
> # BR2_LINUX_KERNEL_USE_DEFCONFIG is not set
> BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(TOPDIR)/target/device/beagleboard/beagleboard-linux-2.6.36.1.config"
> 
> BR2_LINUX_KERNEL_UIMAGE=y
> # BR2_LINUX_KERNEL_ZIMAGE is not set
> 
> and the files I have put in target/device:
> 
> 
> ~/buildroot/bbkernel/target/device$ tree beagleboard/
> beagleboard/
> |-- Config.in
> |-- Makefile.in
> |-- README
> |-- beagleboard-busybox-1.17.x.config
> |-- beagleboard-linux-2.6.36.1.config
> |-- beagleboard_defconfig
> |-- beagleboard_external_toolchain_defconfig
> |-- dropbear
> |   |-- dropbear_dss_host_key
> |   `-- dropbear_rsa_host_key
> |-- kernel-patches
> |   `-- linux-kernel-2.6.36-bb-xm-usb-pwr.patch
> |-- patchrootfs.sh
> |-- shadow
> `-- skeleton
>     `-- etc
>         |-- dropbear
>         |   |-- dropbear_dss_host_key
>         |   `-- dropbear_rsa_host_key
>         |-- network
>         |   `-- interfaces
>         `-- shadow
> 
> 6 directories, 16 files

This is a good organisation, even though in a recent Buildroot
(2011.02), the board-specific stuff would rather go into
board/<manufacturer>/<product>, and there would be no
board-specific Config.in and Makefile.in. The rest would look essential
the same.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] [OT?] Re: Applying custom kernel patches

[Steve Calfee]

----- Original Message ----

> From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> To: buildroot at busybox.net
> Sent: Mon, March 7, 2011 5:50:14 AM
> Subject: Re: [Buildroot] [OT?] Re:  Applying custom kernel patches
> 
> Hello Steeve,
> 
> On Fri, 4 Mar 2011 14:56:28 -0800 (PST)
> Steve Calfee  <nospamcalfee@yahoo.com>  wrote:
> 
> > Yes, Docs are always nice. For now though from my boards  defconfig:
> > 
> > #
> > # Kernel
> > #
> >  BR2_LINUX_KERNEL=y
> > BR2_LINUX_KERNEL_2_6_36=y
> > #  BR2_LINUX_KERNEL_CUSTOM_VERSION is not set
> > #  BR2_LINUX_KERNEL_CUSTOM_TARBALL is not set
> >  BR2_LINUX_KERNEL_VERSION="2.6.36.1"
> >  
BR2_LINUX_KERNEL_PATCH="$(TOPDIR)/target/device/beagleboard/kernel-patches/"
> >  # BR2_LINUX_KERNEL_USE_DEFCONFIG is not set
> >  BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> >  
>BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(TOPDIR)/target/device/beagleboard/beagleboard-linux-2.6.36.1.config"
>
> > 
> > BR2_LINUX_KERNEL_UIMAGE=y
> > # BR2_LINUX_KERNEL_ZIMAGE is not  set
> > 
> > and the files I have put in target/device:
> > 
> > 
> > ~/buildroot/bbkernel/target/device$ tree beagleboard/
> >  beagleboard/
> > |-- Config.in
> > |-- Makefile.in
> > |-- README
> > |--  beagleboard-busybox-1.17.x.config
> > |--  beagleboard-linux-2.6.36.1.config
> > |-- beagleboard_defconfig
> > |--  beagleboard_external_toolchain_defconfig
> > |-- dropbear
> > |    |-- dropbear_dss_host_key
> > |   `-- dropbear_rsa_host_key
> > |--  kernel-patches
> > |   `--  linux-kernel-2.6.36-bb-xm-usb-pwr.patch
> > |-- patchrootfs.sh
> > |-- shadow
> > `--  skeleton
> >     `-- etc
> >         |--  dropbear
> >         |   |--  dropbear_dss_host_key
> >         |   `--  dropbear_rsa_host_key
> >         |--  network
> >         |   `--  interfaces
> >         `-- shadow
> > 
> > 6  directories, 16 files
> 
> This is a good organisation, even though in a  recent Buildroot
> (2011.02), the board-specific stuff would rather go  into
> board/<manufacturer>/<product>, and there would be  no
> board-specific Config.in and Makefile.in. The rest would look  essential
> the same.
> 

Hi Thomas,

Looking at those two files, I guess Makefile.in could be replace with more 
BR2_defines, but how do you replace a custom config system? I like to understand 
"the plan" and I will try to comply with the design.

Regards, Steve