Log in


December 2016
        1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31

airlied [userpic]
AMD annoucement of open drivers...

So the news is out that AMD have committed to opening up specifications and providing some driver code to the open source community!!!

Alex Deucher and I have been working with AMD on this for about 3 months now and it's great to see it finally go public with their plans going forward. The initial code from Novell/SuSE will be appearing around XDS time, and AMD will also be attending.

Initially it will be a 2D modesetting driver, and hopefully a 3D driver will follow later. They are not stopping work on fglrx and will not be releasing any code from fglrx.

They will also be providing us with some access to engineering staff for information on older cards that we hadn't access to before, so we can properly support the current radeon driver (mainly BIOS parsing and workarounds..)

AMD, myself and Red Hat are also working through clearing me from my NDA issues so I can work on the r5xx cards.

So its all very positive and hopefully it we can all work together going forward to produce a top-notch open source driver...

If anyone has any questions on this feel free to post them here and I'll try and answer them if I can...

Re: Hooks for binary only parts?

I suspect, at least for the case of copy protection, that it'd be much easier (and probably more performant) to implement the "HDCP-aware" bits as a direct-rendering driver, parallel to what we already have for GL and similar to how XvMC works. If you put it in the 2D driver you have to work out the network protocol to get the encrypted bits into the driver which is a lot of work for nothing. (Although, the whole discussion of copy protection is a lot of work for nothing...)

I guess to answer the question: it doesn't really matter where closed blob hooks go, the reaction will be about the same. But again, we have no indication they even want to do that yet.