lkml.org 
[lkml]   [2003]   [Sep]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Input issues - key down with no key up
Hi!

> > > There is only one solution which works well that I can see: do the
> > > forced-up thing by default, but as soon as you see a real UP event
> > > from a key, disabled forced-up _for that key_ in future.
> >
> > Won't work. There are keyboards that forget to send a key up event
> > sometimes. They usually send it, but from time to time they don't.
> > We need to cover these keyboards, too. It's actually the main reason for
> > the whole forced up thingy.
>
> :( That's a shame, and a peculiar bug too. Then I agree that
> forced-up is needed all the time, if we do not know what triggers the
> keyboard to forget to send one or have any way to detect it.

Can we at least report keyboard as broken to the syslog?
Its usefull if we want manufacturers to eventually fix
their hw (and its extremely usefull when someone gives
you pre-production hw "see if you can break it")
Pavel
--
Pavel
Written on sharp zaurus, because my Velo1 broke. If you have Velo you don't need...

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:48    [W:0.117 / U:0.036 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site