Hi, replying to myself: On Fri, Oct 11, 2002 at 07:07:52PM +0200, Henning Meier-Geinitz wrote: > My question is about the USB scanner driver and its maintainance. If I > understood correctly, the maintainer is now Brian Beattie. Should > patches and bug reports be send to him only, this list or both?
As nobody screamed loudly, I'll just attach the patches. Both patches are against clean 2.4.20-pre10. > * New vendor/product ids (I've already send some to Brian) The scanners are either tested by me or reported to work by other people. I've changed some comments of already existing ids, because there is a difference between the Mustek ScanExpress and BearPaw models. I've also fixed the BearPaw 1200F, the vendor id was wrong. See scanner-newids.dif. > * Quite a lot of scanners are still unsupported by the driver because of > the "only 2 or 3 endpoints" issue. I.e. for some unknown reason the > driver refuses to work with scanners that only have one bulk endpoint. > Is there already a plan on how to fix that? There is a patch at > http://www.mivlgu.murom.ru/~vsu/gt68xx/gt6801-linux.html. While I > can't comment on the quality of the patch, it works for me basically. > > * General stability: With and without the above patch I get sometimes > non-fatal kernel OOPS, especially when unplugging the scanner whe > the application is hung or when trying to remove the scanner module. > As this doesn't happen if I use libusb instead, I guess it's related > to the scanner driver. > Sergey Vlasov seems to have send a patch that may fix these issues to > the old and new maintainers, are there any news about including or > rejecting it? > > * Could the kernel message "scanner.c: open_scanner(1): Unable to access > minor data" be silenced when debugging is not active? SANE tries to > access all the /dev/usb/scanner* devices to check if there is a USB > scanner and so a message is generated for each device file that's not > "connected" to a scanner. I'll attach a patch that fixes all these issues. It's from Sergey Vlasov <[EMAIL PROTECTED]>. I have no experience in kernel hacking so I can't tell if it's the correct approach but: it works for me. No more Oops until now, the scanner module can be unloaded even if the application was killed or the scanner was unplugged during scanning. And it works with GT6801-based no-bulk-out-endpoint scanners. See scanner-endpoint.dif. By the way: scanner.c lists version 0.4.8 but scanner.h has: #define DRIVER_VERSION "0.4.6". Bye, Henning
scanner-newids.dif
Description: video/dv
scanner-endpoint.dif
Description: video/dv
