public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <sboyce@blueyonder.co.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: 2.6.12 USB Keypad still not working
Date: Sun, 26 Jun 2005 03:17:07 +0100	[thread overview]
Message-ID: <42BE1023.90503@blueyonder.co.uk> (raw)
In-Reply-To: <20050624180854.542bb10c.akpm@osdl.org>

Andrew Morton wrote:
> Sid Boyce <sboyce@blueyonder.co.uk> wrote:
> 
>>PhoneSkype USB Phone SK-04.
>>It gets detected, is registered in /sys/bus/usb as a Keypad. Everything 
>>else USB works including the phone handset. Nothing is detected by 
>>showkey when keys are pressed.
>># less /sys/bus/usb/devices/usb3/3-2/3-2:1.3/interface
>>Keypad
>>
>>/dev/usb/hiddev? and /dev/input/keyboard say they are not valid devices 
>>and they are the ones created by the SuSE 9.3 install, not by udev.
>>
>>  From dmesg
>>  ----------
>>usbcore: registered new driver hiddev
>>drivers/usb/input/hid-core.c: timeout initializing reports
>>                               =============================
>>input: USB HID v1.10 Keyboard [BeyondTel USB Phone] on usb-0000:00:02.1-2
>>usbcore: registered new driver usbhid
>>drivers/usb/input/hid-core.c: v2.01:USB HID core driver
>>input: USB HID v1.00 Joystick [CH PRODUCTS CH FLIGHT SIM YOKE USB ] on 
>>usb-0000:00:02.1-1.1
>>input: USB HID v1.00 Joystick [CH PRODUCTS CH PRO PEDALS USB ] on 
>>usb-0000:00:02.1-1.4
>>I am puzzled by the fact that the keypad is recognised, but I cannot do 
>>anything with it.
>>
>># lsusb
>>Bus 003 Device 009: ID 04b8:0103 Seiko Epson Corp. Perfection 610
>>Bus 003 Device 008: ID 067b:3507 Prolific Technology, Inc.
>>Bus 003 Device 007: ID 068e:00f2 CH Products, Inc. Flight Sim Pedals
>>Bus 003 Device 006: ID 05e3:0760 Genesys Logic, Inc. Card Reader
>>Bus 003 Device 005: ID 03f0:0604 Hewlett-Packard DeskJet 840c
>>Bus 003 Device 004: ID 068e:00ff CH Products, Inc. Flight Sim Yoke
>>Bus 003 Device 003: ID 04b4:0303 Cypress Semiconductor Corp. <====
>>Bus 003 Device 002: ID 0451:2077 Texas Instruments, Inc. TUSB2077 Hub
>>Bus 003 Device 001: ID 0000:0000
>>Bus 002 Device 001: ID 0000:0000
>>Bus 001 Device 001: ID 0000:0000
>>
> 
> 
> Was this hardware known to work on ealier kernels?  If so, which?
> 
> 
No, I bought it recently and tried with from 2.6.12-rc6 onwards.
Regards
Sid.
-- 
Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot
Retired IBM Mainframes and Sun Servers Tech Support Specialist
Microsoft Windows Free Zone - Linux used for all Computing Tasks

  reply	other threads:[~2005-06-26  2:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 20:50 2.6.12 USB Keypad still not working Sid Boyce
2005-06-25  1:08 ` Andrew Morton
2005-06-26  2:17   ` Sid Boyce [this message]
2005-06-27 13:10   ` Sid Boyce
2005-07-10  2:21     ` Sid Boyce
  -- strict thread matches above, loose matches on Subject: below --
2005-06-26 12:21 Henk
2005-06-26 23:25 Sid Boyce

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=42BE1023.90503@blueyonder.co.uk \
    --to=sboyce@blueyonder.co.uk \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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