From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to change kernel version
Date: Sun, 19 Aug 2007 14:47:35 +0200 [thread overview]
Message-ID: <001201c7e291$2b8f5ee0$dcc4af0a@atmel.com> (raw)
In-Reply-To: d6cda7730708181940u51f1e3d6ya6e701104d6dc5c7@mail.gmail.com
----- Original Message -----
From: "Thiago A. Corr?a" <thiago.correa@gmail.com>
To: <buildroot@uclibc.org>
Sent: Sunday, August 19, 2007 4:40 AM
Subject: [Buildroot] How to change kernel version
> Hi,
>
> I searched over the archives but I couldn't find anything about how
> one could change the kernel version. The only available option for
> AVR32, 2.6.22, is unable to boot on an STK1000 due to a bug in the MMC
> drivers, so I would like to change it to 2.6.18 which actually works.
>
> Kind Regards,
> Thiago A. Correa
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
That is simple, you can't do it within buildroot!!!
I am working on a patch to allow users to use any kernel version
But that will require the kernel to be 2.6.19 minimum.
The best option is to build it outside buildroot and just
create a path to the tools in $(STAGING_DIR)
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-08-19 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 2:40 [Buildroot] How to change kernel version Thiago A. Corrêa
2007-08-19 12:47 ` Ulf Samuelsson [this message]
2007-08-20 17:26 ` Benjamin Tietz
2007-08-20 18:13 ` Thiago A. Corrêa
2007-08-21 17:18 ` Benjamin Tietz
2007-08-27 10:53 ` Hans-Christian Egtvedt
2007-08-28 1:29 ` Thiago A. Corrêa
-- strict thread matches above, loose matches on Subject: below --
2007-08-19 13:08 Thiago A. Corrêa
2007-08-19 13:28 ` Philippe Ney
2007-08-19 14:51 ` Ulf Samuelsson
2007-08-19 14:56 ` Thiago A. Corrêa
2007-08-19 18:56 ` 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='001201c7e291$2b8f5ee0$dcc4af0a@atmel.com' \
--to=ulf@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