From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [OT?] Re: Applying custom kernel patches
Date: Mon, 7 Mar 2011 14:50:14 +0100 [thread overview]
Message-ID: <20110307145014.6fb32bec@surf> (raw)
In-Reply-To: <100123.65141.qm@web161814.mail.bf1.yahoo.com>
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
next prev parent reply other threads:[~2011-03-07 13:50 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 [this message]
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=20110307145014.6fb32bec@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