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.

What about r600g?
And more general question:
Who in AMD tell FLOS gpu driver devs what to focus on? Is it self-organizing work? Or there are some strong guidelines from above (like get X for Y familly of chips..)

What about r600g?
And more general question:
Who in AMD tell FLOS gpu driver devs what to focus on? Is it self-organizing work? Or there are some strong guidelines from above (like get X for Y familly of chips..)

ISA of R600 chips makes supporting OpenCL completely extremely difficult.
But SI works in a more developer-friendly fashion.
Personally I prefer a complete SI compute support rather than two broken ones (Evergreen and SI), considered the insufficient manpower of OSS radeon team.

What about r600g?
And more general question:
Who in AMD tell FLOS gpu driver devs what to focus on? Is it self-organizing work? Or there are some strong guidelines from above (like get X for Y familly of chips..)

r600g has had this basic compute support for a while now. It's available in Evergreen and newer chips (Radeon 5000 series and higher). Radeon 4000-series and lower are missing some of the required hardware features, so I'm not sure what the current status is (I sold my last 4770 a while ago). Maybe the 4000-series has partial support...

Some of the developers, such as Tom Stellard who wrote these patches, are AMD employees. I'm assuming that they are told what to focus on (or they get to choose projects that their managers approve of... *shrug*). The others who aren't AMD employees get to work on whatever they want. In my case, I volunteer some of my free time working on OpenCL unit tests for clover (found in Piglit). I do it to scratch an itch, but everyone gets to benefit.