On 16 June 2015 at 17:20, Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote: > On Di, 2015-06-16 at 14:57 +1000, Dave Airlie wrote: >> Hi Gerd, >> >> just looking at the display info vs fbdev init, why are they not the >> other way around, it makes no sense to me to init fbdev and then >> hotplug it with the display info response, surely setting it up on the >> current displays is what we want. > > fbdev doesn't (and can't by ioctl interface design) response to hotplug, > so the framebuffer console will not adapt to window resizes anyway. So > I through just going with 1024x768 for the framebuffer console (like all > other qemu kms drivers) is fine. But fbcon does react to console resizes, we hotplug them with kms drivers, However it is limited to the a maximum of the first size allocated, so if we know in advance we need a larger display then things can resize down below that. > We can change it it you prefer, we'll need to wait for the display_info > response then and move fbdev init down a few lines. Yes that would be fine, Dave. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
