Michel Dänzer <[EMAIL PROTECTED]> writes:
> On Sun, 2005-02-06 at 19:32 +0500, Dimitry Naldayev wrote:
>> Michel Dänzer <[EMAIL PROTECTED]> writes:
>>
>> > FWIW, the infamous radeon DRI reinit patch is at
>> > http://penguinppc.org/~daenzer/DRI/radeon-reinit.diff
>> >
>> look like it is realy not best way do things right...
>>
>> so couple of questions:
>> 1) what happens when we do vt switch?
>
> You mean with this patch? If there are no clients using the DRM, the DRI
> is de-initialized and re-initialized again on return to the X server.
NO, I am not about the patch...
I am about the X server and drm module --- what happens when we do vt
switch? How this event dispatched? what parts of code I need to look to
understand this?
>
>> 2) what differences between vt switch and context switch from hardware/drm
>> point of view?
>
> None, really. Without this patch (and even with it if there are clients
> using the DRM), the X server simply holds the hardware lock while
> switched away to prevent clients from touching the hardware.
>
No, I am not about this. X server holds hardware lock becouse drm not ready
to share hardware between different X sessions... but why?
See my logic:
first case:
1) we have window and render OpenGL inside it. DRM manage OpenGL data to
hardware...
2) now we HIDE the window by other window. Are the OpenGL data will go to
hardware? No, becouse the OpenGL window hiden...
Second case:
1) we have window and render OpenGL inside it. DRM manage OpenGL data to
hardware...
2) now we do vt switch...
What differences between first and second cases? why X server need to hold
lock on hardware? Why DRM cannot manage second case as it manage first one?
What we need to add to DRM for this?
--
Dimitry
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
