Messages in this thread |  | | Date | Tue, 04 Sep 2001 16:22:19 +0300 | From | Michael Ben-Gershon <> | Subject | Re: lpr to HP laserjet stalls |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |