From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] usb/serial control open
Date: Sun, 23 Mar 2014 17:41:34 -0700 [thread overview]
Message-ID: <20140324004134.673DBB827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 23 Mar 2014 20:32:07 EDT." <b77e121bfb2adb22b182f72bea92e76a@brasstown.quanstro.net>
On Sun, 23 Mar 2014 20:32:07 EDT erik quanstrom <quanstro@quanstro.net> wrote:
> > > i think it is even easier to set the state up properly with cpurc or
> > > consolefs' configuration file, and have the various programs not even
> > > care that they're talking to a serial port.
> >
> > Not my experience. Occasionally programs do have to care about
> > some serial port parameters and if such a program crashes you
> > have a partially working interface. Think CTS/RTS state etc.
>
> doesn't sound like the common case. in any event, seems like a
> program fiddling with CTS/RTS should do the whole setup, especially
> if it plans on crashing. :-)
The issue is program A can leave things in non-working order
and program B running after A has to deal with this. This is
no different from bringing up a system in a known good state.
next prev parent reply other threads:[~2014-03-24 0:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 18:09 erik quanstrom
2014-03-23 18:34 ` Gorka Guardiola
2014-03-23 18:55 ` erik quanstrom
2014-03-23 19:47 ` Gorka Guardiola
2014-03-23 19:55 ` Gorka Guardiola
2014-03-23 20:32 ` erik quanstrom
2014-03-23 21:08 ` Gorka Guardiola
2014-03-24 1:49 ` erik quanstrom
2014-03-23 21:32 ` Bakul Shah
2014-03-23 21:53 ` erik quanstrom
2014-03-23 22:02 ` Bakul Shah
2014-03-24 0:32 ` erik quanstrom
2014-03-24 0:41 ` Bakul Shah [this message]
2014-03-23 5:04 ` lucio
2014-03-23 19:53 ` Gorka Guardiola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140324004134.673DBB827@mail.bitblocks.com \
--to=bakul@bitblocks.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).