Hi!
Ok, I'll try to make a (short) summary. Andreas wanna deal with this whole issue by informing the userspace via a ping-pong mechanism based on sending signals between kernel space (KGI) and userspace (GGI application and/or GGI's kgi-target). Fabio wanna deal with this whole issue by locking/unlocking the critical areas (MMIO-, framebuffer-, Overlay-areas) using either interprocess mutexes (semaphores using shared memory - kernellevel mutexes are also thinkable, but I don't know, if such things really exists accessable from userspace). I think, the most robust and most efficient way is to try to combine BOTH ways. I mean using mutexes AND signals. -- CU, Christoph Egger E-Mail: [EMAIL PROTECTED] +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr f�r 1 ct/ Min. surfen!
