Re: [gdm-list] Multi-seat and multi-display support design
- From: Ray Strode <halfline gmail com>
- To: Halton Huo <Halton Huo sun com>
- Cc: gdm-list gnome org
- Subject: Re: [gdm-list] Multi-seat and multi-display support design
- Date: Thu, 12 Mar 2009 23:14:25 -0400
Hi,
> On Tue, 2009-03-10 at 10:14 -0400, Ray Strode wrote:
>> So, one thing X development has been trying to do over the last few
>> years is get rid of the need for xorg.conf. The keyboard and mouse
>> sections are all evdev these days.
>>
>> I think we need consolekit to associate a usb hub, keyboard, mouse,
>> etc with the session independently from xorg.conf. That's the only
>> way you're going to get sane behavior with hot plugged devices
> Ray,
>
> Could you give a example for Xorg command with specify KPVS?
I don't think there's an out of the box way to do this yet. It's
going to need some changes.
Right now X asks HAL about what keyboards and mice are on the system,
and HAL tells it which driver to load (where the driver is normally
always "evdev").
HAL tells X any time a new keyboard or mouse gets plugged in. If
there are multiple X servers running on the different VTs, only the X
server on the active vt will have the input devices open. When you
switch VTs the old vt's X server closes its device fds and the new
vt's X server opens them.
In a multiseat world, we want the X server for a given seat to only
open the devices that belong to that seat. ConsoleKit is the registry
of seat information, so the X server may need to be changed to query
ConsoleKit.
--Ray
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]