public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net, mjr@znex.org
Subject: Re: [linux-usb-devel] Re: USBLP_WRITE_TIMEOUT too short for Kyocera FS-1010.
Date: Thu, 8 Aug 2002 19:52:29 -0400	[thread overview]
Message-ID: <20020808195229.C3414@sventech.com> (raw)
In-Reply-To: <200208082333.QAA11560@adam.yggdrasil.com>; from adam@yggdrasil.com on Thu, Aug 08, 2002 at 04:33:20PM -0700

On Thu, Aug 08, 2002, Adam J. Richter <adam@yggdrasil.com> wrote:
> Mark J Roberts writes:
> >Printing complicated postscript documents makes my Kyocera FS-1010
> >hit that timeout. I increased it to 240 seconds and the problem
> >seems to have disappeared.
> >
> >I guess there ought to be a blacklist or something.
> 
> 	I saw a similar thing a few weeks ago (under 2.5.27?) with the
> Hewlett-Packard 656C ink jet printer, which only occurred when I would
> send a page with images on it, so the printer really would need a long
> time before it was ready to accept more data.
> 
> 	I would hope that the kernel should be able to wait as long
> as the printer wants before the printer indicates that it is ready for
> more data.  I don't know if this is a bug in these printers' USB
> implementations or if it is a real kernel bug.  I just haven't had
> time to investigate it yet (and I no longer have access to that printer,
> although 656C's are only $30 at Fry's).

I suspect it's a bug in the kernel.

It sounds like the printer is NAKing all of the transfers while it's
busy flushing out the data sent to it. This is to be expected because it
can only store so much data and sending data is MUCH faster than it can
print it.

I think the problem is that the printer driver has a timeout. I don't
think it should. It just doesn't make sense in this case. I say let the
device NAK as long as it wants. It's the applications job to decide if
it's been too long or not.

JE


      reply	other threads:[~2002-08-08 23:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08 23:33 USBLP_WRITE_TIMEOUT too short for Kyocera FS-1010 Adam J. Richter
2002-08-08 23:52 ` Johannes Erdfelt [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=20020808195229.C3414@sventech.com \
    --to=johannes@erdfelt.com \
    --cc=adam@yggdrasil.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mjr@znex.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