Re: [Dri-devel] reinit-0-0-1-branch ready for merge on trunk

[Michel <mi...@da...>]

On Don, 2002-08-29 at 23:47, Alan Hourihane wrote:=20
>=20
> A more architectural view needs to be taken on how this operates
> with other chipsets and remove the whole dependency of doing this
> to every driver.

After some thinking, something along these lines might work:

If a driver can support reinit (i.e. it can deal with the DRI getting
disabled and enabled again), it calls a DRI support function to register
hooks for disabling and enabling. The DRI wraps the EnterVT() and
LeaveVT() functions and calls those hooks in its wrapper functions.

Would that be any better than the current implementation? It would still
require about the same amount of code to be added to each driver, but on
top of that it would introduce a dependency on a certain version of the
DRI library, and it's not guaranteed to work with all drivers (they
might have different ordering constraints in the VT switching
functions).


So, do we absolutely have to wait until one day, someone figures out an
elegant way to unify all of suspend/resume, DRI on multiple displays
(both with clients running everywhere at the same time) and reinit? Or
can't we have the latter now, and then fold it into the rest on that
fine day? It satisfies my needs now, and I can hardly believe that they
are my needs alone.


--=20
Earthling Michel D=E4nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast