On 04/30/2013 02:42 PM, Laurent Pinchart wrote: > On Tuesday 30 April 2013 12:28:42 Arnd Bergmann wrote: >> On Tuesday 30 April 2013, Tomi Valkeinen wrote: >>> The bootloader would init the display hardware, the bootfb would give an >>> early /dev/fb0 for the kernel and userspace, and when the real display >>> driver is loaded, the bootfb would be unbound and the real driver would >>> take over. > > This could be done with a KMS driver as well ;-)
Right, I forgot to mention that. I had it in mind also =). DRM has the same problem as fbdev with multi-arch and lots of display and panel drivers. Probably the same bootfb could be used for DRM also. Or do you see any benefit of having a "bootkms" driver, or such? Tomi
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
