[OpenBIOS] [PATCH v2] Implement copy-resolutions-property

[Mark Cave-Ayland]

On 01/10/16 20:35, Tarl Neustaedter wrote:

> On 2016-Oct-1 14:11 , Mark Cave-Ayland wrote:
> 
>> Finally for reference take a look at the Sun Framebuffer FAQ at
>> http://www.sunhelp.org/faq/FrameBuffer.html to check the format the mode
>> string should be in (it seems to be the format eluded to earlier by
>> Tarl)
> 
> Yup. Looking at that, I'm reminded there are four variables for
> resolution: Height, Width, bits-per-pixel, and frequency (updates per
> second).
> 
> The usual answer for how this worked was that you specified a particular
> resolution at startup, and subsequent drivers looked up that resolution
> in their own tables. There wasn't anything about passing a list of
> resolutions in, it was _the_ specific resolution to use. The assumption
> is that when you picked the startup resolution, that was the resolution
> you intended to use, period.

Yes I think that's what I'm inclined to do - add the standard VGA/XGA
resolutions along with the current custom resolution if specified.


ATB,

Mark.