That's a great point. Would it be possible to re-structure the Closed Source code in a way that a lot of the stuff is shared with the OS version? And then hooks for either binary bits for patented stuff or OS counterparts.
Originally Posted by elanthis
If this was implemented that way, then the clean room concerns would be limited to those bits, and it would all be easier for everyone. Of course there may be reasons why that is not feasible ...
Either that or there is no hardware acceleration for some reason. What's the output of
Originally Posted by icek
HD4200 here and also very smooth with compiz. KDE's Kwin is sluggish though.
glxinfo |grep rendering
The closed source driver will not be opened, people should stop trying to come up with a bright idea about. The closed driver is so big and so intermigle with sensitive technology (content protection stuff) that it doesn't make sense to open it. Moreover it's a completely different codebase, it could not be integrated with mesa.
Originally Posted by mendieta
Sadly, and I'm guessing you're aware of this, a lot of proprietary (and open source no doubt!) software is just....munted. Comes with top management wanting deadlines over maintainability, and then of course later there's other things to do and you don't get a chance to go back an clean things out, another deadline looms, hacks are made, and so the cycle continues.
Originally Posted by devius
I'm quite sure there are interesting comments in any the code for any proprietary driver, from stressed out and annoyed devs.
I should make it clear that the "hd7xxx" and "hd8xxx" names came from curaga and I responded using the same terminology - I don't know what future generations of GPUs will be called when they hit the market.
If you see the alternative.
Funny... if those end up being the final names, the radeons will go back to the same name they had 11 years before (with an added HD, and probably a bit more processing power).
Originally Posted by bridgman
Tags for this Thread