All of lore.kernel.org
 help / color / mirror / Atom feed
From: W.P. <laurentp@wp.pl>
To: buildroot@busybox.net
Subject: [Buildroot] [OT?] Re: Applying custom kernel patches
Date: Sat, 05 Mar 2011 00:21:03 +0100	[thread overview]
Message-ID: <4D7173DF.6060407@wp.pl> (raw)
In-Reply-To: <AANLkTikET+tnALmPDw67_17SsJpuOOFDarCKm7tWOGEE@mail.gmail.com>

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
>>
>>     
>
>   

  reply	other threads:[~2011-03-04 23:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 21:15 [Buildroot] Applying custom kernel patches bruce bushby
2011-03-04 21:52 ` ANDY KENNEDY
2011-03-04 22:06   ` bruce bushby
2011-03-04 22:13     ` ANDY KENNEDY
2011-03-07 13:43       ` Thomas Petazzoni
2011-03-04 22:21 ` Steve Calfee
2011-03-04 22:39   ` [Buildroot] [OT?] " W.P.
2011-03-04 22:45     ` ANDY KENNEDY
2011-03-04 22:59       ` Yann E. MORIN
2011-03-04 23:19         ` bruce bushby
2011-03-04 23:02       ` bruce bushby
2011-03-04 23:21         ` W.P. [this message]
2011-03-04 22:56     ` Steve Calfee
2011-03-07 13:50       ` Thomas Petazzoni
2011-03-07 21:46         ` Steve Calfee
2011-03-07 13:48 ` [Buildroot] " Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D7173DF.6060407@wp.pl \
    --to=laurentp@wp.pl \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.