[syslinux] best resolution detection

[Shuduo Sang]

On Fri, Apr 19, 2013 at 12:30 AM, Gene Cumm <gene.cumm at gmail.com> wrote:
> On Thu, Apr 18, 2013 at 11:55 AM, Shuduo Sang <sangshuduo at gmail.com> wrote:
>> On Thu, Apr 18, 2013 at 11:15 PM, H. Peter Anvin <hpa at zytor.com> wrote:
>>> On 04/16/2013 11:45 PM, Shuduo Sang wrote:
>>>>>
>>>>> It is a bit hard, because even if the relevant BIOS calls are
>>>>> implemented, most video BIOSes have a fixed list of largely archaic
>>>>> resolutions.
>>>>
>>>> grub2 can use VESA BIOS extensions to get supported resolution list.
>>>> Although there be possible mistake BIOS grub meet and make grub fallback.
>>>> If syslinux has this feature we may reduce resolution switching and reduce
>>>> screen flash or visual artifacts at last.
>>>>
>>>
>>> I don't think you understood what I am saying.
>>>
>>> On a typical laptop, this is what VESA BIOS will tell you:
>>>
>>> "Welcome to VESA BIOS.  The native resolution is 1600x900.  Would you
>>> like to set your screen resolution to 640x480, 800x600, 1024x768, or
>>> 1280x1024?"
>>>
>>> To be fair, there are some which are much better than that, but they are
>>> the exception, not the rule.
>>>
>>>         -hpa
>>>
>>>
>>
>> Sorry if I misunderstand your point. Back to my question, is it
>> possible to have a feature
>> like grub's GRUB_GFXMODE=auto? Then we can use one universal USB disk
>> on different
>> system with different best resolution. And we also need to support
>> background stretch/zoom
>> etc like Gene mentioned.
>>
>> Thanks,
>> Shuduo
>
> If the VESA BIOS says "I want 1600x900 but I won't tell you how", what
> do you choose?  1024x768, 1280x1024, or 640x480?
>

We don't need expect everything perfect. I guess grub can't handle
this too. We can still use
hard code resolution as what we're using right now.

> --
> -Gene
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>