Re: 2.4.19: drivers/usb/printer.c usblpX on fire

[Pete de Zwart <dezwart@froob.net>]

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

Yeah, that makes sense, it's not the kernel's job to take care of the
printers status beyond the basics.

Make the printer drivers like a pseudo-micro-kernel, have the basic printer
operations done in the kernel and have the rest of the functionality farmed
out to individual printer modules.

Ignoring the above, where should the functionality for the extended printer
operations reside?

In the print spooler? A separate process that deals with a bunch of printers?

If this is going off-topic for LKML where would be a better place to discuss
this?

	Pete de Zwart.

Around about 1052h 11/08/2002, Brad Hards emitted the following wisdom:
> So the kernel doesn't care about most of the error codes (since it isn't 
> interpreting the data stream), but there are some things that are noted for 
> historical reasons. Those things (like "out of paper" turn out to be widely 
> supported (or if not, are at least set to benign values). All the "unique" 
> error codes are a problem for userspace.
> 
> Does this make sense?

-- 
The real reason your computer crashed, thanx to the BOFH:
"Mailer-daemon is busy burning your message in hell."

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]