From: Jesse Pollard <pollard@cats-chateau.net>
To: Gunther.Mayer@t-online.de (Gunther Mayer),
Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: linux-parport@torque.net, linux-kernel@vger.kernel.org
Subject: Re: Printing to off-line printer in 2.4.0-prerelease
Date: Thu, 4 Jan 2001 19:13:52 -0600 [thread overview]
Message-ID: <01010419215503.09343@tabby> (raw)
In-Reply-To: <200101041530.JAA92328@tomcat.admin.navo.hpc.mil> <3A54CD80.4A163381@t-online.de>
In-Reply-To: <3A54CD80.4A163381@t-online.de>
On Thu, 04 Jan 2001, Gunther Mayer wrote:
>Jesse Pollard wrote:
>> Originally, (wayback machine on) this was handled by a pull-up resistor
>> in the parallel interface, on the "off-line" signal. ANY time the printer
>> was powered off, set offline, or cable unplugged, the "off-line" signal
>> was raised by the pull-up. No data lost.
>>
>> Now the parallel interface is bidirectional, and can have multiple devices
>> attached - this "fix" cannot be used. The interface is now more of a
>> buss than a single attached interface, and signals from a missing device
>> (powered off or disconnected) are floating. They may float high or low,
>> and depending on the environment (and which end of the cable is unplugged)
>> any thing in between.
>
>Not true. Electrical characteristics for parallel port implementations/cards
>differ wildly, nevertheless most implementations have:
>- data lines: bidirectional (see datasheets)
>- signal lines: see datasheets, never floating !
>
>Floating signal lines are a silicon bug/bad engineering and have nothing
>to do with bidirectional interfaces !
I didn't mean to imply that it was - just that it is much harder to determine
if the device is attached or detatched. That depends on the characteristics of
the interface and the cable (acting as an antenna).
>
>Nowadays most integrated chips have internal signal line pull-ups internally, e.g.
>W83877TF says:
>-BUSY, ACK, PE, SLCT, ERR:
> TTL level input pin. This pin is pulled high internally.
>-AFD, STB, INIT, SLIN
> Open-drain output pin with 12 mA sink capability. Pulled up internally.
>-Data lines:
> TTL level bi-directional with 24 mA source-sink capability.
>
>Of course I would expect add-in cards to exist, with not so sophisticated chipsets
>and makers that have "forgotten" external pull-ups for economical reasons (2 cents :-)
>We should NOT care for broken hardware !!! I haven't seen any of these yet, even.
>
>On the other hand printer implmentations vary wildly, too.
>LJ1100: leave signal lines alone if powered off (0x7f)
> i.e. signal printer-not-ready ack-active out-of-paper
>DJ500: signal printer-error and off-line when powered off (0x87) !!!
> => Linux would dump data on this printer, if switched off.
>
>I think the current linux lp code tries to handle exotic/weird printers
>gracefully and leaves mainstream printers and users alone.
It all depends - I've seen printers work perfectly ... and yet others
completely fail. The Xerox 5700 printers wouldn't work if the cable were
over 9 feet long. They would if a high signal quality data cable were obtained,
worked at 15', but no longer than that. Even then, they would not identify
(and neither would Zerox) what happens when they were powered off (you loose
data).
And yet no problem with a HP laserjet at 40'.
And the signals do vary if it is unplugged at the printer end and not
at the host end (major difference - shielded cable works MUCH better).
--
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@cats-chateau.net
Any opinions expressed are solely my own.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-05 1:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 15:30 Printing to off-line printer in 2.4.0-prerelease Jesse Pollard
2001-01-04 19:22 ` Gunther Mayer
2001-01-05 1:13 ` Jesse Pollard [this message]
2001-01-04 23:20 ` David Ford
-- strict thread matches above, loose matches on Subject: below --
2001-01-03 18:44 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
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
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=01010419215503.09343@tabby \
--to=pollard@cats-chateau.net \
--cc=Gunther.Mayer@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@torque.net \
--cc=pollard@tomcat.admin.navo.hpc.mil \
/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