9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] usb/serial control open
Date: Sun, 23 Mar 2014 17:53:22 -0400	[thread overview]
Message-ID: <9838602a5db28f523fec74b5e8a9c2ab@brasstown.quanstro.net> (raw)
In-Reply-To: <20140323213208.A38E8B827@mail.bitblocks.com>

> A similar idea here would be to have a "default" command to
> for default settings. When a device is opened, it is
> initialized with these settings. The reason I like this is
> because then I don't need to teach every serial IO program
> what setting to use (often the other end is a dumb device
> requiring its own fixed and peculiar settings).

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.

rdb, for example, was one program that got this wrong.  it was setting
the baud, which backfired in some cases.  not doing anything is a better
solution.  you can always echo bxyz>/dev/eiaXXctl, assuming it really
is a serial line.  :-)

- erik



  reply	other threads:[~2014-03-23 21:53 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 [this message]
2014-03-23 22:02               ` Bakul Shah
2014-03-24  0:32                 ` erik quanstrom
2014-03-24  0:41                   ` Bakul Shah
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=9838602a5db28f523fec74b5e8a9c2ab@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).