Subject: CVS commit: src/sys/arch/vax/vsa
To: None <source-changes@NetBSD.org>
From: Michael L. Hitch <mhitch@netbsd.org>
List: source-changes
Date: 03/19/2004 20:12:07
Module Name:	src
Committed By:	mhitch
Date:		Fri Mar 19 20:12:07 UTC 2004

Modified Files:
	src/sys/arch/vax/vsa: lcspx.c

Log Message:
Don't map the framebuffer again when attaching the lcspx driver if it was
already mapped in the early console startup.

The software cursor isn't going to blink if we don't start it - set up the
callout when attaching.

Now that the cursor blink routine is actually called, blink the entire cursor
line rather than just the first pixel.

Don't try to clear the current cursor if the pointer to it hasn't been
initialized.  This seems to happen when using the display as console, but
not when using a serial console.

On early console startup, use the framebuffer sizes, not the character cell
size to compute how much to clear.

The lcspx display will now initialize when booting with the display console,
but the dz device is not detected and the keyboard will not work yet.  I
haven't tracked down why the dz device isn't found (it works fine when
using a serial console).


To generate a diff of this commit:
cvs rdiff -r1.1 -r1.2 src/sys/arch/vax/vsa/lcspx.c

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.