Matt Sealey wrote:

Basically you need to ask yourself: Who in my system has this information? Mesa certainly doesn't, but it sounds like somehow you want mesa to magically know about your window system. It doesn't & can't.


Right now, I think YOU expect Mesa magically knows, via dynamic
linking and kernel modules, neither of which we have :)

No, mesa can't know. You have to find a way to tell it.

I KNOW.


Question, again: What functions is Mesa providing that let me tell it,
that people are already using?

I know glResizeBuffersMESA() but I can't expect all apps to do this.
My only choice is context-specific functions?

Mesa has none. That's waaay beyond the scope of what Mesa does or can do. A huge chunk of the DRI-specific infrastructure is dedicated to just that task. We currently use a kernel driver for that. We "know" how many clients are using 3D by asking our kernel driver how many times its device file has been opened.


I think that if you can detect how many clients are using 3D you can probably also do the locking / shared memory technique.



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to