Intel GPU Driver Tries To Rip Out FBDEV Support
Phoronix: Intel GPU Driver Tries To Rip Out FBDEV Support
Intel's Daniel Vetter is attempting for the Intel DRM graphics driver to remove support for its FBDEV frame-buffer layer with a new patch-set entitled "fbdev no more!", but will this finally usher in the killing of the Linux kernel's FBDEV subsystem?..
What does it mean though? Does it mean no hi res console? No console decorations?
no fbdev? how would Weston work in VirtualBox?
VirtualBox gets off its ass and makes a proper KMS driver like VMWare is working on/did
Originally Posted by nerdopolis
EDIT: Oh hey, guess they are. http://www.phoronix.com/scan.php?pag...tem&px=MTAxOTk Shouldn't be an issue then.
Last edited by Ericg; 06-17-2013 at 06:28 PM.
Does anyone really use console decorations? And high res is still supported, you just do a straight up DRM console instead of FBDEV console (See KMSCon)
Originally Posted by duby229
I love this. Now nVidia's property drivers will be forced to either target kmdcon's fbdev since the kernel's is being deprecated, or get rewriten to use the kernel's own Mode Setting (KMS) instead of the driver's
Finally, I'll get to have decent resolutions on my linux console :P
I suppose AMD will also need to clean up some of it's Catalyst code now...
I've had to use virtual terminals as a fallback in situations where I've bricked my video drivers. It would sure be nice to retain high-res VTs if DRM is not working. Does anyone know if that ability will be removed as part of the process?
I presume you mean kernel DRM, not the userspace side of DRM?
Originally Posted by MaxToTheMax
If so, you never had high resolution VTs without kernel DRM, unless you use a straight framebuffer (unaccelerated) driver, whether native or VESA/VGA.
If you mean the userspace DRM interface, the short answer is yes:
The longer answer is that the in-kernel accelerated graphics drivers all use DRM, the kernel VT emulation currently uses fbcon in graphics mode, and fbcon currently needs a framebuffer; no one wants to maintain the VT emulation, so "drmcon.ko" will probably not happen.
Originally Posted by Daniel Vetter
Now, I'll try to avoid a system without fbdev, even if it means not updating to a new kernel; for me, it would break Links2 and fbi, and it would spell the end for fbvnc, etc. Say what you will about "x is broken, you shouldn't use it": it works for me, and I can use a graphical browser without needing to fire up X.
Oh, the patches aren't quite what they're advertised as. They make fbdev support optional, by stubbing out all the hooks when you don't select DRM_I915_FBDEV. Which means that all of the analysis above is only true for CONFIG_DRM_I915_FBDEV=n.
Hmmm..that's sucks. Browsing with links2, watching videos with mplayer and even playing SLD games (fb is the only true way to use ScummVM) on the console weekends was always pretty fun
And FBDEV is a pretty nice fallback option in case of X failure too
Did I understand correctly? They are completely ditching the VT subsystem without providing any equivalent replacement? Certainly this can't be.