Date: Mon, 18 Aug 2003 13:53:49 +0200 (MET DST)
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
To: John Bradford <john@grabjohn.com>
cc: jamie@shareable.org, aebr@win.tue.nl, linux-kernel@vger.kernel.org,
       neilb@cse.unsw.edu.au, vojtech@suse.cz
Subject: Re: Input issues - key down with no key up
In-Reply-To: <200308161515.h7GFFeUS000159@81-2-122-30.bradfords.org.uk>
Message-ID: <Pine.GSO.3.96.1030818134629.12013A-100000@delta.ds2.pg.gda.pl>
Organization: Technical University of Gdansk
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1265
Lines: 30

On Sat, 16 Aug 2003, John Bradford wrote:

> > What are the known problems with mode #3, then?
> 
> It's poorly implemented by a lot of keyboards.

 Specifically, it wasn't used much at the beginning (see e.g. when we came
to trying it -- it's already ~15 years since it was introduced) and then
the crapware era began and some manufacturers stopped taking care of less
commonly used standard functionality. 

> Has anybody actually verified that the keyboards that are presenting
> the problem in quesiton are not specifically identifyable by their ID
> string, or some other means - E.G. they only exist on specific, known
> laptops?

 I recall testing an i486 laptop around 1996 and not only it accepted
switching mode to #3, but it reported it as being active then as well. 
Yet it generated #2 codes regardless... 

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

-
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/