On Tue, 24 Oct 2006, Henning Meier-Geinitz wrote: > On 2006-10-24 15:47, [email protected] wrote: > > Hi. Can anyone explain the state of the SANE2 branch? I've noticed that > > the SANE2 development seems inactive. Is this branch discontinued? > > The development of SANE2 hasn't begun, there have been only > discussions and there is a draft of the SANE2 standard. The standard > is not finished yet as some of the problems are not easy to solve.
Ok, I'll stick to SANE1 for now, then. > > I will make a try to eliminate the separate data port requirement for > > "saned". I think it should be possible to do this by extending the SANE1 > > protocol in a backwards compatible way, say, by introducing a new RPC > > call. Comments on this? > > Possible problems: You can't cancel a scan while data acquisition is > in progress. This is one of the adavantages of the 2 port solution. I think cancel should be possible even without the separate port. TCP is bi-directional: You can send a cancel request to "saned" even though data flows in the other direction. It's true that most RPC servers (including saned, I guess) won't respond to new requests until the last one is finished, but my plan is not to transfer all data in one single call, but let the client do several calls, just like sane_read(). So, the client should be able to cancel the acquisition instead of calling the server for more data. Regards, -- Peter ?strand ThinLinc Chief Developer Cendio AB http://www.cendio.se Teknikringen 3 583 30 Link?ping Phone: +46-13-21 46 00 From [email protected] Wed Oct 25 10:59:48 2006 From: [email protected] (Maik Musall) Date: Wed Oct 25 11:25:55 2006 Subject: [sane-devel] Canon LiDE 70 support Message-ID: <[email protected]> Hi, I'm newly subscribed here, and found just two postings about this scanner in the archives. I purchased one today and am trying to get support for it. So far, no success. I tried to just add a struct canon_lide_70_model into genesys_devices.c by copying the lide_60 part and only adjusting the resolutions and model names, and adding a line {0x04a9, 0x221c, &canon_lide_60_model}, into genesys_usb_device_list. After this, I added the usb data to /etc/sane.d/genesys.conf, and then after compiling I get: # scanimage -L device `genesys:libusb:004:007' is a Canon LiDE 70 flatbed scanner but scanning doesn't actually work: # scanimage > ~/file.pnm scanimage: open of device genesys:libusb:004:007 failed: Invalid argument The scanner doesn't show any reaction. I wonder if it's a GENE based one at all. How do I find out? How can I help to get this supported? I have 14 days before I have to send it back if it doesn't work... ;-) I'm using gentoo Linux 2.6.17-r8 and sane-backends 1.0.18-r2. Here is the lsusb -v -v output's section about the scanner: Bus 004 Device 007: ID 04a9:2225 Canon, Inc. Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 idVendor 0x04a9 Canon, Inc. idProduct 0x2225 bcdDevice 0.00 iManufacturer 1 Canon iProduct 2 CanoScan iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 255 Vendor Specific Subclass bInterfaceProtocol 255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength 10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass 255 Vendor Specific Class bDeviceSubClass 255 Vendor Specific Subclass bDeviceProtocol 255 Vendor Specific Protocol bMaxPacketSize0 64 bNumConfigurations 1 Regards -- Maik Musall <[email protected]> GPG public key 0x856861EB (keyserver: wwwkeys.de.pgp.net)
