openChrome which you refference to (http://openchrome.org/) is just a DDX driver and it's responible for managing modes (resolution, refresh rate), displays (CRTCs, PLLs, etc.) and 2D plus Xv acceleration. It contains some single 3D bits, but it's not responsible for rendering anything.
For 3D acceleration you need:
1) single bits in DDX driver
2) DRM module
3) Mesa 3D driver (may be Gallium)
Situation for pre-Chrome 9:
1) We have working DRM module (called via) and Mesa 3D driver (called unichrome) but both are in poor state. 3D applications works but not really stable and feature-complete.
2) Thomas is working on new DRM module (openchrome) and new Mesa 3D driver (also called openchrome for now). It's already usable but AFAIK still needs some little work before going mainline.
Situation for Chrome 9:
VIA submitted patches to kernel to add support for Chrome 9 in old "via" kernel DRM module. As we have now better "openchrome" DRM module it would be nice to port VIA patches to this new openchrome DRM module.
If my knowledge is up to date, there is not 3D Mesa driver for Chrome 9. I can found two messages referencing to that:
and reply to this:following would be needed:
3) A new chrome9 3D driver. Preferrably based on gallium. I don't think
anybody in the open source community is working on this. Is VIA doing
any efforts in this direction?We prefer the G3D for Chrome9 too but we have few information about G3D. Based on your full experience, it will be appreciated if you can give us the guideline for the developing.
EXA acceleration (one supporting RENDER) let you use some nice (composite) 2D effects. It doesn't mean any 3D support and you won't get 3D effects working with just EXA (you need Mesa 3D driver).