public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sun, 23 Mar 2003 07:31:50 +1100	[thread overview]
Message-ID: <3E7CC836.4000707@melbpc.org.au> (raw)
In-Reply-To: 1048355094.8537.11.camel@ixodes.goop.org



Jeremy Fitzhardinge wrote:
> On Sat, 2003-03-22 at 01:23, Tim Josling wrote:
> 
>>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.
> 
> 
> I'm wondering if a better fix might be to have something like:
> 
> 	if (wait * 2 > wait)
> 		wait *= 2;
> 
> at the bottom of the loop, so that the wrap-around doesn't happen.
> 

I tried
  wait *=2;
	if (wait > 10 * HZ)
		wait = 10 * HZ;
and that worked, so your theory would probably work. However to my mind 
it is a hack.

> 
>>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.
> 
> 
> Yes, I just installed it.  It suddenly made the printer useful again, so
> I've printing more, and seeing the hangs.  I enabled interrupts, which
> seems to work OK.
> 
> 	J

Good. That (enabling interrupts fixes the problem) tends to add credence 
to my theory.

Happy printing!

Tim Josling



      reply	other threads:[~2003-03-22 20:29 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   ` [PATCH] to drivers/parport/ieee1284_ops.c to fix timing dependent hang Tim Josling
2003-03-22 17:44     ` Jeremy Fitzhardinge
2003-03-22 20:31       ` Tim Josling [this message]

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=3E7CC836.4000707@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