Lines Matching refs:fbdev
246 Reimplement functions in drm_fbdev_fb_ops without fbdev
250 being rewritten without dependencies on the fbdev module. Some of the
271 Benchmark and optimize fbdev's sys_() helpers and DRM's format-conversion
304 Generic fbdev defio support
307 The defio support code in the fbdev core has some very specific requirements,
308 which means drivers need to have a special framebuffer for fbdev. The main
313 Possible solution would be to write our own defio mmap code in the drm fbdev
323 fbdev defio stuff. These should all work on plain ptes, they don't actually
453 DRM and fbdev drivers. Still, it's the correct thing to do.
462 A number of fbdev drivers provide attributes via sysfs and therefore depend
529 awesome if we could test at least the fbdev helper code and driver code by
533 * There's a massive confusion of different panic handlers. DRM fbdev emulation
537 into the DRM fbdev emulation helpers. A much cleaner approach here would be to
734 for fbdev.
856 Convert fbdev drivers to DRM
859 There are plenty of fbdev drivers for older hardware. Some hardware has
862 removed from fbdev.
864 Very simple fbdev drivers can best be converted by starting with a new
867 existing fbdev code.
869 More complex fbdev drivers can be refactored step-by-step into a DRM
871 the transition layer between the DRM core infrastructure and the fbdev
873 copy over the fbdev driver, and hook it up to the DRM code. Examples for
874 several fbdev drivers are available in Thomas Zimmermann's fbconv tree