On Jun 8, 2005, at 1:30 PM, Gerhard Jaeger wrote:
> On Wednesday 08 June 2005 18:35, Steven Palm wrote:
>
>> scanimage(12019) malloc: *** error for object 0x303fe0: double free
>> scanimage(12019) malloc: *** set a breakpoint in szone_error to debug
>>
>> Is th
sane-find-scanner lists:
found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan],
chip=LM9832/3) at libusb:003:002-04a9-220d-ff-00
scanimage -L lists:
device `plustek:libusb:003:002-04a9-220d-ff-00' is a Canon N670U/
N676U/LiDE20 USB flatbed scanner
scanimage(12019) malloc: *** er
Still working on the microtek2 backend stuff for libusb...
It seems that the odd issues I'm encountering will go away if I don't
ever close the USB device. If I leave it open for the duration of the
backend lifetime, scanimage -L will properly identify it. If I open
and close it for each ope
OK, although I will need to read the other endpoint for image data,
that apparently is not the issue I'm hitting right now.
I can open the scanner.
I can send it short INQUIRY and get the requested data block back
then read status.
I can send it long INQUIRY and get the requested data block
On May 21, 2005, at 11:08 AM, gerard klaver wrote:
> To select in SANE in the same configuration (conf 0, interface 0 and
> altsetting ) a different endpoint is not possible yet.
And there is only one configuration in this scanner, and I had
tried altsetting with no luck, it seems there is no
On May 14, 2005, at 7:18 AM, Henning Meier-Geinitz wrote:
>> Any notes on how to go about (or general guidelines for) converting a
>> driver to support libusb?
>
> You shouldn't use libusb directly but the sanei_usb functions. AFAIK
> the avision backend has been changed to use direct USB access in
On May 14, 2005, at 7:18 AM, Henning Meier-Geinitz wrote:
> On Fri, May 13, 2005 at 08:37:08PM -0500, Steven Palm wrote:
>> Is anyone working on the microtek2 driver, specifically to allow it
>> to support libusb?
>
> Have you already asked the authors of that backend? I'
Is anyone working on the microtek2 driver, specifically to allow it
to support libusb?
In looking at things, it appears as though it was designed to deal
with the scanners through opening the /dev files and sending/reading
SCSI data directly.
Any notes on how to go about (or general guideli
