On Thu, Oct 20, 2016 at 10:46:11AM +0200, María Cano wrote: > >> HITACHI STARBOARD (DOESN’T WORK) > >> DIFF FOR cat /proc/bus/input/devices > >> > T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 12 Spd=12 MxCh= 0 > >> > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > >> > P: Vendor=10c4 ProdID=0661 Rev= 0.00 > >> > S: Manufacturer=SZiB0rdelectronics > >> > S: Product=IBOADDEVICE > >> > C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=300mA > >> > I:* If#= 0 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) > >> > E: Ad=81(I) Atr=03(Int.) MxPS= 32 Ivl=1ms > >> > E: Ad=02(O) Atr=03(Int.) MxPS= 8 Ivl=1ms > >> > >> DIFF FOR cat /proc/bus/input/devices > > > > That looks like /sys/kernel/debug/usb/devices, not input/devices. Which > > is fine :) > > > > That looks like it is going to take a "vendor-specific" driver to > > communicate with it. If you can get the specs from the vendor, we will > > be glad to help you out with writing a driver for it, but without that, > > or a bunch of reverse engineering effort, it's probably not going to be > > possible :( > > > Ok, I'll try to contact with the seller and the manufacturer, let's > see if we are lucky. Great! > >> HITACHI STARBOARD (DOESN’T WORK) > >> DIFF FOR cat /proc/bus/input/devices > >> > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 > >> > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > >> > P: Vendor=1477 ProdID=0008 Rev=13.13 > >> > S: Manufacturer=eIT-Xiroku > >> > S: Product=Optical Touch Sensor HTM131 > >> > S: SerialNumber=002302314034 > >> > C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA > >> > I:* If#= 0 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) > >> > I: If#= 0 Alt= 1 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) > >> > E: Ad=82(I) Atr=01(Isoc) MxPS= 900 Ivl=1ms > >> > > >> > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 2 Spd=1.5 MxCh= 0 > >> > >> > >> DIFF FOR cat /proc/bus/input/devices > > > > Again, that's the usb devices file. > > > > And why the odd blank line? Are you sure you didn't miss some lines > > there? > > > > Anyway, a device with only one isoc endpoint seems really odd, is this a > > camera? > > > I don't know what tecnology it uses, but it is possible it is a > camera, look at the top of the whiteboard: > http://www.hitachistarboard.us/hitachi-fx-trio-77-inch-whiteboard.html Hm, or, worst case, it might move the logic of trying to determine where the user is touching to the host computer, running software to turn the camera into an input device. That's going to be messy :( > >> MULTICLASS (DOESN’T WORK) > >> DIFF FOR cat /proc/bus/input/devices > >> > T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 7 Spd=12 MxCh= 0 > >> > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > >> > P: Vendor=10c4 ProdID=ea60 Rev= 1.00 > >> > S: Manufacturer=Silicon Labs > >> > S: Product=CP2102 USB to UART Bridge Controller > >> > S: SerialNumber=0001 > >> > C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA > >> > I:* If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=cp210x > >> > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > >> > E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms > >> > >> DIFF FOR cat /proc/bus/input/devices > > > > Look, the serial driver bound to it properly! So there is hope, now you > > just need to have some userspace program to talk to the device, as it is > > now being exported by the kernel as a "normal" serial port. > > > > That's again going to be hard without some specs from the manufacturer > > on how to talk to the device. > > > > Ok, I'll try to get more information about specs, but what exactly I > have to ask? We need to know: - the protocol the device uses in order to communicate with the host computer in order to properly detect and control the device. good luck! greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
