Date: Mon, 01 Sep 2003 18:23:49 -0600 From: Scott Long <scottl@freebsd.org> To: John Birrell <jb@cimlogic.com.au> Cc: "Scott M. Likens" <damm@fpsn.net> Subject: Re: Question related to FreeBSD Serial Console... Message-ID: <3F53E315.6070401@freebsd.org> In-Reply-To: <20030902101451.F1311@freebsd1.cimlogic.com.au> References: <1062445674.59251.1.camel@acheron.livid.de> <3F53CF00.6020304@freebsd.org> <20030901232227.5F1D23A4C3@www.fastmail.fm> <3F53D645.2040501@freebsd.org> <20030902101451.F1311@freebsd1.cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
John Birrell wrote: > On Mon, Sep 01, 2003 at 05:29:09PM -0600, Scott Long wrote: > >>At one time I was working on patches to the loader to make the console >>speed configurable. At the time, at least, I didn't see any evidence >>that the settings were stored in the boot0 block, but maybe I was wrong. > > > AFAIK, the boot0 block uses bios int 0x16 to get a key-press and bios int > 0x10 to display a character, so in a situation where you *want* a serial > console, the F1 etc stuff can't be used unless the bios supports console > re-direction. And you have to live with whatever baud rate the bios sets. > > Once you get to boot2, then the serial console can work if set in /boot.config. > > It would be nice to have a boot.config setting for the baud rate. I have a > board here that allows bios re-direction to either the first or second serial > port at a fixed baud rate of 38400. I have to build boot2 with > BOOT_COMCONSOLE_SPEED=38400, and then the kernel with CONSPEED=38400 to > get all the ducks in a row. > > But it would be even nicer if both boot2 and the kernel would just work with > whatever baud rate the bios set. > This is exactly the problem that I was working on. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F53E315.6070401>