linux-kernel - Re: Keys get stuck

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080314182407.GA6990@ucw.cz>
Date:	Fri, 14 Mar 2008 19:24:08 +0100
From:	Pavel Machek <pavel@....cz>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	David Newall <davidn@...idnewall.com>,
	"Fred ." <eldmannen@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: Keys get stuck

On Fri 2008-03-14 10:21:29, Jiri Kosina wrote:
> On Thu, 13 Mar 2008, Pavel Machek wrote:
> 
> > No.
> > hw is proper place to implement autorepeat, and along with some 
> > buffering, it has chance to work. Kernel is not real-time, and X are 
> > definitely not real-time, while autorepeat is real-time operation.
> > It actually mostly works in ps/2 case. Buffer in hardware means that 
> > pretty big interrupt delays can be tolerated without problems.
> 
> That's true. Unfortunately USB keyboards don't behave this way and there 
> is nothing we can do about that.

Maybe. (Could we get host controller to effectively timestamp usb
packets for us?)

..but that is not a problem here, because X are broken even on ps/2
keyboards. USB keyboards may be misdesigned, but they are not responsible
for problems we see.
							Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/