Re: DRI and vt switching?

2004-09-30 Thread Keith Whitwell
Alan Cox wrote: On Iau, 2004-09-30 at 13:56, Keith Whitwell wrote: Looking in the i810 driver, it seems like the ringbuffer is flushed and disabled until the X server calls EnterVT again, and AGP memory is unbound. How is the client generally notified about this? The server holds the hw lock until

Re: DRI and vt switching?

2004-09-30 Thread Alan Cox
On Iau, 2004-09-30 at 13:56, Keith Whitwell wrote: > > Looking in the i810 driver, it seems like the ringbuffer is flushed and > > disabled until the X server calls EnterVT again, and AGP memory is > > unbound. How is the client generally notified about this? > > The server holds the hw lock until

Re: DRI and vt switching?

2004-09-30 Thread Thomas Hellström
> Thomas Hellström wrote: >> Hi! >> >> How is VT switching normally handled when a DRI client is active? >> Meaning, for example, switching from the X display to a virtual text >> console? >> >> Looking in the i810 driver, it seems like the ringbuffer is flushed and >> disabled until the X server c

Re: DRI and vt switching?

2004-09-30 Thread Keith Whitwell
Thomas Hellström wrote: Hi! How is VT switching normally handled when a DRI client is active? Meaning, for example, switching from the X display to a virtual text console? Looking in the i810 driver, it seems like the ringbuffer is flushed and disabled until the X server calls EnterVT again, and AG

DRI and vt switching?

2004-09-30 Thread Thomas Hellström
Hi! How is VT switching normally handled when a DRI client is active? Meaning, for example, switching from the X display to a virtual text console? Looking in the i810 driver, it seems like the ringbuffer is flushed and disabled until the X server calls EnterVT again, and AGP memory is unbound. H