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> In-Reply-To: <28c22017-7b01-63b0-946a-d0d255af16b2@grosbein.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180814024729.GM2118>