From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] Multiboot ammendment: non-VBE video
Date: Thu, 24 Dec 2009 23:29:23 +0100 [thread overview]
Message-ID: <20091224222923.GW12122@thorin> (raw)
In-Reply-To: <d7ead6de0909010837k285d1a88tdee3d999d3cd57e2@mail.gmail.com>
On Tue, Sep 01, 2009 at 05:37:11PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> Hello. I'm implementing video part of multiboot specification.
> Currently the only defined interface is for providing VBE info. I
> propose following way to set fields if video is non VBE:
> vbe_control_info=0xffffffff
> When vbe_control_info is set to 0xffffffff all VBE-specific fields are invalid
> vbe_mode set to 0xffff
> vbe_interface_seg=0xffff
> vbe_interface_off=0xffff
> vbe_interface_len=0xff
> vbe_mode_info points to structure similar to vbe_mode_info but with
> all vbe-specific fields set to zero. Remaining (valid) fields are
> (full structur is in include/grub/i386/pc/vbe.h)
This seems like one of these cases in which legacy gets in the way. Why
don't we just replace the legacy structure with something that doesn't need
dummy fields?
--
Robert Millan
"Be the change you want to see in the world" -- Gandhi
next prev parent reply other threads:[~2009-12-24 22:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 15:37 [RFC] Multiboot ammendment: non-VBE video Vladimir 'phcoder' Serbinenko
2009-12-24 22:29 ` Robert Millan [this message]
2009-12-28 12:07 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-01 11:30 ` Robert Millan
2010-01-02 18:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-03 16:13 ` Robert Millan
2010-01-03 16:35 ` Isaac Dupree
2010-01-04 21:19 ` richardvoigt
2010-01-04 19:35 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-07 18:45 ` Robert Millan
2010-01-07 20:18 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-12 16:52 ` Robert Millan
2010-01-12 16:54 ` Multiboot video in GRUB (Re: [RFC] Multiboot ammendment: non-VBE video) Robert Millan
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=20091224222923.GW12122@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.