From owner-freebsd-stable@freebsd.org  Tue Aug 14 02:47:25 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE7251066839
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Tue, 14 Aug 2018 02:47:25 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6329F7A2DF
 for <freebsd-stable@freebsd.org>; Tue, 14 Aug 2018 02:47:25 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD))
 (envelope-from <pi@freebsd.org>)
 id 1fpPMn-000NBK-7P; Tue, 14 Aug 2018 04:47:29 +0200
Date: Tue, 14 Aug 2018 04:47:29 +0200
From: Kurt Jaeger <pi@freebsd.org>
To: Eugene Grosbein <eugen@grosbein.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: FreeBSD blocks on BOCHS serial port
Message-ID: <20180814024729.GM2118@home.opsec.eu>
References: <e0c6883a-ed3c-c48e-6821-05d0aa3eb034@tu-dortmund.de>
 <bc8f5df6-e338-a9fd-bdd7-e7e146cbcee7@grosbein.net>
 <661e5d36-6684-fae5-b325-f02ad570f2b4@tu-dortmund.de>
 <28c22017-7b01-63b0-946a-d0d255af16b2@grosbein.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <28c22017-7b01-63b0-946a-d0d255af16b2@grosbein.net>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2018 02:47:26 -0000

Hi!

> 14.08.2018 3:15, Alexander Lochmann wrote:
> 
> >> You should not rely on defaults and make sure you disable modem control/CD
> >> either explicitly (using stty(1) etc.) or implicitly by switching to /dev/cuau0
> >> instead of /dev/ttyu0. Flow control settings should match too, for both sides
> >> of virtual port.
> > Thx. I cannot even run 'stty < /dev/ttyu1' to see the current settings.
> > It simply blocks...
> 
> Use /dev/ttyu1.init to see defaults and /dev/ttyu1.lock to set/show
> locked defaults that cannot be changed without disabling a lock first.

Thanks for this pointer! Is that behaviour written down/explained
somewhere in the man pages ?

-- 
pi@FreeBSD.org         +49 171 3101372              2 years to go !