summaryrefslogtreecommitdiffstats
path: root/sys/conf
diff options
context:
space:
mode:
authorimp <imp@FreeBSD.org>2005-07-15 04:19:42 +0000
committerimp <imp@FreeBSD.org>2005-07-15 04:19:42 +0000
commit1fb171848d478cccca5e5a71f83044ee30f7178b (patch)
tree5ad294fee569464596402622ad83fc1adcfe0d90 /sys/conf
parenta5137833ce7bbc0093965a89ff8a853d293fe20c (diff)
downloadFreeBSD-src-1fb171848d478cccca5e5a71f83044ee30f7178b.zip
FreeBSD-src-1fb171848d478cccca5e5a71f83044ee30f7178b.tar.gz
Don't wait for the printer to become ready before allowing the open to
succeed. There are many printers that return status over the read channel, and if we wait for the status to become ready, then we can't find the status automatically. Linux doesn't wait, nor does it ever seem to really check the status in any meaningful way... If there really is a problem, the writes to the bulk out endpoint will still fail (like they would if the printer was ready and then ran out of paper or became unready). In addition, there are a number of printers being made that emulate the 'status' byte by returning '0' always rather than '0x18'. This fixes the EBUSY on open timeouts on those printer as well. Reviewed by: the defining silence on usb@
Diffstat (limited to 'sys/conf')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud