From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Linux Kernel 2.6.17 support in Buildroot
Date: Tue, 26 Aug 2008 15:15:47 +0200 [thread overview]
Message-ID: <20080826131547.GI2213@mx.loc> (raw)
In-Reply-To: <1B0F60C9E236904CB364F9EF52E0AFD90241B20E@sma10.technidata-ag.com>
Hi Paul,
On Mon, Aug 25, 2008 at 10:01:18AM +0200, Bussmann, Paul wrote:
>Unfortunately, the current Linux Kernel does not support the Board and
>adding support to it is much too difficult to me.
2.6.17 was released around Jun 18 2006. I'd ask those people for a
vaguely recent kernel.
>I was glad about the feature that a custom Kernel is selectable in the
>Buildroot project configuration.
>Concerning the Toolchain settings, it seems to be not possible to select
>a custom version or version 2.6.17.
>
>How can I test if Buildroot would create a correct Toolchain using Linux
>2.6.17 instead of 2.6.26?
LTP comes to mind.
HTH,
prev parent reply other threads:[~2008-08-26 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 8:01 [Buildroot] Linux Kernel 2.6.17 support in Buildroot Bussmann, Paul
2008-08-26 13:15 ` Bernhard Reutner-Fischer [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=20080826131547.GI2213@mx.loc \
--to=rep.dot.nop@gmail.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