From: Michael Ben-Gershon <mybg@netvision.net.il>
To: linux-kernel@vger.kernel.org
Cc: Tim Waugh <twaugh@redhat.com>
Subject: Re: lpr to HP laserjet stalls
Date: Tue, 04 Sep 2001 16:22:19 +0300 [thread overview]
Message-ID: <3B94D58B.180860A2@netvision.net.il> (raw)
In-Reply-To: <3B93E289.7F121DE9@netvision.net.il> <20010903221142.J20060@redhat.com> <3B94B4E7.701C76FA@netvision.net.il> <20010904121523.Q20060@redhat.com> <3B94B93B.2B907DCF@netvision.net.il> <20010904122751.S20060@redhat.com>
Tim Waugh wrote:
>
> On Tue, Sep 04, 2001 at 02:21:31PM +0300, Michael Ben-Gershon wrote:
>
> For interrupt-driven mode: irq=auto dma=nofifo
> For PIO mode: irq=auto dma=none
> For DMA mode: irq=auto dma=auto
>
> You need to check the 'dmesg' output after parport_pc has loaded to
> see exactly what it will use though (i.e. whether it has detected
> usable hardware).
>
> The line that goes 'parport0: PC-style at 0x378 (0x778)' is the
> important one. Ignore the stuff in [brackets] at the end; if an
> interrupt is mentioned it is using it; if a DMA channel is mentioned,
> it is using it; and if it says 'using FIFO' then it's using the FIFO
> with programmed IO (rather than DMA).
OK. Firstly I rebuilt the kernel (2.4.9) with CONFIG_PARPORT_PC_FIFO
enabled. I also configured the parallel driver to be a module, to enable
easier testing.
I found that whatever I did, printing was not stalled (this must be a
result of CONFIG_PARPORT_PC_FIFO).
However, I found that dmesg gave some strange messages every so often under
PIO and DMA modes.
FIFO is stuck
BUSY timeout
dma write timed out
I don't know what they mean (the printing itself was not affected) but
I guess it would be better to avoid modes which give such messages.
At the moment I am loading the module with:
insmod parport
insmod parport_pc io=0x378,0xa800 irq=auto,auto dma=nofifo,nofifo
If there is anything more I should be doing, please let me know.
Thanks for all the help,
Michael Ben-Gershon
mybg@netvision.net.il
next prev parent reply other threads:[~2001-09-04 13:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 20:05 lpr to HP laserjet stalls Michael Ben-Gershon
2001-09-03 21:11 ` Tim Waugh
2001-09-04 0:20 ` Horst von Brand
2001-09-04 8:36 ` Tim Waugh
2001-09-04 0:56 ` Patrick Dreker
2001-09-04 8:50 ` Tim Waugh
2001-09-04 12:07 ` Patrick Dreker
2001-09-04 11:05 ` Michael Ben-Gershon
[not found] ` <3B94B4E7.701C76FA@netvision.net.il>
[not found] ` <20010904121523.Q20060@redhat.com>
2001-09-04 11:21 ` Michael Ben-Gershon
2001-09-04 11:27 ` Tim Waugh
2001-09-04 13:22 ` Michael Ben-Gershon [this message]
2001-09-04 13:27 ` Tim Waugh
2001-09-04 13:41 ` Michael Ben-Gershon
2001-09-04 13:48 ` Tim Waugh
2001-09-04 21:17 ` Michael Ben-Gershon
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=3B94D58B.180860A2@netvision.net.il \
--to=mybg@netvision.net.il \
--cc=linux-kernel@vger.kernel.org \
--cc=twaugh@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.