-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dave Airlie wrote:
> And to be honest this is "bollocks" I don't want to quote private mails > here, but neither myself or benh said anything of the sort from my > reading, we just a) didn't like your Xegl is the *ONLY* way forward > approach and b) your approach stomped on any chance that older apps (and > DirectFB) would continue working... we both stated we see a three-tier > approach to merged drivers being the way forward, and I'm going to start > adding hooks to CVS, just because we aren't willing to jump in and apply > patches straight away might speak more about how we are "maintainers" and > not "break everything in sighters to add a new feature.." 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. Not trying to stir up trouble, just trying to understand all the issues... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCsgAxX1gOwKyEAw8RAsTgAKCIWVyQicEDlQZohy07wVmS/10dzgCfT0UE Xw07jUE7l+Y1WthmHdMPujM= =vrLN -----END PGP SIGNATURE----- ------------------------------------------------------- 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