From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262337AbTHUAds (ORCPT ); Wed, 20 Aug 2003 20:33:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262367AbTHUAds (ORCPT ); Wed, 20 Aug 2003 20:33:48 -0400 Received: from kweetal.tue.nl ([131.155.3.6]:26383 "EHLO kweetal.tue.nl") by vger.kernel.org with ESMTP id S262337AbTHUAdr (ORCPT ); Wed, 20 Aug 2003 20:33:47 -0400 Date: Thu, 21 Aug 2003 02:33:45 +0200 From: Andries Brouwer To: Jamie Lokier Cc: Andries Brouwer , Neil Brown , Vojtech Pavlik , linux-kernel@vger.kernel.org Subject: Re: Input issues - key down with no key up Message-ID: <20030821023345.A3204@pclin040.win.tue.nl> References: <20030815094604.B2784@pclin040.win.tue.nl> <20030815105802.GA14836@ucw.cz> <16188.54799.675256.608570@gargle.gargle.HOWL> <20030815135248.GA7315@win.tue.nl> <20030815141328.GA16176@ucw.cz> <16189.58357.516036.664166@gargle.gargle.HOWL> <20030821003606.A3165@pclin040.win.tue.nl> <20030820225812.GB24639@mail.jlokier.co.uk> <20030821015258.A3180@pclin040.win.tue.nl> <20030821000302.GC24970@mail.jlokier.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030821000302.GC24970@mail.jlokier.co.uk>; from jamie@shareable.org on Thu, Aug 21, 2003 at 01:03:02AM +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 21, 2003 at 01:03:02AM +0100, Jamie Lokier wrote: > So the decision must be: shall we do the wrong thing for keyboards > which report DOWN only (the key will appear stuck to some programs), > or shall we do the wrong thing for keyboards which report DOWN, no > repeat and then UP, by making it look like the key was released early? There are many more problems with your synthesized events. Look at your "repeat delay + a bit more". Can you specify how much "a bit more" is? In times of heavy disk activity we lose interrupts. Indeed, if I copy a CD image or untar a kernel tree my keyboard and mouse are dead for several seconds. There is no guaranteed "a bit more" within which we will see a keyboard event. If the only events that are seen are actual events, and on rare occasions we miss an event, that is not so bad. We just hit that key again. But if we synthesize events, then a missed key up causes autorepeat. In fact I see unwanted autorepeat - maybe once a day suddenly a single keystroke causes three to five identical characters to appear - but I am not sure what mechanism causes this. Andries