The largest part of the impact from the R3xx documentation will be in the 3D stack (mesa/mesa mostly, mesa/drm a bit) which is separate from radeonhd and radeon anyways. That said, most of what was traditionally thought of as "2D acceleration" (video, EXA etc..) now relies heavily on the 3D engine and the docs will also allow improvements there.
Since the radeonhd driver is aimed only at more recent chips (currently R5xx and up) you won't see R3xx/4xx work done directly in that driver, but any improvement made to the acceleration code in radeon will probably have some impact on radeonhd shortly afterwards. As an example, Alex was able to get full EXA Render working for the first time last night on R300, and that work is an important step towards providing the same functionality on R5xx and higher ASICs.
Since the radeonhd driver is aimed only at more recent chips (currently R5xx and up) you won't see R3xx/4xx work done directly in that driver, but any improvement made to the acceleration code in radeon will probably have some impact on radeonhd shortly afterwards. As an example, Alex was able to get full EXA Render working for the first time last night on R300, and that work is an important step towards providing the same functionality on R5xx and higher ASICs.
Comment