linux-kernel - Re: 2.6.25.3: serial problem (minicom)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080614102900.6830ed46@lxorguk.ukuu.org.uk>
Date:	Sat, 14 Jun 2008 10:29:00 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"R.L. Horn" <lists@...tcheap.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25.3: serial problem (minicom)

>    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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/