From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] meta-handheld
Date: Sun, 24 Apr 2011 10:25:03 +0100 [thread overview]
Message-ID: <201104241025.03973.paul.eggleton@linux.intel.com> (raw)
In-Reply-To: <BANLkTime-0+ye-PRrZW5F9zSu9WNvSERYg@mail.gmail.com>
On Saturday 23 April 2011 00:09:38 Andrea Adami wrote:
> I agree with Richard, for keeping it as meta- group.
> About expectations, at least for Zaurus I don't see problems: vanilla
> 2.6.38 kernel, actual udev, imminent move to xorg-xserver if kdrive is
> finally doomed.
>
> Ipaq's seem suffering more bitrot...
This is a problem, yes. Most of the iPAQs require 2.6.21-hh which is ancient
and unmaintained and as we know presents difficulties with modern udev. Some of
the iPAQs will work with mainline but many functions will be unavailable. This
is something I hope can be sorted out - surely by now a lot of the "ip blocks"
used within iPAQs and other PDAs are now in mainline already and all that's
necessary is some plumbing...?
Anyway, I'm concerned that if these machines get pushed out to some random
repo it's only going to make things worse. I think we can mitigate the
concerns about people rushing in only to find that the level of support for
their device is less than they hoped simply by being crystal clear about each
device's status in documentation (e.g. a wiki page), something which we have
not been good at recently. (Am I volunteering to maintain this information as
well? Naturally :) )
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre (UK)
next prev parent reply other threads:[~2011-04-24 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 16:04 [RFC] meta-handheld Paul Eggleton
2011-04-21 16:57 ` Graeme Gregory
2011-04-21 17:27 ` Koen Kooi
2011-04-21 19:21 ` Richard Purdie
2011-04-22 23:09 ` Andrea Adami
2011-04-24 9:25 ` Paul Eggleton [this message]
2011-04-25 19:15 ` Khem Raj
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=201104241025.03973.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox