From: Tim Josling <tej@melbpc.org.au>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Philip.Blundell@pobox.com, linux-parport@torque.net
Subject: Re: [PATCH] to drivers/parport/ieee1284_ops.c to fix timing dependent hang
Date: Sat, 22 Mar 2003 20:23:44 +1100 [thread overview]
Message-ID: <3E7C2BA0.4040100@melbpc.org.au> (raw)
In-Reply-To: 1048278154.6017.2.camel@ixodes.goop.org
Jeremy,
Good to know someone has read my email.
According to my reading of the code, it should only happen in polled
mode, but I have only one week of experience looking at kernel source.
So it should be a work-around, assuming interrupts work on the parallel
port on your system :-). It is an very vexing problem, as I'm sure you know.
By the way, LJ1100s tend to get page feeding problems about the time the
warranty runs out, but HP has a free kit you can order to fix the problem.
Tim Josling
Jeremy Fitzhardinge wrote:
> On Wed, 2003-03-19 at 00:08, Tim Josling wrote:
>
>>I have an HP1100 printer and since I upgraded to a faster CPU the
>>printer has started hanging. The problem persisteed across 2.0 2.2 and
>>2.4 kernel versions. I am running Red Hat Linux 8.0 on a Compaq Armada E500.
>>
>>The problem occurs intermittently. The symptom is that the 'buffer
>>contains data' light stays on on the printer, but data transfer stops.
>
>
> Ah, so that's why that happens. I've been getting the same thing with
> my LJ1100.
>
> Is this just in polled mode? Does using interrupts constitute a
> work-around for the hang?
>
> J
>
>
>
next prev parent reply other threads:[~2003-03-22 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 8:08 [PATCH] to drivers/parport/ieee1284_ops.c to fix timing dependend Tim Josling
2003-03-21 20:22 ` Jeremy Fitzhardinge
2003-03-22 9:23 ` Tim Josling [this message]
2003-03-22 17:44 ` [PATCH] to drivers/parport/ieee1284_ops.c to fix timing dependent hang Jeremy Fitzhardinge
2003-03-22 20:31 ` Tim Josling
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=3E7C2BA0.4040100@melbpc.org.au \
--to=tej@melbpc.org.au \
--cc=Philip.Blundell@pobox.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@torque.net \
/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