From: "Paul Fulghum" <paulkf@microgate.com>
To: "Ivan Passos" <lists@cyclades.com>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>,
"Linux Serial List" <linux-serial@vger.kernel.org>
Subject: Re: CLOCAL and TIOCMIWAIT
Date: Mon, 26 Feb 2001 19:27:54 -0600 [thread overview]
Message-ID: <001101c0a05c$825f4150$0201a8c0@mojo> (raw)
In-Reply-To: <Pine.LNX.4.10.10102261651000.15230-100000@main.cyclades.com>
> A customer has just brought to my attention that when you try to use the
> TIOCMIWAIT ioctl with our boards and CLOCAL is enabled, you can't check
> changes in the DCD signal. He also mentioned that that is possible with
> the regular serial ports.
>
> As I understood, CLOCAL meant disabling DCD sensitivity, so if CLOCAL is
> disabled, no changes in DCD will be passed from hardware driver to the
> kernel or userspace. The way the serial driver is implemented, this is not
> true (i.e. even with CLOCAL enabled, you can still see DCD changes through
> the TIOCMIWAIT command).
>
> My question is: what's the correct interpretation of CLOCAL?? If the
> serial driver's interpretation is the correct one, I'll be more than happy
> to change the Cyclades' driver to comply with that, I just want to make
> sure that this is the expected behavior before I patch the driver.
>
> Thanks in advance for your comments.
>
> Later,
> Ivan
I believe CLOCAL only governs how DCD is used (or ignored) when opening
a port (must be active to complete open) and maintaining a connection
(negation signals hangup).
So CLOCAL controls the driver's 'interpretation' of DCD but
TIOCMIWAIT monitors the signal transitions without regard to
a predefined interpretation (let's the application decide what
to do with DCD).
Paul Fulghum
paulkf@microgate.com
next prev parent reply other threads:[~2001-02-27 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 0:56 CLOCAL and TIOCMIWAIT Ivan Passos
2001-02-27 1:27 ` Paul Fulghum [this message]
2001-02-27 3:19 ` Jeremy Jackson
2001-02-27 22:59 ` Theodore Y. Ts'o
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='001101c0a05c$825f4150$0201a8c0@mojo' \
--to=paulkf@microgate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lists@cyclades.com \
/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).