Re: Resurrecting the vax lcg framebuffer driver?

[David Brownlee <abs%netbsd.org@localhost>]

On 15 December 2014 at 17:11, Björn Johannesson <rherdware%yahoo.com@localhost> wrote:
> [...]
> If you want to play with this copy lcg.c to src/sys/arch/vax/vsa,
> uncomment both relevant lines in your kernel config ('lcg0 at' and
> 'wsdisplay at lcg0'), enable ttyw0 in /etc/ttys if you are using serial
> console. You can also enable ttyw1, ttyw2... for more vt:s.
> This is -current (7.99.1) tree but it should work on several earlier
> releases.
> The acceleration code is still in there but #ifdef'd out (LCG_NO_ACCEL).
>
> If you don't want to or can't compile a kernel you can get them from
> http://2.248.109.164/lcgfb.zip
> http://2.248.109.164/lcg.c
> both the accelerated and unaccelerated are in that zip file.
>
> Relevant lines from dmesg:
> lcg0 at vsbus0 csr 0x21801000 vec 440 ipl 15 maskbit 2
> lcg0: framebuffer size 1280x1024, depth 8 (magic 0x5)
> lcg0: using font QVSS (8x15), console size: 160x68
> wsdisplay0 at lcg0 kbdmux 1

Thanks for working on this - its good to see some fresh vax blood :)

Out of curiosity (and apologies if you've already tried this and I
missed it in the mail thread), but do all the acceleration ops fail? I
wondered it might be worth trying the simplest blkset(), with/without
some additional delays to see if they worked?