Hi, > >> Otherwise a guest driver that assumes it is always present and tries > >> to read from that area of memory will crash. > > > > Oh, reading should work no matter what. You just don't find valid edid > > data there if it is turned off. > > Thanks for the info. My current use case for this is passing a set of > possible guest > display resolutions from the host to the guest driver, rather than using an > internal > hard-coded list. I guess that over time QEMU could become "smarter" about > building > the list of supported resolutions depending upon the capabilities of the host?
Yes, that is the plan. There are xres and yres properties already, which will show up as preferred resolution in the edid blob. The generator also supports to set the maximum display resolution, and the display dpi (needed when we add hidpi support some day). stdvga doesn't support to change the edid dynamically (i.e. on window resize) because the hardware doesn't support interrupts, so we can't easily signal edid updates to the guest. cheers, Gerd
