From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "R.L. Horn" <lists@eastcheap.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)
Date: Sat, 14 Jun 2008 10:29:00 +0100 [thread overview]
Message-ID: <20080614102900.6830ed46@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <alpine.LNX.1.00.0806131635260.1294@hani.compact.internal>
> Setting the baud rate to B0 clears both (as per SUS).
>
> Subsequently setting the baud rate to something other than B0 leaves the
> control lines low.
>
> As it happens, apart from the fact that it breaks minicom, I actually prefer
> this behavior.
What happens after you go from B0->Banythingelse should depend on the
termios settings at that point. This sounds like a bug therefore.
If you want that behaviour intentionally set B0, after this termios
call then set CLOCAL before changing the baud back.
I'll take a look at this next week.
Alan
next prev parent reply other threads:[~2008-06-14 9:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 21:36 2.6.25.3: serial problem (minicom) R.L. Horn
2008-06-14 9:29 ` Alan Cox [this message]
2008-06-15 7:04 ` R.L. Horn
2008-06-16 10:13 ` Alan Cox
2008-06-17 4:22 ` R.L. Horn
2008-06-17 8:58 ` Alan Cox
2008-06-17 11:03 ` R.L. Horn
2008-06-18 0:15 ` Hans-Peter Jansen
2008-06-18 17:55 ` Alan Cox
2008-06-18 20:07 ` Olivier Galibert
2008-06-19 8:20 ` R.L. Horn
2008-06-19 23:46 ` Hans-Peter Jansen
2008-06-20 11:22 ` R.L. Horn
2008-06-17 10:50 ` R.L. Horn
-- strict thread matches above, loose matches on Subject: below --
2008-05-15 19:06 Chris Rankin
2008-05-16 3:23 ` Andrew Morton
2008-05-16 7:28 ` Chris Rankin
2008-05-16 17:33 ` Jay Cliburn
2008-05-17 12:29 ` Chris Rankin
2008-05-17 13:22 ` Jay Cliburn
2008-05-17 13:32 ` Jay Cliburn
2008-05-17 14:49 ` Chris Rankin
2008-05-17 15:10 ` Jay Cliburn
2008-05-17 18:46 ` Bart Van Assche
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=20080614102900.6830ed46@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@eastcheap.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