From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot with a custom kernel
Date: Tue, 7 Oct 2008 14:10:38 +1100 [thread overview]
Message-ID: <20081007031038.GA5127@cloud.net.au> (raw)
In-Reply-To: <1B0F60C9E236904CB364F9EF52E0AFD9026139CB@sma10.technidata-ag.com>
On Tue, Sep 23, 2008 at 07:57:05PM +0200, Bussmann, Paul wrote:
> > 2) tarball up your custom kernel and place it in the dl dir. Make
> > sure you name is according to what you have in your buildroot config
> > for the kernel version. BR will then assume you've already dl'ed the
> > kernel and use your version.
>
> I already tried this with 2.6.17 on ARM. Resulting in everything _looked_ fine at first but my board instantly rebooted when I tried to use TCP stuff. It is indeed related to BR's toolchain, because if I use the manufacture's (Ka-Ro) toolchain to compile the kernel, it works.
> So I asked on this mailing list about getting a 2.6.17-supporting Buildroot environment (2008-08-25) with the following answer (2008-08-26):
>
> > 2.6.17 was released around Jun 18 2006. I'd ask those people for a
> > vaguely recent kernel.
>
> So I'd be very interested if you have similar success.
>
> See http://www.nabble.com/Linux-Kernel-2.6.17-support-in-Buildroot-tt19139626.html#a19139626
I had 2.6.15 running with a buildroot-compiled gcc 4.1.2 without issue.
I have my own customised kernel with the whole source checked in (not a
tarball). I can probably share the makefiles later this week, or add
some support to buildroot for it. It's a bit messy as the kernel's
support for out-of-tree builds is a bit weird.
I'm now using a much more recent kernel, but we have various changes and I'd
rather not just maintain them as a set of patches (too tedious).
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2008-10-07 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 15:56 [Buildroot] Buildroot with a custom kernel Alex Rades
2008-09-23 17:29 ` Christopher Taylor
2008-09-23 17:57 ` Bussmann, Paul
2008-09-24 12:25 ` Alex Rades
2008-09-24 14:34 ` Christopher Taylor
2008-10-07 3:10 ` Hamish Moffatt [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=20081007031038.GA5127@cloud.net.au \
--to=hamish@cloud.net.au \
--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.