From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Using a different kernel tree ?
Date: Thu, 27 Mar 2008 10:52:22 +0100 [thread overview]
Message-ID: <057401c88ff0$46259410$ad289e86@LPSC0173W> (raw)
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 ?
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 ?
--
Guillaume Dargaud
http://www.gdargaud.net/
"It's a little-known fact that the Y1K problem caused the Dark Ages."
next reply other threads:[~2008-03-27 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 9:52 Guillaume Dargaud [this message]
2008-03-27 12:06 ` [Buildroot] Using a different kernel tree ? Bernhard Fischer
2008-03-28 12:33 ` Ulf Samuelsson
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='057401c88ff0$46259410$ad289e86@LPSC0173W' \
--to=dargaud@lpsc.in2p3.fr \
--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