On Thu, Feb 01, 2007 at 06:37:12PM +0100, Markus Armbruster wrote:
> Gerd Hoffmann <kraxel@xxxxxxx> writes:
>
> > Hi,
> >
> > This patch creates two separate input devices for keyboard and mouse
> > events. The reason for this is to separate them in the linux input
> > layer and allow them being routed different ways.
> >
> > Use case: Configure the X-Server like this to get the mouse
> > events directly from the linux input layer, which has the major
> > advantage that absolute coordinates work correctly:
> >
> > Section "InputDevice"
> > Driver "evdev"
> > Identifier "Mouse[1]"
> > Option "Device" "/dev/input/event<nr>"
> > EndSection
> >
> > This makes the keyboard stop working though in case mouse and
> > keyboard events are coming through the same input device.
> >
> > please apply,
>
> I tried it out. With the configuration sketched above, I get a
> working keyboard and mouse, and the mouse behaves much better than
> before. However, with the default configuration, the mouse doesn't
> work at all.
Yes, if the current Xorg server automatic configuration doesn't 'just work'
for both keyboard and mouse then applying this patch is a non-starter.
Is there some way we can keep the original device supplying both keyboard
and mouse events as before, and just have this second device as an opt-in
'absolute pointer' event device. That way existing Xorg setups will still
work correctly without needing any config changes, while providing the
ability to opt-in to getting absolute events by adding the extra config.
Ideally Xorg hardware probing could then be modified, so that future Xorg
releases would automatically utilize the extra device (if present) for
absolute co-ords without needing the extra config at all.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|