Date: Sun, 14 Sep 2003 12:34:44 +0200
From: Andries Brouwer <aebr@win.tue.nl>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
       Zwane Mwaikambo <zwane@linuxpower.ca>, vojtech@suse.cz,
       linux-kernel@vger.kernel.org
Subject: Re: Another keyboard woes with 2.6.0...
Message-ID: <20030914123444.D3371@pclin040.win.tue.nl>
References: <2F284368A@vcnet.vc.cvut.cz> <20030913205244.A3295@pclin040.win.tue.nl> <20030913214047.GF8973@vana.vc.cvut.cz> <20030914121323.B3371@pclin040.win.tue.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030914121323.B3371@pclin040.win.tue.nl>; from aebr@win.tue.nl on Sun, Sep 14, 2003 at 12:13:23PM +0200
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 913
Lines: 24

On Sun, Sep 14, 2003 at 12:13:23PM +0200, Andries Brouwer wrote:

> > From log it looks like that switch likes 0x41 a lot: it reports ID 0x41AB,
> > it reports current scan set 0x41, and when we enable it, it returns spurious
> > 0x41... And the last 0x41 is one which confuses everything.
> 
> Yes. ID is OK. Scancode set is OK. But the final one is unexpected.
> 
> You say "confuses everything".
> Is it not treated as a keypress for the F7 key?

Hmm. Yes. An F7 that is never released.
Is that what you see - an infinitely repeated F7 until
you hit the next key?

And the 0x41 is generated by this switch?

And it also occurs on 2.4 but there nothing bad happens?

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