On Fri, 07 Sep 2001 19:49:42 +0100, Philip Blundell <philb@gnu.org> wrote:
>
> [ ... ]
>
> always 35 seconds long then it seems unlikely that it's caused by a
> byte being read in unexpectedly.
>
> Do you know what chip your parallel port uses?
>
> If you have any way to find out, it would be useful to know exactly what the
> bad data the printer is seeing is -- whether it's a data byte being
> duplicated, or random garbage being inserted in the middle.
>
> p.
>
>
dmesg output when parport loads is below.
I'm working on getting the data the printer sees when there's an error.
-- Dave Strauss
Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ...
Winbond chip at EFER=0x2e key=0x87 devid=52 devrev=17 oldid=ff
Winbond chip type 83627
Winbond LPT Config: cr_30=01 60,61=0378 70=07 74=03, f0=3a
Winbond LPT Config: active=yes, io=0x0378 irq=7, dma=3
Winbond LPT Config: irqtype=pulsed low, high-Z, ECP fifo threshold=7
Winbond LPT Config: Port mode=ECP
SMSC Super-IO detection, now testing Ports 2F0, 370 ...
0x378: FIFO is 16 bytes
0x378: writeIntrThreshold is 9
0x378: readIntrThreshold is 9
0x378: PWord is 8 bits
0x378: Interrupts are ISA-Pulses
0x378: ECP port cfgA=0x10 cfgB=0x48
0x378: ECP settings irq=7 dma=<none or set by other means>
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Fri Sep 07 2001 - 15:15:28 EDT