[sane-devel] GL660+GL646 (genesys/genesys-new) on CanoScan3000(F)?

[amth@suomi24.fi]

After a while looking into QS Scan08/09/11/113 vs. GL6xx/GL84x chipsets,
it seems that CanoScan 3000/3000F/5000F have GL-chipsets as the packages
found on the actual 3000F hardware suggests LQFP128(GL646) + TQFP48(GL660=
)
-combo that is not used on any of the QS/Scan-chipsets (I bet no-one is
interested to repackage chips on scanners).

The only thing that needs to be changes to see that it actually is GL660+=
GL646
is to take away only the very last of the tests (tools/check-usb-chip.c
"if (val !=3D 0x15)... reg 0x4e !=3D reg 0x38"-test) after that other tes=
ts
seem to pass just fine and 'sane-find scanner -v -v' reports:

<snap>
This is sane-find-scanner from sane-backends 1.0.15-cvs
trying libusb:

<device descriptor of 0x04a9/0x2215 at 006:004 (Canon CanoScan)>
bLength               18
bDescriptorType       1
bcdUSB                2.00
bDeviceClass          255
bDeviceSubClass       255
bDeviceProtocol       255
bMaxPacketSize0       64
idVendor              0x04A9
idProduct             0x2215
bcdDevice             3.03
iManufacturer         3 (Canon)
iProduct              4 (CanoScan)
iSerialNumber         0 ()
bNumConfigurations    1
 <configuration 0>
 bLength              9
 bDescriptorType      2
 wTotalLength         39
 bNumInterfaces       1
 bConfigurationValue  1
 iConfiguration       0 ()
 bmAttributes         192 (Self-powered)
 MaxPower             10 mA
  <interface 0>
   <altsetting 0>
   bLength            9
   bDescriptorType    4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints      3
   bInterfaceClass    0
   bInterfaceSubClass 0
   bInterfaceProtocol 0
   iInterface         0 ()
    <endpoint 0>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x81 (in 0x01)
    bmAttributes      2 (bulk)
    wMaxPacketSize    512
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 1>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x02 (out 0x02)
    bmAttributes      2 (bulk)
    wMaxPacketSize    512
    bInterval         0 ms
    bRefresh          0
    bSynchAddress     0
    <endpoint 2>
    bLength           7
    bDescriptorType   5
    bEndpointAddress  0x83 (in 0x03)
    bmAttributes      3 (interrupt)
    wMaxPacketSize    1
    bInterval         8 ms
    bRefresh          0
    bSynchAddress     0

<trying to find out which USB chip is used>
    checking for GT-6801 ...
    this is not a GT-6801 (bcdUSB =3D 0x200)
    checking for GT-6816 ...
    this is not a GT-6816 (bDeviceClass =3D 255, bInterfaceClass =3D 0)
    checking for GT-8911 ...
    this is not a GT-8911 (check 1, bDeviceClass =3D 255, bInterfaceClass=

=3D 0)
    checking for MA-1017 ...
    this is not a MA-1017 (bDeviceClass =3D 255, bInterfaceClass =3D 0)
    checking for MA-1015 ...
    this is not a MA-1015 (bcdUSB =3D 0x200)
    checking for MA-1509 ...
    this is not a MA-1509 (bcdUSB =3D 0x200)
    checking for LM983[1,2,3] ...
    this is not a LM983x (bDeviceClass =3D 255, bInterfaceClass =3D 0)
    checking for GL646 ...
    this is not a GL646 (bDeviceClass =3D 255, bInterfaceClass =3D 0)
    checking for GL646_HP ...
    this is not a GL646_HP (bDeviceClass =3D 255, bInterfaceClass =3D 0)
    checking for GL660+GL646 ...
<This USB chip looks like a GL660+GL646>

found USB scanner (vendor=3D0x04a9 [Canon], product=3D0x2215 [CanoScan], =
chip=3DGL660+GL646)
at libusb:006:004

  # Your USB scanner was (probably) detected. It may or may not be suppor=
ted
by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary por=
ts
  # can't be detected by this program.
done
</snap>

And if you look at <http://www.sane-project.org/unsupported/canon-5000f.h=
tml>,
<http://www.sane-project.org/unsupported/umax-astra-4700.html> that are
based on exactly similar chipsets and <http://www.sane-project.org/unsupp=
orted/umax-astra-4500.html>
that only differs mildly, at least those should be workable with genesys/=
genesys-new.

Why I sent this email here you might ask, just to let people know that th=
ere
are much more scanners to be included to the genesys/genesys-new backend
(in case there is need for CanoScan 3000F testing, I'm ready'n'willing fo=
r
it). :-)


Ps. And yes, I have soldered off the RF-shied off the board so I can see
all chips and markings on them, but they are all cryptic Canon-specific
numbering.


--
amth