I'm assuming you want me to do this test tweak in the parport driver. If so
what file should I concentrate on?
From: Tim Waugh [mailto:firstname.lastname@example.org]
Sent: Thursday, March 22, 2001 4:32 PM
To: Cianfaglione, Mark [SKY:EQ10:EXCH]
Subject: Re: [PARPORT] FW: results from EPP mode
On Thu, Mar 22, 2001 at 03:49:10PM -0500, Mark Cianfaglione wrote:
> Mar 21 21:08:27 localhost kernel: parport0: Mode 0x2040 rejected by
Okay, we can ignore bit 13 (the '2') since that just signals to the
parport layer that we want address rather than data, and bit 6 (the
'4') means EPP. 'rejected by' means that peripheral knows that the
host wants to talk EPP, but it can't (as opposed to just being
confused by the negotiation), and the host should choose another mode.
It definitely speaks EPP rather than ECP? Also, what happens if you
just fool parport_negotiate into thinking that the peripheral is happy
(i.e. set xflag to 1 before the 'mode && !xflag' test)?
-- 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 : Fri Mar 23 2001 - 12:46:58 EST