NetBSD/sys/arch/vax/vsa
mhitch a5e785cccf 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).
2004-03-19 20:12:07 +00:00
..
asc_vsbus.c
dz_ibus.c
dz_vsbus.c
hdc9224.c
hdc9224.h
if_ze_vsbus.c
lcspx.c Don't map the framebuffer again when attaching the lcspx driver if it was 2004-03-19 20:12:07 +00:00
leds.c
lkc.c
ncr.c
smg.c
vsbus.c
vsbus_dma.c