Today I got mesa-solo to work with the new interface unichrome driver.

GLXDrawable is used by MiniGLX and __DRIdrawable is used by the driver.
__DRIid is used as a hash key to lookup __DRIdrawable in dri_util.c.

Jon, perhaps we should sync up our work on mesa-solo.

Thanks,
Erdi


Jon Smirl wrote:
I'm trying to fix up mesa-solo. I'm working on glXMakeCurrent.

In bindContext3 the drawable/readable are GLXDrawable. In X these are
XID's so they match with __DRIid. In miniglx GLXDrawable is a pointer.
Why  does un/bind take __DRIid instead of __DRIdrawable?

Should X call __driFindDrawable() before calling un/bind so that it can
pass in pointers too?


===== Jon Smirl [EMAIL PROTECTED]




__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to