Date: Tue, 14 Aug 2018 15:17:50 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Kurt Jaeger <pi@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD blocks on BOCHS serial port Message-ID: <e3a47bcd-d07e-7f84-d97a-e819da19a290@grosbein.net> In-Reply-To: <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> <20180814024729.GM2118@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
14.08.2018 9:47, Kurt Jaeger wrote: >> 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 ? Sort of. Default serial driver for modern FreeBSD is uart(4) that documents these file names extremely concisely but does not explain their meaning. Legacy serial driver sio(4) has manual page describing them in detail.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e3a47bcd-d07e-7f84-d97a-e819da19a290>