From: "Goede, J.W.R. de" <j.w.r.degoede@hhs.nl>
Subject: Re: problem with softraw and keycodes > 128
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Date: Fri, 08 Jun 2007 13:31:50 +0200
Message-ID: <web-68582106@hhs.nl>
In-Reply-To: <20070607191648.GC18372@suse.cz>
References: <4667C00D.40708@hhs.nl>
 <20070607131503.GA26905@suse.cz>
 <46681C5B.80201@hhs.nl>
 <20070607153639.GB5775@suse.cz>
 <466848F6.9010707@hhs.nl>
 <20070607191648.GC18372@suse.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1080
Lines: 35

On Thu, 7 Jun 2007 21:16:48 +0200
 Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Thu, Jun 07, 2007 at 08:05:42PM +0200, Hans de Goede
> wrote:
>  
> > This is an atkbd only setting, right, so indeed it
> doesn't affect USB, 
> > right?
> 
> Right, what I meant is that USB keyboards are affected by
> the very same
> problem you describe (163 in kernel will be 153 in X),
> and it can't be
> worked around by setting softraw to 0.
> 

Yes, I see I've been thinking about this some more and I 
tend to agree that doing the mapping at the kernel and
always represent an identical keyboard (fake)scancode wise,
is indeed the best way forward.

You said that someone at Suse is working on this, can you
disclose his mail address, I would like to help, atleast by
testing and I can probably do more then just that.

Thanks & Regards,

Hans


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