On Thu, Jan 31, 2002 at 02:11:23PM -0500, Roland McGrath wrote: > > Do I use a third thread for assert_dtr? If I need to assert the dtr, the > > only strategy I can think of is to open in blocking mode. However, if I use > > synchronous RPC, this is better done in a seperate thread. I don't know how > > to assert the dtr otherwise. > > You don't need an additional thread, because you are never reading or > writing while keeping DTR low (you can't, since the way you keep DTR low is > to close the terminal).
Sorry, I was not clear in my earlier reply. I was assuming that I would keep the ioport open even after deserting the DTR, but deallocating it is also a good idea. To do it cleanly, I think I will have to interrupt the reader and writer rpcs if necessary, so I don't need to rely on the error value (EMIG_SERVER_DIED or so) to find out what happened. Mmmh. I will have to think a bit longer about this. The good news is that the exact way how the open is done (incl the dtr handling) and setting the modem bits is the only thing that is missing, then I can start to test it. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
