Re: Missing X binary

On Sat, 4 Dec 2021 at 09:06, Izumi Tsutsui <[email protected]> wrote:
>
> > - Finding out that Xorg 1.20 won't build, so switching pmax to using
> > 1.10 (similar to vax)
>
> Note 1.20 wsfb Xorg servers work on dreamcast and luna68k etc.
>
> > - X failing to start due to missing WSDISPLAYIO_GET_FBINFO support in
> > the cfb driver (now added)
>
> Maybe adding a missing WSDISPLAYIO_LINEBYTES ioctl will also work around.
>  https://nxr.netbsd.org/xref/xsrc/external/mit/xf86-video-wsfb/dist/src/wsfb_driver.c?r=1.37#447

I've added WSDISPLAYIO_GET_FBINFO to the dev/tc drivers for cfb, mfb,
sfb, sfbplus, tfb and xcfb (it really was a trivial change once I
worked out wth was going on and what was needed)

I wonder if the fallthrough ioctl handling should trap
WSDISPLAYIO_LINEBYTES and check for populate it from
WSDISPLAYIO_GET_FBINFO, rather than every driver having to implement?

> > - Thinking the keyboard mapping is all to hell, until I realised that
> > the key marked <X] sends The Correct Sequence To Delete A Character,
> > not ^H
>
> I wonder if "DEFAULT_TO_WSKBD" is worth or not.
>  https://nxr.netbsd.org/xref/external/mit/xorg/server/drivers/xf86-input-keyboard/Makefile?r=1.19#13
>
> (some other ports have "native to PS/2 keycode" tables derived from OpenBSD)

I have it set for pmax, and it _appears_ to be right (for gxemul
running DEC values of right), so I assume we want to be making more
use of it going forward?

David