[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC] Multiboot ammendment: non-VBE video
From: |
Robert Millan |
Subject: |
Re: [RFC] Multiboot ammendment: non-VBE video |
Date: |
Thu, 24 Dec 2009 23:29:23 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
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
- Re: [RFC] Multiboot ammendment: non-VBE video,
Robert Millan <=