<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Troels,<br>
    <br>
    I prepared a quick patch for your scanner in
    'backend/pixma_imageclass.c'. The patch is based on recent
    development version 1.0.25.<br>
    <br>
    You also need to copy the attached udev rules file to
    '/etc/udev/rules.d'.<br>
    <br>
    I also added MF8500C Series. Both scanners should work with this
    patch, if they are similar to running MF4700 Series.<br>
    <br>
    Please read README.linux for installing Sane and basic testing. <br>
    <br>
    If you want to see some debug messages in a terminal or if you want
    to use ethernet, please read sane-pixma man page.<br>
    <br>
    Cheers,<br>
    Rolf<br>
    <br>
    <br>
    <div class="moz-cite-prefix">Am 28.07.2014 um 15:47 schrieb Troels
      Thomsen:<br>
    </div>
    <blockquote
cite="mid:%3CCANAA4oZPvXUpt=y_UKjLr-iOba0U1HPrXSLW0VUKSOm1DxVwYw@mail.gmail.com%3E"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div><span style="font-family:courier new,monospace"><br>
                  </span></div>
                <span style="font-family:courier new,monospace">Hi, <br>
                  <br>
                </span></div>
              <span style="font-family:courier new,monospace">I'm trying
                to figure out if I can get Canon iSENSYS MF8230c to work
                with sane-pixma back-end.<br>
              </span></div>
            <div><span style="font-family:courier new,monospace">I've
                been reading a bit and experimenting a bit.<br>
                <br>
              </span></div>
            <span style="font-family:courier new,monospace">On the
              positive side, there is already support for "i-SENSYS
              MF3010, MF4320d, MF4330d, MF4550d".<br>
            </span></div>
          <span style="font-family:courier new,monospace">What worries
            me is that I saw that there was committed new .c files only
            3 days ago, to support a few new canon models, so I suspect
            I need to work a bit for it ;-)<br>
            <br>
          </span></div>
        <div><span style="font-family:courier new,monospace">Can I
            convince the driver to treat my usb vid/pid as eg the
            iSENSYS mf4330d, and then see where that leaves me? (ohh ...
            nasty thought: is there a vid/pid cheat option in linux usb
            driver stack, so I could do it that way around?)<br>
          </span></div>
        <div><span style="font-family:courier new,monospace">Or do I
            need to take a copy of the .c file, change the VID/PID, and
            then see where that leaves me?<br>
            <br>
          </span></div>
        <div><span style="font-family:courier new,monospace">IN GENERAL,
            a few pointers to where I should go next would be greatly
            appreciated!</span></div>
        <div><span style="font-family:courier new,monospace"></span></div>
        <div><span style="font-family:courier new,monospace">/Troels<br>
            <br>
          </span></div>
        <div><span style="font-family:courier new,monospace">misc traces
            below<br>
          </span></div>
        <div><span style="font-family:courier new,monospace"><br>
            $ sudo lsusb<br>
          </span></div>
        <div><span style="font-family:courier new,monospace"><cut><br>
          </span></div>
        <div><span style="font-family:courier new,monospace">Bus 002
            Device 009: ID 04a9:2779 Canon, Inc. <br>
          </span></div>
        <div><span style="font-family:courier new,monospace"><cut><br>
            <br>
            $ sudo scanimage -L<br>
            No scanners were identified. <br>
            <br>
            sudo sane-find-scanner -v -v -v<br>
          </span></div>
        <div><span style="font-family:courier new,monospace"><cut><br>
            <device descriptor of 0x04a9/0x2779 at 002:009
            (Canon,Inc. MF8200C Series)><br>
            bLength               18<br>
            bDescriptorType       1<br>
            bcdUSB                2.00<br>
            bDeviceClass          0<br>
            bDeviceSubClass       0<br>
            bDeviceProtocol       0<br>
            bMaxPacketSize0       64<br>
            idVendor              0x04A9<br>
            idProduct             0x2779<br>
            bcdDevice             0.00<br>
            iManufacturer         1 (Canon,Inc.)<br>
            iProduct              2 (MF8200C Series)<br>
            iSerialNumber         3 (2c9efc4f5de2)<br>
            bNumConfigurations    1<br>
             <configuration 0><br>
             bLength              9<br>
             bDescriptorType      2<br>
             wTotalLength         62<br>
             bNumInterfaces       2<br>
             bConfigurationValue  1<br>
             iConfiguration       0 ()<br>
             bmAttributes         192 (Self-powered)<br>
             MaxPower             2 mA<br>
              <interface 0><br>
               <altsetting 0><br>
               bLength            9<br>
               bDescriptorType    4<br>
               bInterfaceNumber   0<br>
               bAlternateSetting  0<br>
               bNumEndpoints      3<br>
               bInterfaceClass    255<br>
               bInterfaceSubClass 0<br>
               bInterfaceProtocol 255<br>
               iInterface         0 ()<br>
                <endpoint 0><br>
                bLength           7<br>
                bDescriptorType   5<br>
                bEndpointAddress  0x03 (out 0x03)<br>
                bmAttributes      2 (bulk)<br>
                wMaxPacketSize    512<br>
                bInterval         0 ms<br>
                bRefresh          0<br>
                bSynchAddress     0<br>
                <endpoint 1><br>
             bLength           7<br>
                bDescriptorType   5<br>
                bEndpointAddress  0x84 (in 0x04)<br>
                bmAttributes      2 (bulk)<br>
                wMaxPacketSize    512<br>
                bInterval         0 ms<br>
                bRefresh          0<br>
                bSynchAddress     0<br>
                <endpoint 2><br>
                bLength           7<br>
                bDescriptorType   5<br>
                bEndpointAddress  0x85 (in 0x05)<br>
                bmAttributes      3 (interrupt)<br>
                wMaxPacketSize    64<br>
                bInterval         11 ms<br>
                bRefresh          0<br>
                bSynchAddress     0<br>
              <interface 1><br>
               <altsetting 0><br>
               bLength            9<br>
               bDescriptorType    4<br>
               bInterfaceNumber   1<br>
               bAlternateSetting  0<br>
               bNumEndpoints      2<br>
               bInterfaceClass    7<br>
               bInterfaceSubClass 1<br>
               bInterfaceProtocol 2<br>
               iInterface         0 ()<br>
                <endpoint 0><br>
                bLength           7<br>
                bDescriptorType   5<br>
                bEndpointAddress  0x01 (out 0x01)<br>
                bmAttributes      2 (bulk)<br>
                wMaxPacketSize    512<br>
                bInterval         0 ms<br>
                bRefresh          0<br>
                bSynchAddress     0<br>
                <endpoint 1><br>
                bLength           7<br>
                bDescriptorType   5<br>
                bEndpointAddress  0x82 (in 0x02)<br>
                bmAttributes      2 (bulk)<br>
                wMaxPacketSize    512<br>
                bInterval         0 ms<br>
                bRefresh          0<br>
                bSynchAddress     0<br>
            <br>
            <br>
            <br>
            <br>
          </span></div>
      </div>
    </blockquote>
    <br>
  </body>
</html>