On Sun, Jun 17, 2001 at 12:08:42AM +0200, EJ wrote: > >> That's true. But, that's why I asked why you use usb_get_report, but > >> not usb_set_report. > vp>Maybe usb_get_report should be handled the same way, but there wasn't a > vp>need for that yet. Also the sync approach makes life much simpler. > > Yes; it makes debugging a lot easier. I know what to do (in the order > of usb_set_report parameters), but I'd like to do it from userspace. I > can dump the reports coming from the usb_get_report, but not from the > reverse (that is, I haven't found where the bytes are actually sent). > > >> Well, this is what I see: > >> Jun 16 22:26:06 dwarf kernel: hid-core.c: reading report type 1 id 1 failed len 4 >read 0 > vp>> > >> If I change the logic in hid_read_report to use 'my' logic, I get > >> valid reports out of it... > vp>Are you sure the reports are valid? My UPS and mouse and keyboard and > vp>other devices, except for a Saitek joystick all return with the correct > vp>data length of transferred data. The Saitek joystick returns 1, while it > vp>should return 11. > > Well; a 0 size is not what you'd expect for a size (at least, I > don't). But, <drumroll> your code, unpatched works without complaining > about invalid length reports. <This is where I really don't understand > what happened...> > > vp>Oh, I meant the interface/endpoint descriptors in /proc/bus/usb/devices. > vp>Thanks for the report descriptor dump, too. > > ok, here's the interface/endpoint descriptor output. > > T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 > B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 > D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=0000 ProdID=0000 Rev= 0.00 > S: Product=USB UHCI Root Hub > S: SerialNumber=e000 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=08ca ProdID=0020 Rev= 1.00 > S: Manufacturer=AIPTEK > S: Product=APT-6000U > C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 50mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=hid > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl= 3ms Thanks. This looks quite normal. > vp>By the way, looking at the report descriptor below, hid-input.c should > vp>be able to handle this device and generate input events for it. Does it? > vp>Did you try evtest? > > Yes, but you have to run it on an event device (maj 13, min 64) right? > But it returns "evtest: No such device". You probably didn't load/compile in evdev.o? > Also, I need access to the > Feature mentioned in the Application(Digitizer.Digitizer), so I can > set some features of the tablet. You should be able to do that even through the input interface. If it doesn't work, then it should be fixed/added. What stuff is that? > However, I've seen events from the device when I used it statically > linked to the kernel, at the same time using my logitech usb mouse > (conviniently attached to the ps/2 port now). > > Then the evtest app works. Does it give sensible data? -- Vojtech Pavlik SuSE Labs _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: http://lists.sourceforge.net/lists/listinfo/linux-usb-devel
