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?
>
> Cheers,
> 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 
scripts/genesys_bulk_write_register.awk
scripts/genesys_bulk_write_register2.awk
scripts/genesys_read_register.awk
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 
data).

        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 
backend.

        Patches and questions are welcomed.

Regards,
        Stef

-------------- next part --------------
A non-text attachment was scrubbed...
Name: scripts.tar.gz
Type: application/x-tgz
Size: 6691 bytes
Desc: not available
Url : 
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20050726/fe2404a7/scripts.tar-0001.bin
From [email protected]  Tue Jul 26 05:09:52 2005
From: [email protected] (=?iso-8859-1?q?St=E9phane_VOLTZ?=)
Date: Tue Jul 26 05:10:59 2005
Subject: [sane-devel] HP ScanJet 2400 (GENESYS)
In-Reply-To: <[email protected]>
References: <[email protected]>
Message-ID: <[email protected]>

Le Mercredi 20 Juillet 2005 14:29, Julio Otero Boehl a ?crit?:
> Hello,
>
> I've just finishing compiling and installing the latest CVS on my
> system, tweaked the config a little bit, and the ScanJet 2400 is
> recognized. I did not test it too much, but would like to know if I can
> help the developers in some way (testing, etc).
>
> My Linux system is a little bit odd (It's a Linkstation system running
> kernel 2.4.17-ppc. I'am using libusb 0.1.10a.
>
> Best regards and thanks for the work on the genesys backend.
>
> Julio

        Hello,

        what I need to complete HP2400 support is usbsniff-1.8 logs- taken 
under 
windows- of clearly identified scans. Based on these data, I'd should be able 
to tune the gl646 functions to run your scanner. However, since I don't have 
acces to such a scanner, you (and others) will have to test the changes, 
which will be a slow process. Hopefully the 2400 is close enough to the 2300 
so it may not be that long.

Regards,
        Stef

Reply via email to