On Wed, Aug 22, 2007 at 03:47:31PM +0200, Matthias Hopf wrote: > No. But you already limit yourself to the primary card, a new design > shouldn't be limited that way. And an astonishingly big number of people > have to rely on vesa fb, because driver development for their hardware > sucks big time (no docs, no hardware in time, etc.). Currently AFAIK we > don't allow changing the resolution here during runtime, I'd like to see > a new framework being flexible enough with this respect.
Why on earth do you need vesafb? Just use the vesa driver and be done with it. (Also, there's nothing preventing runtime mode changes when using the fbdev driver. If there's a missing hook, then just add it.) Cheers, Daniel
signature.asc
Description: Digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
-- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
