Sid Boyce <[EMAIL PROTECTED]> wrote: > > Andrew Morton wrote: > > Sid Boyce <[EMAIL PROTECTED]> wrote: > > > >>Andrew Morton wrote: > >> > >>>Sid Boyce <[EMAIL PROTECTED]> 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? > >>> > >>> > > > > > > Is this working OK now? > > > > If not, I think a fresh report is needed - please cc > > linux-usb-devel@lists.sourceforge.net, thanks. > > > > > > > Sadly no, the problem is still the same with up to 2.6.13-rc3-git9. I've > had a look around the skypejournal site and found some stuff suggesting > user space tools may be needed, the example program at > http://share.skype.com/developer_zone/documentation/skype_api_for_linux/ > skype-dbus-testclient-20050422.tar.bz2 does not build. > barrabas:/ftp/jul05/skype.dbus # make > g++ -c -pipe -Wall -W -g -DDBUS_API_SUBJECT_TO_CHANGE -ggdb -DQT_SHARED > -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -I/usr/lib/qt3/mkspecs/default -I. > -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include > -I/usr/lib/qt3/include -I.ui/ -I.moc/ -o .obj/main.o main.cpp > Assembler messages: > FATAL: can't create .obj/main.o: No such file or directory > make: *** [.obj/main.o] Error 2 > > Although all the signs are that it is detected, YaST hardware info does > not report it and it doesn't bind to a device.
OK, but I still don't understand whether this is an actual regression. Did that device work OK under any earlier kernel? If so, which one(s)? Thanks. ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
