Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 12 Mar 2005 18:31:19 +0100
From:      Marius Strobl <marius@alchemy.franken.de>
To:        Scott Long <scottl@samsco.org>
Cc:        cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/dev/uart uart_cpu_sparc64.c
Message-ID:  <20050312183119.F55534@newtrinity.zeist.de>
In-Reply-To: <423322C6.2070401@samsco.org>; from scottl@samsco.org on Sat, Mar 12, 2005 at 10:11:34AM -0700
References:  <200503121706.j2CH63ds065431@repoman.freebsd.org> <423322C6.2070401@samsco.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Mar 12, 2005 at 10:11:34AM -0700, Scott Long wrote:
> Marius Strobl wrote:
> > marius      2005-03-12 17:06:03 UTC
> > 
> >   FreeBSD src repository
> > 
> >   Modified files:
> >     sys/dev/uart         uart_cpu_sparc64.c 
> >   Log:
> >   In uart_cpu_getdev_console() when determinig whether we should use
> >   a serial console anyway because input-device is set to keyboard and
> >   output-device is set to screen but no keyboard is plugged in don't
> >   assume that a device node for the input-device alias exists. While
> >   this is true for RS232 keyboards (the node of the SCC and UART
> >   respectively which controls the keyboard doesn't disappear when no
> >   keyboard is plugged in) this assumption breaks for USB keyboards.
> >   It's most likely also not true for PS/2 keyboards but OFW doesn't
> >   reliably switch to a serial console when the potential keyboard is
> >   a PS/2 one which isn't plugged in so this couldn't be verified
> >   properly.
> >   
> >   Reported by:    Will Andrews <will@csociety.org>, obrien
> >   MFC after:      1 week
> >   
> >   Revision  Changes    Path
> >   1.18      +6 -4      src/sys/dev/uart/uart_cpu_sparc64.c
> 
> Does this fix the serial console problems with the Blade100?  If so then 
> I'll generate a March snapshot ASAP for it.
> 

I expect it to but I don't have a Blade 100 to verify myself. I hope
either Will or David will confirm that this fixes the problem seen on
Blade 100 but it was a bug nevertheless.

Marius



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050312183119.F55534>