From b8d0833822d5a6f30b089455e328c68047d23dee Mon Sep 17 00:00:00 2001 From: Bertrik Sikken Date: Sun, 23 Sep 2007 19:28:01 +0000 Subject: [PATCH] Info from FormularDaten 2007/2/3 --- unsupported/hp-photosmart-3180.html | 266 ++++++++++++++++++++++++++++ 1 file changed, 266 insertions(+) create mode 100644 unsupported/hp-photosmart-3180.html diff --git a/unsupported/hp-photosmart-3180.html b/unsupported/hp-photosmart-3180.html new file mode 100644 index 00000000..5425aafb --- /dev/null +++ b/unsupported/hp-photosmart-3180.html @@ -0,0 +1,266 @@ + + + + + Scanner information + + + + + + + + + +

Scanners not supported by SANE

+

Manufacturer and model

+

Hewlett-Packard Photosmart C3180 +

+

Bus type

+

USB +

+

Vendor ID

+

0x03F0 +

+

Product ID

+

0x5611 +

+

Chipset

+

Unknown +

+

Comments

+

Probably similar to Hp Photosmart 5100 series. +

+

Output of /proc/bus/usb/devices or sane-find-scanner -v -v or lsusb -vv

+ 
+<device descriptor of 0x03f0/0x5611 at 001:003 (HP Photosmart C3100 series)>
+bLength               18
+bDescriptorType       1
+bcdUSB                2.00
+bDeviceClass          0
+bDeviceSubClass       0
+bDeviceProtocol       0
+bMaxPacketSize0       8
+idVendor              0x03F0
+idProduct             0x5611
+bcdDevice             1.00
+iManufacturer         1 (HP)
+iProduct              2 (Photosmart C3100 series)
+iSerialNumber         3 (MY6A6C34FF04P9)
+bNumConfigurations    1
+ <configuration 0>
+ bLength              9
+ bDescriptorType      2
+ wTotalLength         131
+ bNumInterfaces       4
+ bConfigurationValue  1
+ iConfiguration       0 ()
+ bmAttributes         192 (Self-powered)
+ MaxPower             2 mA
+  <interface 0>
+   <altsetting 0>
+   bLength            9
+   bDescriptorType    4
+   bInterfaceNumber   0
+   bAlternateSetting  0
+   bNumEndpoints      3
+   bInterfaceClass    255
+   bInterfaceSubClass 204
+   bInterfaceProtocol 0
+   iInterface         0 ()
+    <endpoint 0>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x01 (out 0x01)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 1>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x82 (in 0x02)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 2>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x83 (in 0x03)
+    bmAttributes      3 (interrupt)
+    wMaxPacketSize    8
+    bInterval         10 ms
+    bRefresh          0
+    bSynchAddress     0
+  <interface 1>
+   <altsetting 0>
+   bLength            9
+   bDescriptorType    4
+   bInterfaceNumber   1
+   bAlternateSetting  0
+   bNumEndpoints      2
+   bInterfaceClass    7
+   bInterfaceSubClass 1
+   bInterfaceProtocol 2
+   iInterface         0 ()
+    <endpoint 0>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x0A (out 0x0A)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 1>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x8B (in 0x0B)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+  <interface 2>
+   <altsetting 0>
+   bLength            9
+   bDescriptorType    4
+   bInterfaceNumber   2
+   bAlternateSetting  0
+   bNumEndpoints      2
+   bInterfaceClass    255
+   bInterfaceSubClass 255
+   bInterfaceProtocol 255
+   iInterface         0 ()
+    <endpoint 0>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x07 (out 0x07)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 1>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x88 (in 0x08)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+   <altsetting 1>
+   bLength            9
+   bDescriptorType    4
+   bInterfaceNumber   2
+   bAlternateSetting  1
+   bNumEndpoints      2
+   bInterfaceClass    255
+   bInterfaceSubClass 212
+   bInterfaceProtocol 0
+   iInterface         0 ()
+    <endpoint 0>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x07 (out 0x07)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 1>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x88 (in 0x08)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+  <interface 3>
+   <altsetting 0>
+   bLength            9
+   bDescriptorType    4
+   bInterfaceNumber   3
+   bAlternateSetting  0
+   bNumEndpoints      2
+   bInterfaceClass    8
+   bInterfaceSubClass 6
+   bInterfaceProtocol 80
+   iInterface         0 ()
+    <endpoint 0>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x04 (out 0x04)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+    <endpoint 1>
+    bLength           7
+    bDescriptorType   5
+    bEndpointAddress  0x85 (in 0x05)
+    bmAttributes      2 (bulk)
+    wMaxPacketSize    64
+    bInterval         0 ms
+    bRefresh          0
+    bSynchAddress     0
+
+ +

Want to add or correct information?

+

+ 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. +

+ +

Information for Manufacturers

+

+ 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. +

+ +

Links

+ + +
+ +

+ SANE homepage
+ Contact +

+

+ $Date$ $Author$ +

+ + +