I've been experimenting with using the software autorepeat functionality in
drivers/input/input.c and have the problem that it autorepeats all EV_KEY
reported events, this includes mouse buttons etc. which for a combined
mouse/keyboard device is undesirable. I appreciate that I could override th
On Tue, 12 Feb 2008, Jiri Kosina wrote:
On Tue, 12 Feb 2008, Timo Aaltonen wrote:
If all the events are seen by evtest, then everything is fine on the
kernel side and you should just tweak your X configuration.
hmm, but X doesn't allow key-id's >255, so I can only wait until they support
more
On Tue, 12 Feb 2008, Timo Aaltonen wrote:
> > If all the events are seen by evtest, then everything is fine on the
> > kernel side and you should just tweak your X configuration.
> hmm, but X doesn't allow key-id's >255, so I can only wait until they support
> more? (maybe in X.org R7.5..)
You ne
Jiri Kosina wrote:
That is OK. But you shouldn't run into the situation when you run out of
the free evdev devices.
Seems indeed to be a misinterpretation on my side.
I add a few debug statements, and it seems that although the event
device kernel name increases, they still reference the sam
On Tue, 12 Feb 2008, Jiri Kosina wrote:
On Tue, 12 Feb 2008, Timo Aaltonen wrote:
yes. Could you please grab reasonably recent kernel
(2.6.24-rc would be ok), compile it with CONFIG_HID_DEBUG,
modprobe the 'hid' module with 'debug=1' parameter, and send me the
output from the time you connect
On Tue, 12 Feb 2008, Timo Aaltonen wrote:
> > > yes. Could you please grab reasonably recent kernel
> > > (2.6.24-rc would be ok), compile it with CONFIG_HID_DEBUG,
> > > modprobe the 'hid' module with 'debug=1' parameter, and send me the
> > > output from the time you connect the keyboard and
Jiri Kosina wrote:
On Tue, 12 Feb 2008, Erik Slagter wrote:
Negative ;-)
A few moments ago I rebooted with HAL disabled and without going into X. I
unplugged the hub that has the mouse and keyboard attached and plugged it back
in again, a few times. Once again every time higher event handlers w
On Tue, 12 Feb 2008, Erik Slagter wrote:
> > this is very likely bug in HAL -- please see
> > https://bugzilla.novell.com/show_bug.cgi?id=344872
> Negative ;-)
> A few moments ago I rebooted with HAL disabled and without going into X. I
> unplugged the hub that has the mouse and keyboard attached
Jiri Kosina wrote:
On Mon, 11 Feb 2008, Erik Slagter wrote:
Symptoms: when I remove (unplug) a USB keyboard or mouse, the
corresponding event device seems to be closed but not released; when I
plug the device back in, it gets a new input device handle. This means
that after several suspend/re
