From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: Status of ARM machines in OE
Date: Wed, 10 Jan 2007 19:51:21 +0100 [thread overview]
Message-ID: <eo3cje$v28$1@sea.gmane.org> (raw)
In-Reply-To: <200701101432.06542.openembedded@hrw.one.pl>
Marcin Juszkiewicz wrote:
>> but still no SD, right?
>
> What does rule 'Machine must have working 2.6 kernel' has to do with SD?
That rule (which I understand and support fully, BTW) will break SD on
the collie.
>> What is not usable for users in collie angstrom?
>
> There is no MMC/SD support, few other things are not finished in 2.6 port
> too. Before those get fixed collie is unusable for users.
Well SD is certainly a major drawback. If that is the most important
thing, I would not call that "unusable", though. Just certain parts are
unusable.
Any machine maintainers for collie, yet, or nobody at all?
next prev parent reply other threads:[~2007-01-10 18:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 15:18 Status of ARM machines in OE Marcin Juszkiewicz
2007-01-08 15:28 ` Marcin Juszkiewicz
2007-01-08 16:03 ` Justin Patrin
2007-01-08 16:08 ` Koen Kooi
2007-01-08 18:12 ` Erik Hovland
2007-01-09 7:50 ` Marcin Juszkiewicz
2007-01-08 16:19 ` Cliff Brake
2007-01-08 16:22 ` Koen Kooi
2007-01-08 17:52 ` Richard Purdie
2007-01-08 18:10 ` Koen Kooi
2007-01-08 18:23 ` Paul Sokolovsky
2007-01-08 18:34 ` Koen Kooi
2007-01-08 19:34 ` Marcin Juszkiewicz
2007-01-09 13:30 ` Marcin Juszkiewicz
2007-01-09 13:34 ` Koen Kooi
2007-01-09 22:09 ` Rolf Leggewie
2007-01-09 22:22 ` Marcin Juszkiewicz
2007-01-10 13:00 ` Rolf Leggewie
2007-01-10 13:32 ` Marcin Juszkiewicz
2007-01-10 18:51 ` Rolf Leggewie [this message]
2007-01-10 14:06 ` Paul Sokolovsky
2007-01-10 14:38 ` Koen Kooi
2007-01-10 14:54 ` [Angstrom-devel] " Paul Sokolovsky
2007-01-08 17:18 ` pHilipp Zabel
2007-01-09 18:07 ` Paul Sokolovsky
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='eo3cje$v28$1@sea.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.