From: Paul Sokolovsky <pmiscml@gmail.com>
To: openembedded-devel@lists.openembedded.org,
<angstrom-distro-devel@linuxtogo.org>
Subject: Re: [Angstrom-devel] Status of ARM machines in OE
Date: Wed, 10 Jan 2007 16:54:55 +0200 [thread overview]
Message-ID: <1127600830.20070110165455@gmail.com> (raw)
In-Reply-To: <45A4FA79.7040706@dominion.kabel.utwente.nl>
Hello Koen,
Wednesday, January 10, 2007, 4:38:49 PM, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Paul Sokolovsky schreef:
> <snip>
>> So, what's really required is someone to physically test
>> boot on a machine, and that's enough. Not boot means upstream (hh.org)
>> kernel problem, otherwise, it works (bugs are either common or due to
>> specific kernel bug also).
> That's not true. Yesterday my h5550 didn't boot, but I got it booting by using the a
> different /boot/params and fixing the fstab.
Yes, I know, that what I wrote to the large part is wishful thinking
at this time, but if people indeed change point of view to such
discrepancies from "we're stuck at that" to "temporary evil", it would
quickly become reality.
As for h5000 hardships, recent bootloader talk was exactly about
that - if all or none of pocketpc's used /boot/params, there woild be much
less probability for such issues, and they would reoccur much rarely
and be fixed much quicker.
fstab is of course more hard case - while it's very tempting to
reduce to a single standard MTD layout, it's less practical that
having single generic bootloader support (+ any number of adhoc
model-specific ones, of course).
> regards,
> Koen
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-01-10 14:56 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
2007-01-10 14:06 ` Paul Sokolovsky
2007-01-10 14:38 ` Koen Kooi
2007-01-10 14:54 ` Paul Sokolovsky [this message]
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=1127600830.20070110165455@gmail.com \
--to=pmiscml@gmail.com \
--cc=angstrom-distro-devel@linuxtogo.org \
--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 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.