| 1 |
Hi ?????????, |
| 2 |
on Thursday, 2006-06-22 at 22:22:30, you wrote: |
| 3 |
> sappho ~ # dmesg | grep -i parp |
| 4 |
> parport0: PC-style at 0x1fff13043bc (0x1fff13047bc), irq 8687936, dma |
| 5 |
> 0 |
| 6 |
> [PCSPP,TRISTATE,COMPAT,ECP,DMA] |
| 7 |
|
| 8 |
Seems OK, I wondered about the strange IRQ but this seems to be normal |
| 9 |
for SPARCs . However, it doesn't say anything about using a FIFO, which |
| 10 |
later it assumes was there. |
| 11 |
|
| 12 |
> lp0: using parport0 (interrupt-driven). |
| 13 |
> Partition check: |
| 14 |
> parport0: FIFO is stuck |
| 15 |
> parport0: BUSY timeout (1) in compat_write_block_pio |
| 16 |
|
| 17 |
The FIFO (if any) doesn't run empty because it thinks the printer was |
| 18 |
asserting the BUSY line. Hum...broken hardware? Are you sure this chip |
| 19 |
has a FIFO, or could it have been mis-categorized by the driver? |
| 20 |
You could try adding some printk()s to drivers/parport/parport_pc.c to |
| 21 |
get a better look at what's going on. |
| 22 |
|
| 23 |
> [...] but I don't |
| 24 |
> know what to specify as I/O address yet, I don't know if 0x1fff13043bc |
| 25 |
> is an acceptable address, I'll try it when tonight I have the chance |
| 26 |
> to |
| 27 |
> reboot the server (cannot reboot now, there are still other people |
| 28 |
> using |
| 29 |
> that server.) |
| 30 |
|
| 31 |
The address looks fine. I don't have a clue about Sun hardware but |
| 32 |
memory mapped I/O at this address seems common---Google finds several |
| 33 |
references to other people's hardware. Others seem to have had silimar |
| 34 |
problems, see http://cyberelk.net/tim/parport/archive/current/5042.html |
| 35 |
or for a more recent one, |
| 36 |
http://www.spinics.net/lists/sparclinux/msg00019.html |
| 37 |
The latter could apply to your BUSY line as well. |
| 38 |
|
| 39 |
cheers! |
| 40 |
Matthias |
| 41 |
|
| 42 |
-- |
| 43 |
I prefer encrypted and signed messages. KeyID: FAC37665 |
| 44 |
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665 |
Archives