Hi, On Thu, Feb 26, 2004 at 01:11:47PM -0600, Frank Zago wrote: > >So can sane-find-scanner really talkt to the scanner after that > >change? Can I see the output of sane-find-scanner -v -v after the > >change, please? > > Yes, it can. Looking at the usb traces, it looks like it is very close, if > not identical, to a gl646. The registers used are the same, and the method > to access them is very similar to that of the gl640.
Ok. So I suggest you add another chipset to check-usb-scanner.c with your changes (e.g. GL646HP). This way we can see which of the two types is used in which scanners. > It seems there is at least 3 hp usb scanners (3670, 3690, 2400) that have a > close chip. I'm only sure about the 3670 since that's the only one I found > usb traces. Ok. Can you add this info to the information pages about these scanners in CVS, please? > Is it possible you set up a cvs tree for backends development (not specific > to a particular backend) I think so. I'm not sure if only project managers can do that. Try yourself (with cvs import I guess). Currently we have: CVSROOT html sane-backends sane-frontends What about "experimental" for external/testing backends?. It should be clear from the name that this is not official. If you can't do that, I will. > and a mailing list for people interrested in the > GL scanner-on-chip dev? I don't want to use SF, and it would be better on > alioth anyway. I guess that can only be done by project admins. We should make sure that this list doesn't confuse "regular" SANE users. I'll think about it. > If you don't mind, I'd also like to see what code you have written for the > gl646. See http://www.meier-geinitz.de/sane/genesys-backend/ I'll also add the HP scanners to this page. When you have more code, links or anything else I should add, just ask. I won't have enough time to do real coding in the next time but answering questions and testing is possible :-) Bye, Henning
