Hi, On Wed, Dec 25, 2002 at 05:35:52PM +0100, Oliver Neukum wrote: > [..] > > | There is a small test program (hp_scan.c -- appended below) that can > > | be used to test the scanner device if it's an HP scanner that supports > > | SCL (Scanner Control Language). Known HP scanner that support SCL are > > | the 4100, 5200, 6200, the 6300 -- note that the 4200 is *not* > > | supported since it does not understand SCL; it's also strongly > > | suspected that the 3300 and the PhotoSmart S20 are not SCL compliant. > > | Hp_scan.c's purpose is to test the driver without having to > > | retrieve/configure SANE. Hp_scan.c will scan the entire bed and put > > | the output into a file called 'out.dat' in the current directory. The > > | data in the file is raw data so it's not very useful for imaging. > > > > Should a C program that works with some old HP scanners be really > > included in kernel documentation? I don't think so. If necessary, I > > can put it on a website and add a link here. > > How does it hurt having it in the kernel?
It can confuse the user. I got a question once from a person who didn't know what to do with this file. He thought he needed to put it into the kernel somehow. And he didn't even have an HP scanner. Anyway, I don't mind keeping it. > > Without getting SANE (or another user space application), the user > > can't do much with his scanner anyway. > > But it'll show him whether to use scanner.o or hpusbscsi.o By the way: should I add a paragraph about hpusbscsi and the microtek driver? At least to point out that they are needed for some scanners? Are there any other "special" USB scanner drivers that should be mentioned? > > | **NOTE**: In later kernels (2.3.38+), a new filesystem was introduced, > > | usbdevfs. To mount the filesystem, issue the command (as root): > > > > Isn't this called "usbfs" now? > > In 2.5. We should not change the name in a stable series. It's not important for scanner.txt because I removed the whole section by a link to Documentation/usb/proc_usb_info.txt. However, someone already did the name change, at least in proc_usb_info.txt :-) | **NOTE**: The filesystem has been renamed from "usbdevfs" to | "usbfs", to reduce confusion with "devfs". You may | still see references to the older "usbdevfs" name. Bye, Henning ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
