From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Patches and discussions about the oe-core layer"
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH 1/2] bitbake.conf: update OLDEST_KERNEL to 2.6.0
Date: Thu, 7 Jul 2011 15:34:51 +0100 [thread overview]
Message-ID: <201107071534.51372.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <09ECC867-24F5-4CC7-8312-F00F34897B68@dominion.thruhere.net>
On Thursday 07 July 2011 15:24:46 Koen Kooi wrote:
> angstrom has been setting it to 2.6.16 for some years now, I forget which
> bug that fixed over 2.6.0
Personally I don't know enough about which crusty old 2.6 kernels people are
still using out there, so I figured 2.6.0 was the safest bet.
A trawl of the OE history turns up these two:
-----------------------------------
commit 8b0202e6e3f90a772df301e8522f9deb03e50132
Author: Tom Rini <tom_rini@mentor.com>
Date: Wed Mar 3 12:17:38 2010 -0700
glibc*.inc: Bump OLDEST_KERNEL to 2.6.16
Per glibc's ChangeLog, 2.6.16 is the minimum required by at least glibc
2.9
Prior to this, it was a murky 2.6.14 + patches to 2.6.16 (when it was all
upstream).
-----------------------------------
commit 794e8652f5c4fef71a8b9ab834b39f75b99f9420
Author: Koen Kooi <koen@openembedded.org>
Date: Thu May 21 20:30:37 2009 +0200
Angstrom 2009.X: set OLDEST_KERNEL to 2.6.16 to avoid problems with
ppoll()
-----------------------------------
Any further comments/info? Should we be using 2.6.16 in oe-core as well?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-07-07 14:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 13:11 [PATCH 0/2] update OLDEST_KERNEL Paul Eggleton
2011-07-07 13:11 ` [PATCH 1/2] bitbake.conf: update OLDEST_KERNEL to 2.6.0 Paul Eggleton
2011-07-07 14:24 ` Koen Kooi
2011-07-07 14:34 ` Paul Eggleton [this message]
2011-07-07 23:15 ` Richard Purdie
2011-07-08 5:21 ` Khem Raj
2011-07-08 8:38 ` Paul Eggleton
2011-07-08 8:46 ` Chris Elston
2011-07-08 9:49 ` Paul Eggleton
2011-07-08 9:53 ` Phil Blundell
2011-07-08 10:03 ` Paul Eggleton
2011-07-08 10:12 ` Phil Blundell
2011-07-08 10:20 ` Paul Eggleton
2011-07-08 14:17 ` Khem Raj
2011-07-08 16:28 ` Richard Purdie
2011-07-07 13:11 ` [PATCH 2/2] eglibc: bump PR for OLDEST_KERNEL change Paul Eggleton
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=201107071534.51372.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
/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.