From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using a different kernel tree ?
Date: Fri, 28 Mar 2008 13:33:33 +0100 [thread overview]
Message-ID: <021301c890d9$3bc5c960$dcc4af0a@atmel.com> (raw)
In-Reply-To: 20080327120639.GD13379@mx.loc
> On Thu, Mar 27, 2008 at 10:52:22AM +0100, Guillaume Dargaud wrote:
>>Hello all,
>>I'd like to use, within buildroot, the kernel tree from
>>git://git.xilinx.com/linux-2.6-xlnx.git instead of the vanilla tree coming
>>with buildroot.
>>
>>How does one do that ?
>
> The easiest approach would be to git clone that kernel and
> tar -cjf dl/linux-2.6.24.4.tar.bz2 linux-2.6-xlnx.git
> (--exclude='.git' if you don't want to write patches against it) and use
> that.
>
>>If I just replace toolchain_build_ppc/linux-2.6.24 and/or
>>project_build_ppc/my_project/linux-2.6.24 with the Xilinx tree, on the next
>>"make ARCH=ppc linux26-menuconfig" it just deletes the whole directory and
>>rebuilds it from bzcat...
>>
>>Or are there alternatives if I want to use the nice toolchain built by
>>buildroot ?
>>
>>
>>BTW, what is the difference between toolchain_build_ppc/linux-2.6.24 and
>>project_build_ppc/my_project/linux-2.6.24 ?
>
The toolchain headers is generated from toolchain_build_ppc/linux-2.6.24
and the project related source tree is used for building the kernel image(s).
You can build multiple kernels for the same chip, or one kernel for
multiple chips, or combinations of above.
The following would be possible:
toolchain_build_ppc/linux-2.6.24
project_build_ppc/my_project_24__/linux-2.6.24
project_build_ppc/my_project_24_1/linux-2.6.24.1
project_build_ppc/my_project_24_2/linux-2.6.24.2
project_build_ppc/my_project_24_3/linux-2.6.24.3
This allows you to apply different patchsets for different builds.
Any package built in build_ppc/<package> have to use the same configuration
for all projects. If you need to configure them differently, then
the package needs to be built in project_build_dir/<package>.
> No, previously we only had one source-tree, but Ulf changed that for
> reasons that i do not remember offhand (conflicting patches, i.e. broken
> patches, IIRC).
> _______________________________________________
Best Regards
Ulf Samuelsson
prev parent reply other threads:[~2008-03-28 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 9:52 [Buildroot] Using a different kernel tree ? Guillaume Dargaud
2008-03-27 12:06 ` Bernhard Fischer
2008-03-28 12:33 ` Ulf Samuelsson [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='021301c890d9$3bc5c960$dcc4af0a@atmel.com' \
--to=ulf.samuelsson@atmel.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