If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

How much work to get it into the other drivers? I thought the OpenGL3 implementation was in the shared code and not specific drivers, so what's the ratio there? How much of the work will automatically end up in the other drivers (since they are in shared code paths) and how much must be done on specific driver level?

How much of this work will automatically go into the software/virtualization drivers?

Comment

How much work to get it into the other drivers? I thought the OpenGL3 implementation was in the shared code and not specific drivers, so what's the ratio there? How much of the work will automatically end up in the other drivers (since they are in shared code paths) and how much must be done on specific driver level?

How much of this work will automatically go into the software/virtualization drivers?

1. A lot of it is in the GLSL compiler, which is shared.

2. A lot is in common Mesa code, which is shared.

3. A lot is in the Mesa state tracker, which is shared between Gallium drivers only.

4. And a lot is in driver specific code as well - for starters, the drivers now have be able to handle integers and pass those to the hardware correctly, which is going to be hardware specific.

Intel is working on #1 and #2. My impression is that #3 and #4 is close, but still pretty buggy and someone needs to finish that off. I don't know if that's going to happen for the 8.0 release or not.

The software paths will mostly work using the shared code in #3, and there is ongoing work to make sure that the driver specific parts are working as well.