From: Tim Waugh <twaugh@redhat.com>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: Linux Kernel Maillist <linux-kernel@vger.kernel.org>
Subject: Re: Is printing broke on sparc ?
Date: Tue, 17 Apr 2001 13:42:57 +0100 [thread overview]
Message-ID: <20010417134257.J29490@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.32.0104161752010.18324-100000@filesrv1.baby-dragons.com>
In-Reply-To: <Pine.LNX.4.32.0104161752010.18324-100000@filesrv1.baby-dragons.com>; from babydr@baby-dragons.com on Mon, Apr 16, 2001 at 05:54:41PM -0700
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Mon, Apr 16, 2001 at 05:54:41PM -0700, Mr. James W. Laferriere wrote:
> # /etc/printcap
> #
> # Please don't edit this file directly unless you know what you are doing!
> # Be warned that the control-panel printtool requires a very strict format!
> # Look at the printcap(5) man page for more info.
> #
> # This file can be edited with the printtool in the control-panel.
>
> ##PRINTTOOL3## LOCAL POSTSCRIPT 300x300 letter {} PostScript Default {}
> lp:\
> :sd=/var/spool/lpd/lp:\
> :mx#0:\
> :sh:\
> :lp=/dev/lp0:\
> :if=/var/spool/lpd/lp/filter:
[...]
> /c#eodiecnyotai rhernili s to rpaemn
> s eehpo o-.ROLPR0 roif{\=sl:x
> /p:ao/lr
This looks like characters are getting missed out, rather than
anything getting garbled. The above characters all appear in
/etc/printcap in the order shown. Obviously there isn't enough
redundancy in /etc/printcap for the print-out to be useful despite
that. :-)
Please try adjusting the 'udelay (1)' lines in
drivers/parport/ieee1284_ops.c:parport_ieee1284_write_compat to be
larger delays (for example, try replacing the 1s with 2s, or 5s, and
see if that makes things better).
Let me know what you need to change to get it working.
Thanks,
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-04-17 12:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 0:54 Is printing broke on sparc ? Mr. James W. Laferriere
2001-04-17 12:42 ` Tim Waugh [this message]
2001-04-18 0:10 ` Mr. James W. Laferriere
2001-04-18 0:28 ` Mr. James W. Laferriere
2001-04-18 8:20 ` Tim Waugh
2001-05-16 0:14 ` Mr. James W. Laferriere
2001-05-16 0:27 ` kernel2.2.x to kernel2.4.x jalaja devi
2001-05-16 20:40 ` Alan Cox
2001-05-17 18:20 ` jalaja devi
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 12:37 Is printing broke on sparc ? Jesse Pollard
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=20010417134257.J29490@redhat.com \
--to=twaugh@redhat.com \
--cc=babydr@baby-dragons.com \
--cc=linux-kernel@vger.kernel.org \
/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