Thanks...
I've noticed that if I read data from the parport in ECP mode it will ALWAYS
return the size of the buffer no matter how much data is actually gathered.
Well... Except in an error condition. I would think that the parport module
will return the number of "filled" data points as opposed to the size of the
buffer... Am I missing something??? (I have done that a lot... Ask my
wife...)
Mark
-----Original Message-----
From: Tim Waugh [mailto:twaugh@redhat.com]
Sent: Monday, April 23, 2001 11:30 AM
To: Cianfaglione, Mark [SKY:QD43:EXCH]
Cc: linux-parport@torque.net
Subject: Re: [PARPORT] Nibble mode???
On Mon, Apr 23, 2001 at 10:56:23AM -0400, Mark Cianfaglione wrote:
> Apr 21 20:47:57 localhost kernel: parport0: cpp_mux: aa55f00f52ad51(87)
> Apr 21 20:47:57 localhost kernel: parport0: cpp_daisy: aa5500ff(80)
> Apr 21 20:47:57 localhost kernel: parport0: assign_addrs: aa5500ff(80)
> Apr 21 20:47:57 localhost kernel: parport0: In mode 0x04
> Apr 21 20:47:57 localhost kernel: parport0: Using nibble mode
> Apr 21 20:47:57 localhost last message repeated 2 times
> Apr 21 20:47:57 localhost kernel: parport0: device reported incorrect
> length field (105, should be 107)
> Apr 21 20:47:57 localhost kernel: parport0: In compatibility (forwardidle)
> mode
This is just debug output. Parport uses nibble mode to collect Device
ID information at the moment.
Tim.
*/
-- 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 : Mon Apr 23 2001 - 14:47:29 EDT