public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Lawyer <dave@lafn.org>
To: Ed Vance <EdV@macrolink.com>
Cc: "'Henrique Gobbi'" <henrique@cyclades.com>,
	linux-kernel@vger.kernel.org,
	"'linux-serial'" <linux-serial@vger.kernel.org>
Subject: Re: Char devices drivers
Date: Thu, 28 Mar 2002 13:39:43 -0800	[thread overview]
Message-ID: <20020328133942.A446@lafn.org> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A76EC@EXCHANGE>

On Mon, Mar 11, 2002 at 09:59:14AM -0800, Ed Vance wrote:
> On Mon, Mar 11, 2002, Henrique Gobbi wrote:
> > 
> > Can anyone explain what is the utility of the callout devices 
> > in the char drivers ???
> 
> To further confuse things, most vendors have a "back door" port
> configuration mechanism outside of termio(s)/sgtty. For example, Linux has
> the setserial command. There is less need for separate callout devices when
> the user can set a port to open with the desired flag values.

Setserial doesn't have facilities to set open flags for the ports.  The
reason cua isn't needed is that the programmer can make a ttyS port look
like a cua port by using the O_NONBLOCK or O_NDELAY flags.  However the
non-blocking flag will not only force an open when CD is asserted, but
will make all reads of the port non-blocking.  So the programmer can
change this if he wants after the port has opened.

So eliminating cua means more work for the programmer but less confusion
for users.  Overall, it's a good thing since there are many more users
than programmers.

			David Lawyer

  reply	other threads:[~2002-03-28 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-11 17:59 Char devices drivers Ed Vance
2002-03-28 21:39 ` David Lawyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-01 20:55 Ed Vance
     [not found] <mailman.1017359089.18550.linux-kernel2news@redhat.com>
2002-03-29  0:25 ` Pete Zaitcev
2002-03-11 14:35 Henrique Gobbi

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=20020328133942.A446@lafn.org \
    --to=dave@lafn.org \
    --cc=EdV@macrolink.com \
    --cc=henrique@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /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