Date: Wed, 04 Jun 1997 08:37:01 -0700 From: Paul Traina <pst@shockwave.com> To: Doug Rabson <dfr@nlsystems.com> Cc: cvs-committers@freebsd.org, cvs-all@freebsd.org, cvs-sys@freebsd.org Subject: Re: cvs commit: src/sys/i386/isa sio.c sioreg.h Message-ID: <199706041537.IAA09916@precipice.shockwave.com> In-Reply-To: Your message of "Wed, 04 Jun 1997 10:57:03 BST." <Pine.BSF.3.95q.970604104412.346Z-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Doug Rabson <dfr@nlsystems.com> Subject: Re: cvs commit: src/sys/i386/isa sio.c sioreg.h On Tue, 3 Jun 1997, Paul Traina wrote: > pst 1997/06/03 21:52:41 PDT > > Modified files: > sys/i386/isa sio.c sioreg.h > Log: > If the boot blocks were using the serial port, read the system console > speed using the boot blocks, instead of a hardcoded value stuck in the > kernel. This way, you can have systems using the same kernel but differe >>nt > console speeds. > > Add a sysctl entry for changing the system console speed. > Lock the user tty speed to match the system console speed. > > Nuke CONSPEED. What about when you are using the port for serial gdb and didn't boot from it? What speed will it be set to then? I often use serial gdb way before I can think about setting the speed with sysctl and debugging over 9600 is pointlessly painful. That's what the sysctl is for. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706041537.IAA09916>