From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: USB device not seen by grub
Date: Sat, 5 Dec 2009 21:33:28 +0100 [thread overview]
Message-ID: <20091205203328.GC32638@thorin> (raw)
In-Reply-To: <2e59e6970912041445h603dc278m160695b832121b5@mail.gmail.com>
On Fri, Dec 04, 2009 at 04:45:01PM -0600, richardvoigt@gmail.com wrote:
> There are actually quite a lot of devices like this. Most notebooks
> have broken BIOS that won't load the extension ROM from a PCMCIA slot,
> if grub could do so it would enable booting from a wide variety of
> PCMCIA/CardBus/ExpressCard-to-SCSI/SATA/USB adapters.
PCI ROM processing is a feature we need. The reason we need this is
not to help proprietary OSes, but so that modules like vbe or biosdisk
can work on other platforms (e.g. coreboot).
The code in those ROMs is often proprietary, but it is external to the
motherboard. This is important, because GRUB may act as the primary
firmware for PC-class motherboards (when combined with coreboot). In
this kind of setup, GRUB itself can't support external cards using its
own drivers and must rely on the PCI ROM ones. Therefore this interaction
is always needed.
Also, some platforms like EFI insist on acting as a wrapper between these
PCI ROM drivers and the bootloader. Since this wrapper is completely useless
and just adding overhead, we might as well skip it.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
prev parent reply other threads:[~2009-12-05 20:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 20:26 USB device not seen by grub Chris Jones
2009-12-03 14:45 ` BandiPat
2009-12-03 15:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-03 18:01 ` Chris Jones
2009-12-03 20:02 ` Duboucher Thomas
2009-12-03 20:27 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-03 20:43 ` Chris Jones
2009-12-03 20:24 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-03 21:04 ` Chris Jones
2009-12-03 22:25 ` Chris Jones
2009-12-03 22:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-04 0:24 ` Chris Jones
2009-12-04 1:45 ` Chris Jones
2009-12-05 2:26 ` [solved] " Chris Jones
2009-12-05 2:58 ` richardvoigt
2009-12-05 4:29 ` Chris Jones
2009-12-05 9:16 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-11 0:45 ` Chris Jones
2009-12-23 7:03 ` Chris Jones
2009-12-04 0:27 ` richardvoigt
2009-12-04 21:36 ` Robert Millan
2009-12-04 22:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-05 3:28 ` richardvoigt
2009-12-05 20:22 ` Robert Millan
2009-12-04 22:45 ` richardvoigt
2009-12-05 20:33 ` Robert Millan [this message]
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=20091205203328.GC32638@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.