Blaz Antonic asked about WSCONS framebuffer device driver;

> Related question: what facilities does my code have to provide to wscons
> (which ioctls and other calls) in order to have generic wscons X server
> work on top of it ? Only the GINFO ioctl and the *mmap() function ?

If the framebuffer memory is a plain main memory-alike, and is capable
to draw anything by process address space,  it's just fine to supply to
mmap call in an appropriate form.

> What
> should *mmap() be doing anyway, it is only a couple of lines of code,
> can somebody please clarify it ?

It provides the paddr of framebuffer memory to be used by VM to bind
process address space with it.

> Where do palette changes come in ?

#define WSDISPLAYIO_GETCMAP	_IOW('W', 66, struct wsdisplay_cmap)
#define WSDISPLAYIO_PUTCMAP	_IOW('W', 67, struct wsdisplay_cmap)

I'm a bit concerned about some VAX (high-end) graphics card are designed
specifically for VAX architecture to make CPU off-load to run.  Such the 
hardware arrangement is occasionally obstacle to port a plain Xserver, and
requires detail disclosure from DEC.

Toru Nishimura/ALKYL Technology