From: Tim Waugh <twaugh@redhat.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Peter Osterlund <peter.osterlund@mailbox.swipnet.se>,
linux-kernel@vger.kernel.org
Subject: Re: Printing to off-line printer in 2.4.0-prerelease
Date: Thu, 4 Jan 2001 14:54:58 +0000 [thread overview]
Message-ID: <20010104145458.P23469@redhat.com> (raw)
In-Reply-To: <m2k88czda4.fsf@ppro.localdomain> <20010104112027.G23469@redhat.com> <20010104145229.E17640@athlon.random> <20010104142043.N23469@redhat.com> <20010104153910.A1507@athlon.random>
In-Reply-To: <20010104153910.A1507@athlon.random>; from andrea@suse.de on Thu, Jan 04, 2001 at 03:39:10PM +0100
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
On Thu, Jan 04, 2001 at 03:39:10PM +0100, Andrea Arcangeli wrote:
> As noted yesterday falling into parport_write will silenty lose data when the
> printer is off.
(Actually it depends; I think FIFO/DMA paths are fine, but yes, the
software implementation can lose data.)
> If it's not feasible to make parport_write reliable against
> power-off printer, then I recommend to loop in interruptible mode
> before entering the main loop (waiting the printer to power-on) like
> in latest patch from Peter.
Have I missed a patch? How do you know whether or not the printer is
on yet?
As I understand it, you can't guarantee anything about any of the
signals when the printer is off, so all you can do is look for
'suspicous' things (like 'no error' and 'paper out'). But some
printers do this during normal operation, and hence the LP_CAREFUL
switch.
Return -EIO when the printer is on and off-line is a bug, sure enough.
That's what the -EAGAIN patch was for, and Peter's patch fixes this
too.
But if you want to avoid losing data when your printer is off you need
to use LP_CAREFUL, and hope printing still works at all (depends on
your printer).
If this goes away:
if ((status & LP_PERRORP) && !(LP_F(minor) & LP_CAREFUL))
/* No error. */
last = 0;
then some people might not be able to print at all.
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-01-04 14:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 18:44 Printing to off-line printer in 2.4.0-prerelease Peter Osterlund
2001-01-03 19:13 ` Andrea Arcangeli
2001-01-03 21:00 ` Peter Osterlund
2001-01-03 21:35 ` Andrea Arcangeli
2001-01-04 0:08 ` Peter Osterlund
2001-01-04 0:41 ` Andrea Arcangeli
2001-01-04 1:09 ` Peter Osterlund
2001-01-04 1:39 ` Andrea Arcangeli
2001-01-04 11:17 ` Tim Waugh
2001-01-04 9:27 ` Tim Waugh
2001-01-04 13:50 ` Andrea Arcangeli
2001-01-04 11:20 ` Tim Waugh
2001-01-04 13:52 ` Andrea Arcangeli
2001-01-04 14:20 ` Tim Waugh
2001-01-04 14:39 ` Andrea Arcangeli
2001-01-04 14:54 ` Tim Waugh [this message]
2001-01-04 19:45 ` Peter Osterlund
2001-01-04 19:07 ` Peter Osterlund
2001-01-04 21:52 ` Tim Waugh
2001-01-05 0:33 ` Peter Osterlund
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 15:30 Jesse Pollard
2001-01-04 19:22 ` Gunther Mayer
2001-01-05 1:13 ` Jesse Pollard
2001-01-04 23:20 ` David Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010104145458.P23469@redhat.com \
--to=twaugh@redhat.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.osterlund@mailbox.swipnet.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox