Subject: Re: Accelerated LCSPX driver
To: Blaz Antonic <blaz.antonic@siol.net>
From: Tom G. Christensen <tom.christensen@get2net.dk>
List: port-vax
Date: 08/20/2004 14:08:04
On Mon, 16 Aug 2004, Blaz Antonic wrote:

> Hello,
> 
> Attached is HW accelerated LCSPX driver (for Vaxstation 4000/9x class
> machines). It is a drop-in replacement for existing dumb framebuffer
> driver, offers the same functionality and much more (full palette
> support, hardware cursor, HW acceleration, everything needed to get X
> running in unaccelerated mode, user-defined font support, etc.). It has
> been tested under NetBSD 2.0_beta.
> 
> While this driver is complete as far as console operation goes it still
> has few chunks of debugging code inside (which is commented out) and it
> hasn't been optimised yet. It is also missing HW acceleration support
> for X which will be added before i finish working on it so there's at
> least one more release coming up sometime in the future.
> 
> I would really appreciate it if people could try it out. Please try out
> different font types to see which one suits you best (and to flush out
> any bugs that might still be lurking in the driver, possibly with cursor
> which is the least tested part). Despite being "beta" this driver can
> cause no harm to your hardware, there's no risk involved in trying it
> out, it's considerably faster than existing driver so there's no reason
> for you not to try it if you have suitable hardware :-)
> 
I just found time to try out this driver on my VS4K/90.
The LCSPX is the Highres 72hz, 8 plane 4MPixel v1.1 variant.

Unfortunately I just got a blank screen almost as if it didn't think the
lcspx was the main console. Also the keyboard was beeping and bleeping
like mad so I guess that's where the console output went :(

Here's dmesg output from the boot:

NetBSD 2.0_BETA (GENERIC) #3: Fri Aug 20 12:31:35 CEST 2004
	tgc@atlantis:/usr/src/netbsd/2.0/obj_vax/sys/arch/vax/compile/GENERIC

MicroVAX 4000/90
cpu0: KA49
total memory = 81608 KB
avail memory = 76296 KB
mainbus0 (root)
vsbus0 at mainbus0
vsbus0: 8K entry DMA SGMAP at PA 0x27000000 (VA 0x8790f000)
vsbus0: interrupt mask 0
ze0 at vsbus0 csr 0x20008000 vec 410 ipl 15 maskbit -1
ze0: hardware address 08:00:2b:3c:5b:28
dz0 at vsbus0 csr 0x25000000 vec 524 ipl 15 maskbit 3
dz0: 4 lines
lkms0 at dz0
wsmouse0 at lkms0 mux 0
lcspx0 at vsbus0 csr 0x38000000 vec 440 ipl 15 maskbit 2
wsdisplay0 at lcspx0 kbdmux 1
wsmux1: connecting to wsdisplay0
wsdisplay0: screen 0-7 added (160x68, vt100 emulation)
asc0 at vsbus0 csr 0x26000080 vec 510 ipl 15 maskbit 1
asc0: NCR53C94, 25MHz, SCSI ID 6
scsibus0 at asc0: 8 targets, 8 luns per target
Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <QUANTUM, QM39100TD-S, N1B0> disk fixed
sd0: 8683 MB, 8057 cyl, 10 head, 220 sec, 512 bytes/sect x 17783249 sectors
sd0: sync (160.00ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
sd1 at scsibus0 target 3 lun 0: <SEAGATE, ST3600N, 8336> disk fixed
sd1: 500 MB, 1872 cyl, 7 head, 78 sec, 512 bytes/sect x 1025920 sectors
sd1: sync (160.00ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
sd1: no disk label
boot device: sd0
root on sd0a dumps on sd0b
root file system type: ffs

---

Note how it failed to find the keyboard?
I have that problem as well with the generic kernels. The keyboard is only
detected when I boot with the S3 switch in the 'up' position and the
console is on the serial line.

Here is dmesg from a generic kernel with the std lcspx driver:
NetBSD 2.0_BETA (GENERIC) #4: Fri Aug 20 13:32:22 CEST 2004
	tgc@atlantis:/usr/src/netbsd/2.0/obj_vax/sys/arch/vax/compile/GENERIC

MicroVAX 4000/90
cpu0: KA49
total memory = 81608 KB
avail memory = 76320 KB
mainbus0 (root)
vsbus0 at mainbus0
vsbus0: 8K entry DMA SGMAP at PA 0x27000000 (VA 0x8810f000)
vsbus0: interrupt mask 0
ze0 at vsbus0 csr 0x20008000 vec 410 ipl 15 maskbit -1
ze0: hardware address 08:00:2b:3c:5b:28
lcspx0 at vsbus0 csr 0x38000000 vec 440 ipl 15 maskbit 2
wsdisplay0 at lcspx0 kbdmux 1: console (160x68, vt100 emulation)
wsmux1: connecting to wsdisplay0
wsdisplay0: screen 1-7 added (160x68, vt100 emulation)
asc0 at vsbus0 csr 0x26000080 vec 510 ipl 15 maskbit 1
asc0: NCR53C94, 25MHz, SCSI ID 6
scsibus0 at asc0: 8 targets, 8 luns per target
Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <QUANTUM, QM39100TD-S, N1B0> disk fixed
sd0: 8683 MB, 8057 cyl, 10 head, 220 sec, 512 bytes/sect x 17783249 sectors
sd0: sync (160.00ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
sd1 at scsibus0 target 3 lun 0: <SEAGATE, ST3600N, 8336> disk fixed
sd1: 500 MB, 1872 cyl, 7 head, 78 sec, 512 bytes/sect x 1025920 sectors
sd1: sync (160.00ns offset 15), 8-bit (6.250MB/s) transfers, tagged queueing
sd1: no disk label
boot device: sd0
root on sd0a dumps on sd0b
root file system type: ffs

----

See the difference?
With the above the display is fine and no bleeping from the keyboard but 
also no keyboard input is possible.

-tgc

-- 
Tom G. Christensen - Email: tom.christensen@get2net.dk
Homepage: http://hjem.get2net.dk/tgc
Linux 2.6.7-1.494.2.2 on an i686