Hi,
I was thinking more along the lines of having etc/vga-prefered-{xres,yres} fw_cfg files, then generate a EDID block with them so xorg can pick them up and use as default resolution?
The problem is that the bochs driver will become qemu specific if we do that.
Of course we'll need default backups in case the fw_cfg interface or the config files in fw_cfg space are not present, not only for non-qemu use cases but also old qemu versions.
We could also extent the bochs interface for that (which is maybe the better option anyway).
cheers, Gerd
On Fri, Mar 16, 2012 at 12:33 PM, Gerd Hoffmann kraxel@redhat.com wrote:
Hi,
I was thinking more along the lines of having etc/vga-prefered-{xres,yres} fw_cfg files, then generate a EDID block with them so xorg can pick them up and use as default resolution?
The problem is that the bochs driver will become qemu specific if we do that.
Of course we'll need default backups in case the fw_cfg interface or the config files in fw_cfg space are not present, not only for non-qemu use cases but also old qemu versions.
We could also extent the bochs interface for that (which is maybe the better option anyway).
That sounds good. I think a good interface would expose the EDID block directly instead of a prefered resolution and let Seabios forge the EDID. Qemu is also the "virtual monitor" after all... It is easier to have support code which generates the EDID block in qemu, than having it in SeaBIOS.
-
Gerd Hoffmann -
Julian Pidancet