On Mon, 2009-04-06 at 10:10 -0700, Corbin Simpson wrote:
> Jakob Bornecrantz wrote:
> > On Mon, Apr 6, 2009 at 4:52 PM, José Fonseca <[email protected]> wrote:
> >> On Sat, 2009-04-04 at 04:02 -0700, Jose Fonseca wrote:
> >>> All the python state tracker requires is two functions: one that
> >>> creates a pipe_screen and another that creates a pipe_context. You can
> >>> implement these by provifing your version of  st_hardpipe_winsys.c,
> >>> and linking against the "pyst" library.  However, the python state
> >>> tracker  is headless (it does not know anything about X or any window
> >>> system). So for integrating it with a DRI-based driver you need to
> >>> include all the DRM/DDX glue code yourself...
> >>>
> >>> I can provide you skeleton code/SConscript that does the above.
> >> Pushed.
> 
> Rock. This looks awesome.
> 
> > If you used the drm_api_hooks structs this could be reused for all
> > drivers exporting that api.
> 
> Well, I'm going to have to tweak this a bit anyway, because r300 can't
> work with DRI1 due to limitations further down the line and glisse,
> airlied, and I agree that supporting DRI1 officially in Gallium just
> doesn't sound fun. But this is pretty cool.
> 
> I wonder if it makes sense to directly bind the Python stuff to drm_api
> rather than piggyback it on DRI2 or EGL...

What I'd like for the python binding is a) keep it OS independent; and
b) make it pluggable (i.e., load the hardware driver in runtime, rather
than having to link it in build time).

I thought that EGL drivers would give be a) and b), but after a quick
inspection it seems that EGL drivers imply a full Mesa driver. Not sure
if it is appropriate.

It seems what would be ideal is some sort of "gallium binary
interface...", at the statetracker<->pipe driver level.

Jose


------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to