Indeed. I think that taking the API from ARB_vbo makes these different
implementations entirely possible. The implementation I am interested in right
now is the AGP one, but don't take that to imply that other implementations and
backends are excluded.
I've tried to provide exactly the seperation that I think you're talking about
by sticking closely to the buffer_object semantics from ARB_vbo/ARB_fbo for the
interface.
Ok, I'm not familiar with those semantics (as I'm not too familiar with
such high-level things as OpenGL :) but I'll try to have a look one of
these days).
It's usually very worthwhile to track down the GL extension that exposes the HW
functionality in question - the extensions have been written by people who have
already implemented whatever problem you're considering, usually on multiple
systems, so they often contain a wealth of distilled knowledge applicable to the
lowlevel design.
Keith
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
