I'm still trying to get some sign of life out of a custom printer through the
Just to recap, I am using 2.4.0-test10 with everything compiled into the
kernel ezcept for parport, parport_pc and ppdev which are modules.
I've put some io trace in parport_pc and when it starts what I see is:
The 1284 mux negotiation takes place and finds no mux so it proceeds to the
daisy initialisation section and this appreas to be OK until the routine
parport_negotiate and this always times out.
(Of coursem when the driver is trying to set compatibility mode, there can be
no timeout and so this is OK but on all other operations, this routine will
When this happens, 0x7f is always read from the peripheral which is the value
that you will normally see if the peripheral is not driving the lines.
However, it cannot be that the peripheral is not capable of drivin the lines
because the driver reads sensible values from the peripheral when it is doing
the daisy chain commands.
I've tried this on two separate computers with the same result.
-- To unsubscribe, send mail to: email@example.com --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Tue Nov 14 2000 - 09:38:18 EST