From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] How to build Kernel 2.6.x
Date: Wed, 14 Nov 2012 16:03:02 +0100 [thread overview]
Message-ID: <20121114160302.50eb8ca8@skate> (raw)
In-Reply-To: <CAAsE_ucA-Gag0v-9g4AObY=yB4DZH7AEuvA3zkwGEvUPv5JgWA@mail.gmail.com>
Dear Woody Wu,
On Wed, 14 Nov 2012 22:57:19 +0800, Woody Wu wrote:
> Thanks for telling the information. I will try 2.6.20 and see whether the
> error disappear.
Nooooo. If you're starting a project now, start with a recent kernel.
3.6 is the current one. Of course, check beforehand that there is
support for one platform in the mainline Linux kernel.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-14 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 9:19 [Buildroot] How to build Kernel 2.6.x woody
2012-11-14 14:31 ` Thomas Petazzoni
2012-11-14 14:47 ` Yann E. MORIN
2012-11-14 14:57 ` Woody Wu
2012-11-14 15:03 ` Thomas Petazzoni [this message]
2012-11-14 15:13 ` Woody Wu
2012-11-14 15:24 ` Thomas Petazzoni
2012-11-14 15:28 ` Richard Braun
2012-11-14 15:25 ` Jeremy Rosen
2012-11-14 15:07 ` Woody Wu
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=20121114160302.50eb8ca8@skate \
--to=thomas.petazzoni@free-electrons.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 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.