Date: Tue, 02 Sep 2003 08:39:30 -0700 From: "Scott M. Likens" <damm@fpsn.net> To: Bruce Evans <bde@zeta.org.au> Cc: current@freebsd.org Subject: Re: Question related to FreeBSD Serial Console... Message-ID: <1062517169.97043.3.camel@acheron.livid.de> In-Reply-To: <20030902175538.A617@gamplex.bde.org> References: <1062445674.59251.1.camel@acheron.livid.de> <20030901232227.5F1D23A4C3@www.fastmail.fm> <3F53D645.2040501@freebsd.org> <20030902101451.F1311@freebsd1.cimlogic.com.au> <20030902175538.A617@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--MIMEStream=_0+168898_0205880498192_98246127393 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-A4RY3mrI6STjKlGauX36" Mime-Version: 1.0 --=-A4RY3mrI6STjKlGauX36 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2003-09-02 at 01:33, Bruce Evans wrote: > About the original question: multiple consoles in the kernel are > unsupported in FreeBSD-4 but are standard in -current. Unfortunately, > their implementation is slightly incomplete even in -current. In > -current, you get them by booting with -D after booting using the > kern.console sysctl. The number of consoles is limited only by the > number of devices that support consoles. Low level console i/o (mainly > boot messages and other kernel messags printed by kernel printfs) is > then sent to and received from all the consoles, but for some reason > high-level console output (all i/o from/to /dev/console) is only sent > to the first console in the list. This should be easy to fix for > writes and ioctls though not so easy for reads. I think booting with > -Dh makes the serial console first and booting with -D makes the video > console first (if both are configured). The order can be changed using > the sysctl. Eh veh, 10 different answers to 1 question. The mailing list is doing it's job. But okay, yes I was wanting both consoles to be initialized at the same exact time really. =20 So I would guess then, -current would be best supported for this. That or find a motherboard with builtin serial console support. What a solution, was hoping for something more of an easy answer. But Thanks! > On Mon, 1 Sep 2003, Scott Long wrote: >=20 > > 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 consol= e > > >>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 wro= ng. >=20 > There are already too many places to set it. >=20 > > > 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 ser= ial > > > console, the F1 etc stuff can't be used unless the bios supports cons= ole > > > re-direction. And you have to live with whatever baud rate the bios s= ets. >=20 > I think boot0 is already full (unless you unportabalize it by expanding i= t > beyond one sector). It doesn't have its own serial i/o routines mainly > because there is no space for them. >=20 > > > Once you get to boot2, then the serial console can work if set in /bo= ot.config. > > > > > > It would be nice to have a boot.config setting for the baud rate. I h= ave a > > > board here that allows bios re-direction to either the first or secon= d serial > > > port at a fixed baud rate of 38400. I have to build boot2 with > > > BOOT_COMCONSOLE_SPEED=3D38400, and then the kernel with CONSPEED=3D38= 400 to > > > get all the ducks in a row. >=20 > The latter shouldn't be necessary. The kernel (i386 sio only) uses the > same speed that boot2 used if the kernel was booted with -h. It should > also use the same speed if the kernel was booted with -D. >=20 > > > But it would be even nicer if both boot2 and the kernel would just wo= rk with > > > whatever baud rate the bios set. > > > > This is exactly the problem that I was working on. >=20 > Unfortunately most BIOSes don't provide a way to set the speed. I'm not > sure that it even has a default. I always use 115200 bps, but at least h= e > old BIOS interface is limited to 9600 bps. I may work on this a bit soon > to make 921600 bps work. >=20 > Bruce --=20 "I think we ought to be out there doing what we do best - making large holes in other people's countries." - George Carlin --=-A4RY3mrI6STjKlGauX36 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/VLmxD2+AYUq0LpARAvRZAJ9ad2ZfIUd+xrhA+4HpGYaej1I3PQCgykSJ BXvstzEkRVKQgb7ZPjReO3M= =WbcR -----END PGP SIGNATURE----- --=-A4RY3mrI6STjKlGauX36-- --MIMEStream=_0+168898_0205880498192_98246127393--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1062517169.97043.3.camel>