> from the chip's label, support for you scanner belongs to the rts8891 > backend, even though sane-find-scanner doesn't detect it properly. Do you > have > a windows box where you can run your scanner ? If so I'd be interested by an
I have only windows instalation inside virtualbox, but as vbox does support bridging USB devices inside virtual machines, I was able to scan a 75 dpi color page from the scanner, while capturing communication using UsbSnoop. Since the log file is 3.6Mb even after bzipping, I uploaded it to http://wtx.wz.cz/UsbSnoop.log.bz2 In the log, actual scanning (when the scanner started warming up) starts about 97000 ms > Usbsnoop (http://www.pcausa.com/Utilities/UsbSnoop/) log of a 75 dpi color > scan. I'd be able to tell for sure how close it is from supported models. If > needed I can provide some explanations on how doing it. > From the known information, your scanner doesn't seem to be far from > the > Astra 4400 which isn't yet supported. Bringing support for these 2 scanners > is > a matter of how different they are from supported models. If close, by > exchanging logs and test code we'd be able to have them working. But if they > are too different, support wouldn't be possible with access for a developer > to > the real hardware. What about some form of remote access? > If you feel like it you could add your scanner to rts8891.conf.in and > rts8891_devices.c source files (cloning the HP4470 entry), and have a try. Be > aware that when experimenting with partially supported hardware, you can't > exclude it could be damaged. What type of damage can I expect from that? Something like the scanner lamp driving off the rails, which could be maybe fixed just by using a screwdriver or some parts irreversibly burning out? Martin Petricek
