Hi,

On 4/8/22 13:18, Kevin Kofler via devel wrote:
> Hans de Goede wrote:
>> So most hw will either be new enough to offer an efifb which
>> simpledrm will turn into a drm/kms /dev/dri/card0 device. Or it
>> will be old enough that it almost certainly will have
>> a drm/kms driver.
>>  
>> And for the really odd duck out a vesa mode can be set on the kernel
>> cmdline which simpledrm should then pick up:
>>  
>> https://www.kernel.org/doc/html/latest/admin-guide/svga.html
>> https://www.systutorials.com/configuration-of-linux-kernel-video-mode/
> 
> Thanks for the explanation. If that is true, then this change should be more 
> acceptable than the partly related "desupport all non-(U)EFI systems" one 
> (which I consider entirely unacceptable).
> 
> Still, I remain worried about the details, such as:
> * that, if VESA is needed, the VESA mode has to be configured through the
>   kernel CLI,
> * that, as far as I can see, switching to another mode with kernel VESA
>   requires a reboot (with different kernel CLI options),

Both are correct and are indeed somewhat of a downside, although I'm
not sure if Xorg ever automatically uses vesa as fallback of last
resort, or if this needs manual setup.

> * what will happen to the "basic video mode" boot option (as pointed out by
>   Kamil Paral).

That is a good question, AFAIK this is just adding nomodeset on the
kernel cmdline, so on UEFI systems we will just end up with simpledrm
using the EFI framebuffer device. I'm not sure what will happen with
legacy BIOS boot here though.

Regards,

Hans
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to