[sane-devel] Re: Contributing to CanoScan LiDE 500F development.,

Bruno Friedmann brunofr at ioda.net
Tue Jul 26 12:52:00 UTC 2005

Hello Dag,
I've you need some beta-tester, as I had a brand new Lide 500F, and I'm
working under
Mandriva, I would be happy to help you. I'm just not a C man :-)

Hope really this scan to be soon supported under SANE.
Many thanks for your efforts.

You could find my usbsnoop capture log under
http://ftp.ioda.net/ioda-net/usbsnoop.log.tar.gz ( 1Mo)
Just putting the scan into USB port.

>Message: 2
>Date: Tue, 26 Jul 2005 08:16:41 +0200
>From: Dag Rune Sneeggen <contactus at dudcore.net>
>Subject: Re: [sane-devel] Contributing to CanoScan LiDE 500F
>	development.
>To: St?phane VOLTZ <stefdev at modulonet.fr>,
>	sane-devel at lists.alioth.debian.org
>Message-ID: <42E5D549.7080504 at dudcore.net>
>Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>Thanks a bunch for all the useful information and your awk scripts.
>I'll see if I can get around to fiddling a bit with it this week...
>Hopefully hehe ;)
>Dag Rune Sneeggen
>dudcore Consulting(http://www.dudcore.net) - Quality state-of-art hosting and IT Consulting.
>Personal, reasonable, and honest idealism!
>For geeks by geeks...
>Stéphane VOLTZ wrote:
>>Le Mardi 26 Juillet 2005 02:39, Dag Rune Sneeggen a écrit :
>>>I've read over at
>>>http://www.sane-project.org/unsupported/canon-canoscan-lide-500f.html and
>>>http://www.meier-geinitz.de/sane/genesys-backend/ that there is some work
>>>being done to get support for this scanner. At the moment I have to haul up
>>>vmware with windows virtually to scan stuff.
>>>As such, I'm wondering how fast this development is going, and if there's
>>>any way I could help? Anything in particular that could be helpful?
>>>Dag Rune Sneeggen
>>>dudcore Consulting(http://www.dudcore.net) - Quality state-of-art hosting
>>>and IT Consulting. Personal, reasonable, and honest idealism!
>>>For geeks by geeks...
>>	Hello,
>>	here are the scripts I use to analyze gl646 logs taken with usbsniff 1.8. It 
>>takes a raw log and turn it into a file with higher level functions decoded, 
>>which is much easier to understand. The decode() function used by 
>>needs to be changed to decode gl841 registers. But the rest is OK. There are 
>>still a few raw URB in the results, but they are understable (bulk reads of 
>>	Once the scripts are tuned the process of adding support for GL841 is:
>>	- use usbsniff to log scans with clearly identified parameters (dpi,
>>	  geometry, ...)
>>	- decode the log with the scripts
>>	- isolate portion of it and match them with high level action such as head
>>	  parking, shading calibration etc ...
>>	- change the corresponding functions in genesys_gl841.c to match the
>>	  decoded log.
>>	- run scanimage to test with full debug log
>>	- compare the scanimage log with the decoded log and fixe the differences
>>	  you get.
>>	- once a high level function is done, get to the next one.
>>	I estimate it should take about 20 to 40 hours of work to finish the gl841 
>>	Patches and questions are welcomed.
>>	Stef


	Bruno Friedmann	<bruno at ioda-net.ch>

Ioda-Net Sàrl
	c/o RFV, H. Vauclair SA
	Rue de l'Avenir 12
	2800 Delémont - Switzerland
	Tél : ++41 32 435 7175
	Fax : ++41 32 435 7172
	gsm : ++41 78 802 6760
	www.ioda-net.ch 	www.cfcel.com

More information about the sane-devel mailing list