All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Buchanan <jamesb.au@iinet.net.au>
To: grub-devel@gnu.org
Subject: Update Multiboot spec
Date: Fri, 08 Jul 2005 14:31:50 +1000	[thread overview]
Message-ID: <42CE01B6.8050306@iinet.net.au> (raw)

Is anyone working on an updated Multiboot specification?

If no, I think we should start one and make a page for it on the GRUB-2 
devel wiki.  It should have extra options to scan for the MP structure 
on IA-32 machines, generalize the video options as much as possible 
(give framebuffer address and device and manufacturer IDs, bus and 
function number, something like that -- would it work for PowerPC and 
other machines?), options for detecting all hardware (e.g. linked 
structures saying I found so-and-so PCI cards, so-and-so type of 
graphics/sound/ethernet cards, monitor type and ID, this system has 
ACPI, CPUID for IA-32, things like that.)

I'm just thinking out loud here.  Does anyone want to help write a new 
Multiboot spec?

Thanks,
James



             reply	other threads:[~2005-07-08  4:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08  4:31 James Buchanan [this message]
2005-07-08  5:39 ` Update Multiboot spec Yoshinori K. Okuji
2005-07-08  6:57   ` James Buchanan
2005-07-09  2:49     ` Yoshinori K. Okuji
2005-07-09  5:19       ` Cyril Plisko
2005-07-10 22:28         ` Hollis Blanchard

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=42CE01B6.8050306@iinet.net.au \
    --to=jamesb.au@iinet.net.au \
    --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.