Hello,
 sorry that I was wrong about libusb function, the right one is 
usb_set_configuration(), I saw in sanei_usb the place of usb_set_configuration 
is before usb_claim_interface being used, but when I saw in sane-backend for 
1.0.16 , the sm3600 was usb_claim_interface first after that is 
usb_set_configuration , so I follow that way, after that I don't exactly 
understand why, but for now is already works, I will going to change and to use 
sanei_usb.h .
 
 and I see the chip is SQ113
 <device descriptor of 0x05da/0x3021 at 001:009 (Prolific Technology Inc. USB 
Scanner               )>
 bLength               18
 bDescriptorType       1
 bcdUSB                2.00
 bDeviceClass          0
 bDeviceSubClass       0
 bDeviceProtocol       0
 bMaxPacketSize0       64
 idVendor              0x05DA
 idProduct             0x3021
 bcdDevice             1.00
 iManufacturer         1 (Prolific Technology Inc.)
 iProduct              2 (USB Scanner               )
 iSerialNumber         0 ()
 bNumConfigurations    1
  <configuration 0>
  bLength              9
  bDescriptorType      2
  wTotalLength         39
  bNumInterfaces       1
  bConfigurationValue  1
  iConfiguration       0 ()
  bmAttributes         192 (Self-powered)
  MaxPower             100 mA
   <interface 0>
    <altsetting 0>
    bLength            9
    bDescriptorType    4
    bInterfaceNumber   0
    bAlternateSetting  0
    bNumEndpoints      3
    bInterfaceClass    255
    bInterfaceSubClass 255
    bInterfaceProtocol 255
    iInterface         0 ()
     <endpoint 0>
     bLength           7
     bDescriptorType   5
     bEndpointAddress  0x01 (out 0x01)
     bmAttributes      2 (bulk)
     wMaxPacketSize    512
     bInterval         0 ms
     bRefresh          0
     bSynchAddress     0
     <endpoint 1>
     bLength           7
     bDescriptorType   5
     bEndpointAddress  0x82 (in 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         3 ms
     bRefresh          0
     bSynchAddress     0
 
 <trying to find out which USB chip is used>
     checking for GT-6801 ...
     this is not a GT-6801 (bDeviceClass = 0)
     checking for GT-6816 ...
     this is not a GT-6816 (bcdUSB = 0x200)
     checking for GT-8911 ...
     this is not a GT-8911 (check 2, bcdUSB = 0x200)
     checking for MA-1017 ...
     this is not a MA-1017 (bDeviceClass = 0, bInterfaceClass = 255)
     checking for MA-1015 ...
     this is not a MA-1015 (bDeviceClass = 0)
     checking for MA-1509 ...
     this is not a MA-1509 (bDeviceClass = 0)
     checking for LM983[1,2,3] ...
     this is not a LM983x (bcdUSB = 0x200)
     checking for GL646 ...
     this is not a GL646 (bDeviceClass = 0, bInterfaceClass = 255)
     checking for GL646_HP ...
     this is not a GL646_HP (bDeviceClass = 0, bInterfaceClass = 255)
     checking for GL660+GL646 ...
     this is not a GL660+GL646 (bDeviceClass = 0, bInterfaceClass = 255)
     checking for GL841 ...
     this is not a GL841 (bDeviceClass = 0, bInterfaceClass = 255)
     checking for ICM532B ...
     this is not a ICM532B (check 1, bDeviceClass = 0, bInterfaceClass = 255)
     checking for PV8630/LM9830 ...
     this is not a PV8630/LM9830 (bcdUSB = 0x200)
     checking for M011 ...
     this is not a M011 (bDeviceClass = 0)
     checking for RTS8822L-01H ...
     this is not a RTS8822L-01H (bEndpointAddress = 0x1, bmAttributes = 0x2, 
wMaxPacketSize = 0x200, bInterval = 0x0)
     checking for rts8858c ...
     this is not a rts8858c (bcdUSB = 0x200)
     checking for SQ113 ...
 <This USB chip looks like a SQ113>
 
 found USB scanner (vendor=0x05da [Prolific Technology Inc.], product=0x3021 
[USB Scanner               ], chip=SQ113) at libusb:001:009
 
 
 

                
---------------------------------
Blab-away for as little as 1?/min. Make  PC-to-Phone Calls using Yahoo! 
Messenger with Voice.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060419/5addf245/attachment.htm
From power_station_2...@yahoo.com  Wed Apr 19 11:39:15 2006
From: power_station_2...@yahoo.com (Tamkang)
Date: Wed Apr 19 11:39:59 2006
Subject: [sane-devel] Question about kooka
Message-ID: <20060419113915.78813.qm...@web30511.mail.mud.yahoo.com>

Hello Henning,
I want to ask you about kooka, I have a weird problem with kooka,  I don't know 
where is goes wrong, I mean, in xsane, gimp, all is work ok , but not in kooka, 
as I know kooka also using sane-backend , so my driver also can also work for 
kooka. but now I met the problem is like this, the kooka recognize my driver, 
but when I preview or scanning, the carridge start to move and return back to 
home quickly, not same with xsane , normally the carridge will move preview one 
page and return back to home,  but in kooka is different it only move about a 
little step and return home quick, so it doesn't scan the image, and the kooka 
is no hang or nothing error message.  I already try to search this information, 
the problem is, why in xsane is working but not in kooka? can you help me ? 
Thanks for advance
 
 Best Regards,
 sofian

                
---------------------------------
Love cheap thrills? Enjoy PC-to-Phone  calls to 30+ countries for just 2?/min 
with Yahoo! Messenger with Voice.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060419/98f22632/attachment.html
From cl...@egehuset.dk  Wed Apr 19 12:34:46 2006
From: cl...@egehuset.dk (Claus Boje)
Date: Wed Apr 19 12:30:30 2006
Subject: SV: [sane-devel] Preparation for sane-backends release 1.0.18
In-Reply-To: <20060418155457.gh9...@meier-geinitz.de>
Message-ID: <002901c663ad$a4e4d4f0$6b504c0a@CLAUSBOJE>


> 
> I intend to start the countdown for the release of sane-backends
> 1.0.18 in a few weeks. So it's now the right time to include any big
> changes into sane-backends that are available. Especially big updates
> of existing backends and new backends should be included in the
> following weeks.
> 
I have not heard anything about my patch for the epson perfection 4990 (se
bug 302090).

Bye 

Claus Boje

Reply via email to