You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With cups 1.2.10 on NetBSD (i386, 4.0_BETA2), printing to an HP 1320 attached via USB fails. It works with 1.1.23. NetBSD's ulpt(4) driver does not support reading from USB printers, but because use_bc=1, cups tries to read and the usb driver hangs when no data is forthcoming.
With the attached patch (which is in pkgsrc/print/cups), I was able to print a test page.
Fixing this correctly is tricky; one can't assume a printer is present at configure time (especially for pkgsrc which does bulk builds for binary packages). NetBSD may in the future support the backchannel on ulpt(4). So probably the best approach is to read from the device, but with a timeout, and essentially fall back to use_bc=0 if nothing is read.
The text was updated successfully, but these errors were encountered:
* NetBSD's ulpt driver currently does not support the
* back-channel...
*/
use_bc = 0;
+#else
/*
Disable backchannel data when printing to Brother, Canon, or
Minolta USB printers - apparently these printers will return
the IEEE-1284 device ID over and over and over when they get
@@ -91,6 +100,7 @@
strcasecmp(hostname, "Canon") &&
strcasecmp(hostname, "Konica Minolta") &&
strcasecmp(hostname, "Minolta");
+#endif /* NetBSD */
Version: 1.2.8
CUPS.org User: gdt
With cups 1.2.10 on NetBSD (i386, 4.0_BETA2), printing to an HP 1320 attached via USB fails. It works with 1.1.23. NetBSD's ulpt(4) driver does not support reading from USB printers, but because use_bc=1, cups tries to read and the usb driver hangs when no data is forthcoming.
With the attached patch (which is in pkgsrc/print/cups), I was able to print a test page.
Fixing this correctly is tricky; one can't assume a printer is present at configure time (especially for pkgsrc which does bulk builds for binary packages). NetBSD may in the future support the backchannel on ulpt(4). So probably the best approach is to read from the device, but with a timeout, and essentially fall back to use_bc=0 if nothing is read.
The text was updated successfully, but these errors were encountered: