I have to visit other school where I work too, but here is a summary of datas found related with the whiteboard we have. I have to say It is a summary because we have several whiteboards that are apparently made by the same manufacturer and get exactly the same output device so internally work with the same chips (even if they have different colors and stickers :-). I tested with the last kernel in kernel.org and to my surprise, there are several whiteboards that work with this kernel out of the box and not the one we were using. Ok, here is the output of whiteboard doesn't work (It seems only whiteboards are working have output in the diff for cat /proc/bus/input/devices): 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 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 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 2016-10-13 14:06 GMT+02:00 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>: > A: http://en.wikipedia.org/wiki/Top_post > Q: Were do I find info about this thing called top-posting? > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > A: No. > Q: Should I include quotations after my reply? > > http://daringfireball.net/2007/07/on_top > > On Thu, Oct 13, 2016 at 01:57:54PM +0200, María Cano wrote: >> Okay, I will collect the following information: >> >> 1) Plugging and unplugging USB diff with: cat /sys/kernel/debug/usb/devices > > Yes. > >> 2) Plugging and unplugging USB diff with: cat /proc/bus/input/devices > > Yes. > >> 3) What can I do to know for sure that the system sees the device as a >> serial device? > > We should be able to determine that from step one above. > > thanks, > > 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
