public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Matheus Izvekov <mizvekov@gmail.com>
Cc: linux-kernel@vger.kernel.org, dtor_core@ameritech.net
Subject: Re: usbkbd not reporting unknown keys
Date: Sat, 22 Apr 2006 20:54:02 +0200	[thread overview]
Message-ID: <20060422185402.GC10613@suse.cz> (raw)
In-Reply-To: <305c16960604221111u714bd3b1h2aeb0559b07d911b@mail.gmail.com>

On Sat, Apr 22, 2006 at 03:11:30PM -0300, Matheus Izvekov wrote:

> Hi, i started this thread a long time ago and still got no definitive
> response for it. Whats the position of you guys? Is it an issue worth
> a fix in mainline at all?

My opinion is that usbkbd serves as:

	a) an example usb/input driver
	b) for embedded systems where usbhid is too large

For keyboards with extra keys, use usb-hid.

-- 
Vojtech Pavlik
Director SuSE Labs

  reply	other threads:[~2006-04-22 18:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 19:30 usbkbd not reporting unknown keys Matheus Izvekov
2006-03-08 20:25 ` Matheus Izvekov
2006-03-08 20:47   ` Dmitry Torokhov
2006-03-08 21:34     ` Matheus Izvekov
2006-03-09 13:43       ` Dmitry Torokhov
2006-03-09 20:30         ` Matheus Izvekov
     [not found]           ` <305c16960603141510g72def22bmd0043d5f71d9ef6@mail.gmail.com>
2006-03-14 23:23             ` Matheus Izvekov
2006-04-22 18:11             ` Matheus Izvekov
2006-04-22 18:54               ` Vojtech Pavlik [this message]
2006-04-22 19:59                 ` Matheus Izvekov
2006-04-22 20:04                   ` Vojtech Pavlik
2006-04-22 21:01                     ` Matheus Izvekov
2006-04-22 21:53                       ` Vojtech Pavlik
2006-04-22 22:28                         ` Matheus Izvekov
2006-04-23  6:58                           ` Vojtech Pavlik
2006-04-23 14:00                             ` Matheus Izvekov
2006-04-23 14:16                               ` Vojtech Pavlik

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=20060422185402.GC10613@suse.cz \
    --to=vojtech@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mizvekov@gmail.com \
    /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