public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Goede, J.W.R. de" <j.w.r.degoede@hhs.nl>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with softraw and keycodes > 128
Date: Fri, 08 Jun 2007 13:31:50 +0200	[thread overview]
Message-ID: <web-68582106@hhs.nl> (raw)
In-Reply-To: <20070607191648.GC18372@suse.cz>

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



      reply	other threads:[~2007-06-08 11:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07  8:21 problem with softraw and keycodes > 128 Hans de Goede
2007-06-07 13:15 ` Vojtech Pavlik
2007-06-07 14:55   ` Hans de Goede
2007-06-07 15:36     ` Vojtech Pavlik
2007-06-07 18:05       ` Hans de Goede
2007-06-07 19:16         ` Vojtech Pavlik
2007-06-08 11:31           ` Goede, J.W.R. de [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=web-68582106@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox