All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Setje-Eilers <setje@sun.com>
To: rmh@aybabtu.com
Cc: grub-devel@gnu.org
Subject: Re: VBE info request bit per Multiboot Specification 1
Date: Tue, 04 Aug 2009 16:49:57 -0700	[thread overview]
Message-ID: <4A78C925.3010506@sun.com> (raw)

  <re-send after fixing subscription>

> On Tue, Aug 04, 2009 at 01:37:19PM -0400, Francis Shim wrote:
>> Hi,
>> 
>> In the Multiboot specifications (version 1), there is a flag that
>> the OS Image can set to request that the boot loader provide VBE
>> information to the OS kernel upon boot up via the Multiboot
>> Information structure. Legacy GRUB (GRUB1) deos not support this
>> feature without a patch that is circulating around in OS
>> development websites;
> 
> Hi,
> 
> It's not implemented.  But since you mention that a patched GRUB 
> Legacy supports it, I assume there are a number of OSes that
> implement it.

  FWIW, we've got a prototype VESA console for Solaris that uses that
structure to avoid additional mode switches. In fact, was just looking
into what this looked like in GRUB 2 when someone pointed this thread
out to me.

  If the structure is built up compatibly, things should just work.

> Can you provide us with a test case?  This would make an
> implementation of the GRUB side much easier.
> 
> Btw, would you like to work on this?  It's not difficult, as we
> already support something analogous in the Linux loader.

  Unless there's another preferred interface (or someone beats us to it).
we'll likely end up filling in. Considering the VBE code that's already
there this is fairly trivial.

-jan




             reply	other threads:[~2009-08-04 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-04 23:49 Jan Setje-Eilers [this message]
2009-08-05 10:47 ` VBE info request bit per Multiboot Specification 1 Vladimir 'phcoder' Serbinenko
2009-08-07 11:14 ` Robert Millan
  -- strict thread matches above, loose matches on Subject: below --
2009-08-04 17:37 Francis Shim
2009-08-04 20:35 ` Robert Millan
2009-08-05  2:19   ` Francis Shim

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=4A78C925.3010506@sun.com \
    --to=setje@sun.com \
    --cc=grub-devel@gnu.org \
    --cc=rmh@aybabtu.com \
    /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.