svn commit: r245848 - head/sys/boot/i386/libi386

[John Baldwin]

On Monday, February 04, 2013 4:43:36 am Sergey Kandaurov wrote:
> On 23 January 2013 22:34, John Baldwin <jhb at freebsd.org> wrote:
> > Author: jhb
> > Date: Wed Jan 23 18:34:21 2013
> > New Revision: 245848
> > URL: http://svnweb.freebsd.org/changeset/base/245848
> >
> > Log:
> >   Always update the hw.uart.console hint anytime a change is made to the
> >   comconsole setup.  Previously the hint would be set when if you set a
> >   custom port, but it would not be updated if you later set a custom speed.
> >
> >   Also, leave the hw.uart.console hint mutable so it can be overridden or
> >   unset by the user if needed.
> >
> >   Reviewed by:  kib (earlier version)
> >   MFC after:    1 week
> 
> Looks like this results in something wrong.
> I have a serial console at COM2 (uart1), but it chooses uart0
> (1016 == 0x3F8), compare .flags and the final hw.uart.console value.

Do you have a working console in the loader?  It is setting the hint based
on what the loader uses.  I use this to use COM2 for both loader and
kernel:

console="comconsole vidconsole"
comconsole_port=0x2f8

Note that when hw.uart.console is set, any flags set in hint.uart.X.flags
to set the console are ignored.  If you are not using -h in /boot.config or
setting 'console' for the loader to enable a serial console then the loader
should not be setting hw.uart.console (if it is, that is a bug to be fixed).
However, configuring the kernel to use a different serial console from the
loader seems very odd.  You should be able to manually set hw.uart.console in
loader.conf if you are doing that.

-- 
John Baldwin