diff --git a/unsupported/primax-colorado-2400u.html b/unsupported/primax-colorado-2400u.html new file mode 100644 index 00000000..3824e0da --- /dev/null +++ b/unsupported/primax-colorado-2400u.html @@ -0,0 +1,159 @@ + + + +
++ Primax Colorado 2400u +
++ USB +
++ 0x0461 +
++ 0x0346 +
++ ASIC EICI 10440A +
++ Maybe it works with the viceo backend? +
++<device descriptor of 0x0461/0x0346 at 001:002> +bLength 18 +bDescriptorType 1 +bcdUSB 1.00 +bDeviceClass 0 +bDeviceSubClass 0 +bDeviceProtocol 0 +bMaxPacketSize0 8 +idVendor 0x0461 +idProduct 0x0346 +bcdDevice 0.01 +iManufacturer 2 ((null)) +iProduct 1 ((null)) +iSerialNumber 0 () +bNumConfigurations 1 + <configuration 0> + bLength 9 + bDescriptorType 2 + wTotalLength 32 + bNumInterfaces 1 + bConfigurationValue 1 + iConfiguration 0 () + bmAttributes 64 (Self-powered) + MaxPower 48 mA + <interface 0> + <altsetting 0> + bLength 9 + bDescriptorType 4 + bInterfaceNumber 0 + bAlternateSetting 0 + bNumEndpoints 2 + bInterfaceClass 16 + bInterfaceSubClass 1 + bInterfaceProtocol 0 + iInterface 0 () + <endpoint 0> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x81 (in 0x01) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 + <endpoint 1> + bLength 7 + bDescriptorType 5 + bEndpointAddress 0x02 (out 0x02) + bmAttributes 2 (bulk) + wMaxPacketSize 64 + bInterval 0 ms + bRefresh 0 + bSynchAddress 0 +found USB scanner (vendor=0x0461, product=0x0346) at libusb:001:002 + +T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 +D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 +P: Vendor=0461 ProdID=0346 Rev= 0.01 +S: Manufacturer=Primax +S: Product=USB Scanner +C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 48mA +I: If#= 0 Alt= 0 #EPs= 2 Cls=10(unk. ) Sub=01 Prot=00 Driver=usbscanner +E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms +E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms ++ +
+ If anything is wrong or missing on this page please file a bug report + or use the the + form for adding an unsupported device. +
++ If you own an unsupported scanner, please send as much information as + possible. Especially the output of sane-find-scanner -v -v + and/or cat /proc/scsi/scsi (for SCSI scanners) or cat + /proc/bus/usb/devices (for USB scanners) can help. If you dare to + open the scanner, have a look at the text that's printed on the + chips. That may help to identify the chipset. If you know that the + scanner is similar to another one (e.g. supported by the same Windows + driver), please also mention this fact. +
+ ++ Are you a manufacturer or vendor of scanners and one of your scanners is + not supported by SANE yet? In this case please have a look at our information for manufacturers. +
+ +
+ SANE homepage
+ Contact
+
+ $Date$ $Author$ +
+ + +