Date: Tue, 29 Apr 2014 22:44:15 -0700 From: Nathan Whitehorn <nwhitehorn@freebsd.org> To: Marcel Moolenaar <marcel@freebsd.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r262957 - in head/etc: etc.arm etc.ia64 etc.mips etc.powerpc etc.sparc64 Message-ID: <53608DAF.7070606@freebsd.org> In-Reply-To: <201403092106.s29L6M3D056313@svn.freebsd.org> References: <201403092106.s29L6M3D056313@svn.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/09/14 14:06, Marcel Moolenaar wrote: > Author: marcel > Date: Sun Mar 9 21:06:22 2014 > New Revision: 262957 > URL: http://svnweb.freebsd.org/changeset/base/262957 > > Log: > Change the terminal type/class for enabled serial lines to 3wire. This > allows us to change the uart(4) driver to not hardcode specific line > settings for the serial console. > > A terminal type of 3wire makes sure the console still works when no DCD > signal is present, which preserves behviour. When it is known that the > terminal server (or DCE in general) provides DCD, a terminal type/class > of std can be used. This has the effect of being logged out when one > disconnects from the console -- improving security overall. > > Likewise, when uart(4) does not fixate the baudrate, one can change > the terminal type/class to set a specific baudrate. An operator can use > this to change the console speed mid-flight, without needing a reboot. > Of course it helps in this respect if and when the firmware can be > configured from the OS. > > The above mentioned capabilities depend on uart(4) being changed, which > is to happen next. > Should we set onifconsole for x86 UARTs as well? That enables them if they are the kernel console and is probably a user friendliness improvement. -Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53608DAF.7070606>