On Fri, Mar 16, 2012 at 12:22 PM, Gerd Hoffmann <[email protected]> wrote: > On 03/16/12 13:10, Kevin O'Connor wrote: >> On Fri, Mar 16, 2012 at 10:38:42AM +0100, Gerd Hoffmann wrote: >>> Hi, >>> >>>> Is it worth trying to support high resolutions in Xorg ? If yes, then >>>> we need to expose a valid EDID block. But what capabilities should the >>>> virtual monitor report ? (I mean max resolution, preferred resolution, >>>> should they be static, provided by configuration options, or >>>> dynamically chosen at run-time). >>> >>> At runtime, read from qemu firmware config interface? >> >> The bochsvga code seems to already get a maximum resolution and >> maximum depth through the vbi interace. See the "validate modes" >> section of bochsvga.c:bochsvga_init(). > > Yea, it checks whenever the modes fit into the amout of memory available. > > 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. -- Julian _______________________________________________ SeaBIOS mailing list [email protected] http://www.seabios.org/mailman/listinfo/seabios
