Among the R600g commits hitting the Mesa tree overnight in Toulouse were the pre-requisites for being able to move to pipe-buffer kernel object buffer managers, then the hundreds of lines of new code to use the pipe-buffer manager rather than using kernel buffer objects directly, support for winsys buffer object caching (with vertex/index/constant buffer objects), and support for the upload manager for uploading user VBOs (Vertex Buffer Objects) and index buffers. The upload manager support in R600g should provide quite a speed improvement for a number of OpenGL games/applications, such as those using the ioquake3 engine.
Details and the code changes can be found by examining the Mesa log.
While the R600g driver is not yet on the same level as the R600 classic Mesa driver or that of the R300g driver (the Gallium3D implementation for ATI GPUs up through the Radeon X1000 series), it is slowly but surely reaching such a state.
One XDS item worth mentioning is that when talking to AMD's Alex Deucher two days ago in Toulouse, they will continue work on bringing up and stabilizing the ATI Radeon HD 5000 "Evergreen" series support in the classic Mesa R600 driver even though support for Evergreen has already been added to Gallium3D. As the R600g driver isn't yet at a state to takeover the R600 classic Mesa driver and AMD wanting open-source Radeon HD 5000 series OpenGL acceleration working in the next round of updates, they'll continue for this series on the duplicated effort of implementing the acceleration code in both drivers. Moving forward though -- like with the AMD Radeon HD 6000 series and Fusion -- we should see Gallium3D-only support.