Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
QVSS driver: How can I make it available?
14 views
Skip to first unread message
Charles Dickman
Jul 2, 2015, 5:59:09 PM7/2/15
to
I have been working on a driver for the QVSS/VCB01 qbus frame buffer,
when time permits, since last December.
I want to share it, but don't know how to make it easily available. I
can put it on by internet server, but it might get overwhelmed by the
5 people in the world interested. There are about 4 new source files
and half a dozen or more changes to miscellaneous sys/arch/vax
directory files.
FWIW, I have it working so that multiple pseudo terminals are
available. The LK401 keyboard is working. A mouse device is created,
but I have not tried any of the mouse functions (I have a mouse, but
not the proper cable kit for the VCB01). It is attached by the ws
driver. The qvss scanmap is used so that it scrolls faster than when
using a static frame buffer.
I have played with vi and I played worms for a couple weeks to see if
anything would panic.
Things to do:
- console on qvss (The qvss is console on KA630, but not KA650. I have
a KA630, but not enough memory for NetBSD.)
- mouse testing
- screen text other than 128 x 57 text (something closer to 80 x 25 is
more legible)
- the serial port driver should be tested with something more than a keyboard
-chuck
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
when time permits, since last December.
I want to share it, but don't know how to make it easily available. I
can put it on by internet server, but it might get overwhelmed by the
5 people in the world interested. There are about 4 new source files
and half a dozen or more changes to miscellaneous sys/arch/vax
directory files.
FWIW, I have it working so that multiple pseudo terminals are
available. The LK401 keyboard is working. A mouse device is created,
but I have not tried any of the mouse functions (I have a mouse, but
not the proper cable kit for the VCB01). It is attached by the ws
driver. The qvss scanmap is used so that it scrolls faster than when
using a static frame buffer.
I have played with vi and I played worms for a couple weeks to see if
anything would panic.
Things to do:
- console on qvss (The qvss is console on KA630, but not KA650. I have
a KA630, but not enough memory for NetBSD.)
- mouse testing
- screen text other than 128 x 57 text (something closer to 80 x 25 is
more legible)
- the serial port driver should be tested with something more than a keyboard
-chuck
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-...@muc.de
Felix Deichmann
Jul 3, 2015, 2:02:33 AM7/3/15
to
2015-07-02 23:58 GMT+02:00 Charles Dickman <c...@chdickman.com>:
> I want to share it, but don't know how to make it easily available. I
> can put it on by internet server, but it might get overwhelmed by the
> 5 people in the world interested. There are about 4 new source files
> and half a dozen or more changes to miscellaneous sys/arch/vax
> directory files.
If I am one of the 5 people, I can give it a try in August/September
> I want to share it, but don't know how to make it easily available. I
> can put it on by internet server, but it might get overwhelmed by the
> 5 people in the world interested. There are about 4 new source files
> and half a dozen or more changes to miscellaneous sys/arch/vax
> directory files.
at the earliest.
> - console on qvss (The qvss is console on KA630, but not KA650. I have
> a KA630, but not enough memory for NetBSD.)
with enough memory, but don't know if qvss is console on these.
KA660 was also used in something called "VAXstation 4"...
> - mouse testing
A strange cable and "puck" came with my QVSS.
Is the custom bootloader needed, and did you fix allocation of Qbus
memory space?
Regards
Felix
Charles Dickman
Jul 6, 2015, 9:24:09 PM7/6/15
to
On Fri, Jul 3, 2015 at 2:02 AM, Felix Deichmann <m4j0...@gmail.com> wrote:
> Is the custom bootloader needed, and did you fix allocation of Qbus
> memory space?
The bootloader has to load 64kb below the framebuffer start. The
> Is the custom bootloader needed, and did you fix allocation of Qbus
> memory space?
kernel has to be small enough to load below that.
In qba_attach(), each page in the qbus space is tested and if it is
valid memory it is removed from the sgmap.
0 new messages