From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Distros supporting older kernels?
Date: Thu, 09 Jun 2011 15:43:10 -0700 [thread overview]
Message-ID: <4DF14C7E.7000701@gmail.com> (raw)
In-Reply-To: <4DF0C472.4030608@dresearch-fe.de>
On 06/09/2011 06:02 AM, Steffen Sledz wrote:
> Hi Distro Maintainers,
>
> as you could read in earlier messages of mine, we're forced to use an
> older kernel version (2.6.24) for our hardware. This brings a lot of
> problems as you can imagine (e.g. we're also bound to udev-141).
>
> Until now we've used angstrom-2008.1 with some own patches according to
> the linux-libc-headers and udev versions for our hardware which were
> reasonably not accepted by the Angstrom maintainers (see discussions [1]
> or [2]).
>
> In there current situation (angstrom-2008.1 is deprecated, the new layer
> concept will come up) we're looking for a new, better, less hacky solution.
>
> My first question therefor is if there are any distros explicitely
> supporting older kernels (pre 2.6.27) yet? Or are willing to work on it?
>
I guess a machine layer on top of oe-core could be something you can
work out and add/override needed recipes in this layer.
> [1] <http://thread.gmane.org/gmane.comp.handhelds.openembedded/32375>
> [2] <http://thread.gmane.org/gmane.comp.handhelds.openembedded/42628>
>
> Thx,
> Steffen
>
> PS: Does anybody know a good overview which Linux Kernel API changes
> were made in which kernel version?
>
next prev parent reply other threads:[~2011-06-09 22:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 13:02 Distros supporting older kernels? Steffen Sledz
2011-06-09 13:12 ` Koen Kooi
2011-06-09 13:35 ` Steffen Sledz
2011-06-09 22:43 ` Khem Raj [this message]
2011-06-12 9:19 ` Steffen Sledz
2011-06-12 11:47 ` Koen Kooi
2011-06-15 6:00 ` Steffen Sledz
2011-06-15 14:58 ` Khem Raj
2011-06-12 21:21 ` Frans Meulenbroeks
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=4DF14C7E.7000701@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox