mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Hards <bhards@bigpond.net.au>
To: Josh Litherland <fauxpas@temp123.org>, Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB Keypad
Date: Fri, 19 Jul 2002 13:36:02 +1000	[thread overview]
Message-ID: <200207191336.02403.bhards@bigpond.net.au> (raw)
In-Reply-To: <20020719032008.GA22934@temp123.org>

On Fri, 19 Jul 2002 13:20, Josh Litherland wrote:
> On Thu, Jul 18, 2002 at 08:10:00PM -0700, Greg KH wrote:
> > Should work just fine today.  What kind of problems do you have when you
> > try to do it?
>
> Just not getting any events from the keypad.  When I load up evdev, and
> cat the device I get the appropriate gibberish, so the device is
> detected okay.  This is 2.4.18, if that makes a difference for the
> purposes of this discussion.
OK, evdev is on the userspace side of the input core (and USB is on the other).
If evdev reports events (and you can decode them, if you are interested, using
tools available from the linuxconsole CVS), then all is probably well with USB and
the input core.

The obvious error would be not compiling in the input layer keyboard driver (or
not loading the module, whatever). 

If that definately isn't wrong (like lsmod shows the module, or a normal USB
keyboard works fine and the keypad doesn't), then we'll likely need the 
HID descriptors. Probably easiest to get them from evdev using the evtest
tool from linuxconsole CVS.

Brad

-- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.

  parent reply	other threads:[~2002-07-19  3:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-19  1:52 Josh Litherland
2002-07-19  3:10 ` Greg KH
2002-07-19  3:20   ` Josh Litherland
2002-07-19  3:24     ` Greg KH
     [not found]       ` <20020719033005.GA23021@temp123.org>
2002-07-19  3:35         ` Greg KH
2002-07-19  3:36     ` Brad Hards [this message]
2002-07-19  3:50       ` Josh Litherland
2026-07-06 19:55 dave

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=200207191336.02403.bhards@bigpond.net.au \
    --to=bhards@bigpond.net.au \
    --cc=fauxpas@temp123.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome