Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Applying custom kernel patches
Date: Mon, 7 Mar 2011 14:48:17 +0100	[thread overview]
Message-ID: <20110307144817.216eeec3@surf> (raw)
In-Reply-To: <AANLkTi=_dHFneTLXe3+P1-cOM2dsLsQW6f_fgbK7hSQy@mail.gmail.com>

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

      parent reply	other threads:[~2011-03-07 13:48 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.
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 ` Thomas Petazzoni [this message]

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=20110307144817.216eeec3@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox