>> I don't think the correct solution would be for X and the console to >> directly speak to each other like X saying to the console client "stop >> please", but rather a per-ressource (VGA, keyboard, mouse) way to say >> "I want exclusive access to this ressource". The console client itself >> would just agree to give to the access to X, or something like that.
> Ah, ok. IIRC last time we discussed this I proposed something like having > the userspace drivers as translators that either block a second process > from accessing them, or queue the requests somehow. that would be the best way to do it IMHO :) > My idea was to implement the driver in userspace and force X to use it. > Following this dessign, we could end up seeing X running as non-root. That would require a huge amount of work I fear, especially if we want to support hardware acceleration at the end (like xvideo or dri), but I agree it's the best long-term solution. > What we could do is writing the keyboard, vga etc translators, but don't > implement the actual hardware I/O on them yet. Instead, just use them for > resource management. I was thinking about something like that too, at least until we move to L4 (implementing user-space drivers on top of Mach is tricky). -- Gael Le Mignot "Kilobug" - [EMAIL PROTECTED] - http://kilobug.free.fr GSM : 06.71.47.18.22 (in France) ICQ UIN : 7299959 Fingerprint : 1F2C 9804 7505 79DF 95E6 7323 B66B F67B 7103 C5DA Member of HurdFr: http://hurdfr.org - The GNU Hurd: http://hurd.gnu.org _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
