> > Yuck. See my other post about what fbdev really means in its historical > > context. The struct fb_info really maps better to drm_crtc than to > > drm_framebuffer. In fact take the case of the matrox fbdev driver. It > > creates two framebuffer devices even tho it used one static framebuffer. > > What the driver does is splits the framebuffer in two and assigned each > > part to a CRTC. > > > > So you get the layering naturally. On fbset - fbev layer you can > choose from the resolutions available in the current output setup, in > kmset or whatever - drm layer you can set up the outputs, merge > multiple outputs into single cloned fbdev or separate them, .. > > It's obviously nice if you can set the resolution on all of fbcons, > fbdev and drm layers but getting it work on at least one layer with > proper propagation up and down also works. BTW I don't know any > application which sets linux console (or xterm for that matter) > resolution through the terminal API.
I agree. The mode setting should be done in one layer. Its a matter of doing the proper emulation of the fbdev layer. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
