> > Why would layering the DRM on top of the fbdev driver break DirectFB? I > (think I) understand the issues with actually merging the drivers, but > the more I dig into, for example, MGA DRM, the more convenient it seems > to have DRM on top of fbdev.
It won't if you do it properly.. Jons was doing his well Xegl doesn't need this so we can rip it out method, which doesn't sit well with me or Benh..... he wanted to put the card into a mode at bootup and not let it back out, and have user space consoles and Xegl all running in user space, which is a laudable goal, but things like DirectFB and X expect to be able to take full control, his methods were travelling down the road of preventing this using the justification that no-one will need to run X as Xegl will be king... I may be mis-representing exactly what the issues were but that was what I felt was happening... the basics are Linux fbdev model is horrid, we need to work with it for some sort of backwards compatiblity, we can't just dump it all for some currently prototype project... We'll get where Jon sees us going eventually but we are going to have to get there by a lot more circular method than just warping space/time and stepping through the gap... Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie Linux kernel - DRI, VAX / pam_smb / ILUG ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
