From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Moving from 2.6.36.1 to 2.6.35.11 (or perhaps 2.6.35.9)
Date: Sun, 20 Feb 2011 08:21:19 +0100 [thread overview]
Message-ID: <87pqqndvdc.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <AANLkTikMqQa2b8VALCFzCvhzhLGokgjjeu5jwWgbspv1@mail.gmail.com> (Charles Krinke's message of "Sat, 19 Feb 2011 15:21:47 -0800")
>>>>> "Charles" == Charles Krinke <charles.krinke@gmail.com> writes:
Hi,
Charles> My group desires to use the 2.6.35.11 kernel as it is listed
Charles> as a longterm stable kernel instead of the 2.6.36.1 buildroot
Charles> currently supports <sigh>.
Ok.
Charles> In looking at at buildroot, it appears that changine
Charles> buildroot-2010.11/.config BR2_DEFAULT_KERNEL_HEADERS *and*
Charles> linux/Config.in (3 places) would do it to change to an
Charles> arbitrary kernel version.
Charles> Is this the correct procedure to change these two files? I can
Charles> make it work with 2.6.35.9, but it seems that
Charles> kernel.org/pub/linux/kernel/v2.6/ contains up to 2.6.35.9 but
Charles> not 2.6.35.10 or 2.6.35.11 so 2.6.35.9 works but 2.6.35.11
Charles> fails.
The problem is that the long term kernels is a concept that didn't exist
back when 2010.11 was released. Since 2011.02-rc1 we now automatically
handle the long term support kernels for 2.6.35 for the kernel headers.
Notice that it isn't strictly required to use the exact same kernel
headers version as the kernel, so you could keep your kernel headers at
2.6.35.9 without any likely issue.
For the kernel you can simply choose 'custom tarball' and provide the
long term URL.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-02-20 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 23:21 [Buildroot] Moving from 2.6.36.1 to 2.6.35.11 (or perhaps 2.6.35.9) Charles Krinke
2011-02-20 0:41 ` Bjørn Forsman
2011-02-20 7:21 ` Peter Korsgaard [this message]
2011-02-21 20:46 ` Charles Krinke
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=87pqqndvdc.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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