[sane-devel] Adding Scanner to Backend Configuration
Quoting Hugh McMaster dasjour...@gmail.com: My scanner (Canon Lide 70) is not supported currently, but (I hope) will be supported by the Genesys backend sometime soon. Anyway, if I added the Scanner IDs to the Genesys backend Conf.in and recompiled, would that allow any usage of the scanner at all? The chipset in the Canon Lide 70 is not yet known, but it did not respond positively to gl841 or gl646, so it is will not at present work with the genesys backend. It has only 2 bulk endpoints, but no isosynchronous endpoint, so it is different. Some work is required to identify the chip, and the protocol. Using usbsnoop on a small scan may provide helpful information. In any case, quite a bit of work lies between now and a successful sane scan. I suggest obtaining a usbsnoop log and/or identifying the chipset. The recompile is not likely to work or provide useful information, in my humble opinion. Someone needs to initiage and carry that project forward into development. Good luck, Gerald
[sane-devel] [FYI] new ls5000 backend
Johannes Berg johan...@sipsolutions.net wrote: Hi, I don't plan to submit any patches to coolscan2.c because that code is in my eyes horrible to work with. I also don't plan to submit ls5000.c to SANE because apparently SANE still requires that the backend builds with ancient compilers. I've added ls5000 to sane-backends-extras 1.0.18.8. JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] [FYI] new ls5000 backend
Johannes Berg johan...@sipsolutions.net wrote: Hi, I've added ls5000 to sane-backends-extras 1.0.18.8. Oh, I'll probably have to submit a patch than that prevents coolscan2 from binding the ls5000. Yep, that'll be needed. Though LS-5000 owners won't use coolscan2 so they can just disable it and be done with it. Note that we really need something more general to fix that, because we have the same problem with epson and epson2 stepping on each other's toes in the CVS (and then there's epkowa ... 3 backends for epson scanners, and I'm not counting the snapscan backend ...). JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] [FYI] new ls5000 backend
Hi, I don't plan to submit any patches to coolscan2.c because that code is in my eyes horrible to work with. I also don't plan to submit ls5000.c to SANE because apparently SANE still requires that the backend builds with ancient compilers. I've added ls5000 to sane-backends-extras 1.0.18.8. Oh, I'll probably have to submit a patch than that prevents coolscan2 from binding the ls5000. johannes -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 190 bytes Desc: This is a digitally signed message part Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070512/c9047a2b/attachment.pgp From johan...@sipsolutions.net Sat May 12 09:29:22 2007 From: johan...@sipsolutions.net (Johannes Berg) Date: Sat May 12 10:55:09 2007 Subject: [sane-devel] [FYI] new ls5000 backend In-Reply-To: 1178961968.2647.7.ca...@johannes.berg References: 117306.8896.22.ca...@johannes.berg 871whme7lf@sonic.technologeek.org 1178961968.2647.7.ca...@johannes.berg Message-ID: 1178962162.2647.10.ca...@johannes.berg On Sat, 2007-05-12 at 11:26 +0200, Johannes Berg wrote: Oh, I'll probably have to submit a patch than that prevents coolscan2 from binding the ls5000. This should work. It doesn't prevent it from claiming the USB interface but then queries the scanner and if it's a LS-5000 gives up, that *should* give ls5000 a chance to be queried as the next scanner if I correctly understand how querying works. johannes --- sane-backends-1.0.18.orig/backend/coolscan2.c 2007-05-12 11:26:31.0 +0200 +++ sane-backends-1.0.18/backend/coolscan2.c2007-05-12 11:28:00.0 +0200 @@ -1791,8 +1791,6 @@ cs2_open (const char *device, cs2_interf s-type = CS2_TYPE_LS2000; else if (!strncmp (s-product_string, LS-4000 ED , 16)) s-type = CS2_TYPE_LS4000; - else if (!strncmp (s-product_string, LS-5000 ED , 16)) -s-type = CS2_TYPE_LS5000; else if (!strncmp (s-product_string, LS-8000 ED , 16)) s-type = CS2_TYPE_LS8000;
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'c.c...@dsl.pipex.com' 2. Manufacturer (e.g. Mustek): 'Plustek ' 3. Model name (e.g. ScanExpress 1200UB): 'OpticFilm 7200' 4. Bus type: 'USB' 5. Vendor id (e.g. 0x001): '0x07b3' 6. Product id (e.g. 0x0002): '0x0c07' 7. Chipset (e.g. lm9831): 'GL841' 8. Comments (e.g. similar to Mustek 1234): 'Uses GL841 whereas the unsupported scanner report shows GL842. Do you have a backend in development - I would be happy to test this.' 9. Data (e.g. sane-find-scanner -v -v): 'device descriptor of 0x07b3/0x0c07 at 004:004-07b3-0c07-ff-ff (Plustek INC Film Scanner ) bLength 18 bDescriptorType 1 bcdUSB2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x07B3 idProduct 0x0C07 bcdDevice 4.00 iManufacturer 10 (Plustek INC) iProduct 11 (Film Scanner ) iSerialNumber 12 (1) bNumConfigurations1 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 bLength9 bDescriptorType4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () endpoint 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 1 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize512 bInterval 0 ms bRefresh 0 bSynchAddress 0 endpoint 2 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize1 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 = 0x200) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for GT-8911 ... this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bcdUSB = 0x200) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x200) checking for LM983[1,2,3] ... this is not a LM983x (bcdUSB = 0x200) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x200) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... This USB chip looks like a GL841 (result from sane-backends 1.0.18-cvs) found USB scanner (vendor=0x07b3 [Plustek INC], product=0x0c07 [Film Scanner ], chip=GL841) at libusb:004:004-07b3-0c07-ff-ff '
[sane-devel] [FYI] new ls5000 backend
If anybody wants to do it, all the better, but if it makes the code as unreadable and stupid as it was in coolscan2.c (like parsing bytes from a string at runtime...) then I will not take such a patch nor help maintain a forked version. Please note that the author of coolscan2 is reading this list and might be offended by such unqualified and inappropriate remarks. Or is my code really that bad? Or maybe the stupid functions you refer to were added by others? Trying to use the latest language features is one thing, writing robust and portable code is another. If you can't read the latter, there isn't much I can do. Andras
[sane-devel] Re: [sane-avision] scanimage usb problem.
Ren? Rebe wrote: Hi Erik, On Friday 11 May 2007 23:11:27 Erik P. Olsen wrote: I have changed my HP 7400c scanner connection from scsi to usb which gives me a strange problem. sane-find-scanner finds the scanner OK. xsane accesses the scanner correctly. scanimage -L hangs. Setting debug trace on I get: [erik@epohost ~]$ SANE_DEBUG_AVISION=15 scanimage -L [sanei_debug] Setting debug level of avision to 15. [avision] sane_init:(Version: 1.0 Build: 229) [avision] sane_init: parsing config line [avision] sane_init: config file line 1: ignoring empty line [avision] sane_init: parsing config line # This are the possible options. Normally any scanner [avision] sane_init: config file line 2: ignoring comment line [avision] sane_init: parsing config line # should work just fine without them - and they are only [avision] sane_init: config file line 3: ignoring comment line [avision] sane_init: parsing config line # needed for test and debugging. So if you experience problems [avision] sane_init: config file line 4: ignoring comment line [avision] sane_init: parsing config line # and you solve them with enabling options here, please notify [avision] sane_init: config file line 5: ignoring comment line [avision] sane_init: parsing config line # the SANE/Avision maintainer: Rene Rebe r...@exactcode.de [avision] sane_init: config file line 6: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 7: ignoring empty line [avision] sane_init: parsing config line #option disable-gamma-table [avision] sane_init: config file line 8: ignoring comment line [avision] sane_init: parsing config line #option disable-calibration [avision] sane_init: config file line 9: ignoring comment line [avision] sane_init: parsing config line #option force-a4 [avision] sane_init: config file line 10: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 11: ignoring empty line [avision] sane_init: parsing config line #scsi AVISION [avision] sane_init: config file line 12: ignoring comment line [avision] sane_init: parsing config line #scsi FCPA [avision] sane_init: config file line 13: ignoring comment line [avision] sane_init: parsing config line #scsi MINOLTA [avision] sane_init: config file line 14: ignoring comment line [avision] sane_init: parsing config line #scsi MITSBISH MCA-S600C [avision] sane_init: config file line 15: ignoring comment line [avision] sane_init: parsing config line #scsi MITSBISH MCA-SS600 [avision] sane_init: config file line 16: ignoring comment line [avision] sane_init: parsing config line #scsi HP [avision] sane_init: config file line 17: ignoring comment line [avision] sane_init: parsing config line #scsi hp [avision] sane_init: config file line 18: ignoring comment line [avision] sane_init: parsing config line [avision] sane_init: config file line 19: ignoring empty line [avision] sane_init: parsing config line #scsi /dev/scanner [avision] sane_init: config file line 20: ignoring comment line [avision] sane_init: parsing config line #usb libusb:001:003 [avision] sane_init: config file line 21: ignoring comment line [avision] sane_init: parsing config line usb 0x03f0 0x0801 [avision] sane_init: config file line 22: trying to attach USB:`usb 0x03f0 0x0801' [avision] attach: [avision] attach: opening libusb:001:003 [avision] inquiry: length: 96 [avision] inquiry: inquiring ... [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 3, read: 15000, status: 15000 [avision] try to write cmd, count: 10. [avision] wrote 10 bytes [avision] try to read 96 bytes [avision] read 96 bytes [avision] avision_usb_status: timeout 15000, 1 retries [avision] == (bulk read) going down ... [avision] == (bulk read) got: 0, status: 0 [avision] == (interrupt read) going down ... [avision] == (interrupt read) got: 1, status: 0 [avision] attach: Inquiry gives mfg=hp, model=scanjet 7400c, product revision=0.8S. [avision] attach: Found model: 57 [avision] inquiry: length: 96 [avision] inquiry: inquiring ... [avision] filling command to have a length of 10, was: 6 [avision] Timeouts: write: 3, read: 15000, status: 15000 [avision] try to write cmd, count: 10. [avision] wrote 10 bytes [avision] try to read 96 bytes [avision] read 96 bytes [avision] avision_usb_status: timeout 15000, 1 retries [avision] == (bulk read) going down ... [avision] == (bulk read) got: 0, status: 0 [avision] == (interrupt read) going down ... [avision] == (interrupt read) got: 1, status: 0 [avision] inquiry: length: 136 [avision] inquiry: inquiring ... [avision] filling command to have a length of 10, was: 6 What can my problem be? Did the scanner work fine over SCSI with the same backend version? Can you scan via xsane but just scanimage -L hangs? Yes, the scanner works OK over scsi and yes, I can scan via xsane and it's just
