Another question (s) related to ppdev driver.
1. No handshaking is done in PPSETMODE ioctl command. What is use of this
Doesn't using just PPNEGOT suffice.
2. What is use of PPSETPHASE command. Isnt this supposed to be handled
internally by the driver.
3. Also whats the use of PPDATADIR commnad. Driver shld automatically change
the data direction if I am reading after writing and writing after reading.
Why should user bother about all this.
Can somebody help me with these questions? Or point me to appropriate
documentation for ppdev driver.
> -----Original Message-----
> From: Greg Nelson [mailto:firstname.lastname@example.org]
> Sent: Monday, March 06, 2000 9:31 AM
> To: email@example.com
> Cc: firstname.lastname@example.org
> Subject: [PARPORT] Clean IEEE1284 termination
> I want to check something simple here (I'm working with kernel
> parport_ieee1284_terminate seems to be the only place where the
> handshaking is done to return the port to compatibility mode. (Good.)
> parport_negotiate seems to be the only place
> parport_ieee1284_terminate is called.
> My best understanding is that closing the port leads to calls to
> pp_release, parport_release (if claimed), and
> parport_unregister_device (if pdev non-NULL). I can't find anything
> that would guarantee, at the kernel level, that the port is cleanly
> returned to compatibility mode when the port is closed.
> Does this have to be done at the application level, by renegotiating
> compatibility mode or something like that?
> Greg Nelson
> -- To unsubscribe, send mail to: email@example.com --
> -- with the single word "unsubscribe" in the body of the message. --
-- To unsubscribe, send mail to: firstname.lastname@example.org --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Mon Mar 06 2000 - 16:00:39 EST