From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>,
devel@lists.laptop.org, testing@lists.laptop.org
Subject: GRUB and OLPC
Date: Mon, 08 Apr 2013 00:45:25 +0200 [thread overview]
Message-ID: <5161F705.4050605@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1993 bytes --]
Hello, all. GRUB has supported OLPC for quite some time but I don't know
if there are any remaining users. Given how small the intersection
between geeks and XO-1 owners nowadays is, continuing support is
problematic. Among other things it's likely to degrade over time unless
at least minimum maintainance is done. AFAIK none of the active GRUB
maintainers even possesses one. The current regular testing is limited
to checking whether it builds. The underlying OLPC ieee1275 firmware
implementation OFW supposedly supports also qemu and coreboot. While
it's still somewhat functional in qemu, it lacks important drivers for
modern system when booted with coreboot, most notably AHCI. Some basic
automated testing can be performed with OFW on qemu. They currently
aren't, another gap needed to fill.
Half of the drivers for OLPC aren't included in this OFW-qemu, each of
them with specific interface. As a matter of fact we have some
workarounds enabled for real OLPC which are not needed in qemu but
without them GRUB would hang on real machine. I don't know if they still
work. So tests on qemu are better than nothing but give very small
guarantee. Also OLPC is at intersection of generic i386
XT-almost-compatible and OFW. Whether ieee1275 or i386 functions work
better can be inferred from testing on real hardware but failing that
none is used and corresponding functionality is just disabled. Because
of all these reasons i386-ieee1275 lags behind and missing features
often require special case-checking in other parts. E.g. write-back to
nand is probably trivial to implement but can't be so without testing.
Supporting jffs2 on nand without testing isn't realistic either.
Because of all these reasons it may be time to either find solutions to
at least some of problems (mainly lack of testing) or to retire the port
altogether.
P.S: attitude of OFW devs of rejecting even an idea of GRUB for OLPC
like I've just experienced on IRC isn't helpful.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next reply other threads:[~2013-04-07 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 22:45 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-04-07 23:12 ` GRUB and OLPC James Cameron
2013-04-08 0:18 ` [Testing] " Mitch Bradley
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=5161F705.4050605@gmail.com \
--to=phcoder@gmail.com \
--cc=devel@lists.laptop.org \
--cc=grub-devel@gnu.org \
--cc=testing@lists.laptop.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.