Re: Getting X on Linux/SGI

["David S. Miller" <davem@jenolan.rutgers.edu>]

   From: "John Chen" <chen@betty.esd.sgi.com>
   Date: Wed, 18 Jun 1997 12:41:23 -0700

   I think you also need following stuff for Indy system with Newport graphic:

   1) Newport graphics spec.

I have this.

   2) A basic graphic driver that map RE chip to Xsgi's address
      space, so X can program RE registers

15 minutes of coding...

   3) This graphic driver also needs to set up graphic backend display
      id table and display mode registers (if X support only one visual,
      this step is simple), to program Cmap for cursor color
      and to program cursor registers for glyph and location.
      All of these work can also be done in X if driver map backend to X.

I can do this since I have #1, in fact I might be setting up the
backend display for one visual already in the text console driver I
wrote.  The way to manipulate the cursor and cmap is pretty much
documented in my text console driver as well, but I think some of the
actual cursor code is just pound define'd out but it is/was there.
(worse case you have to sift through the CVS history for the driver
and check out a version right before I snipped the code out if I in
fact did remove it at some point)

As for the input queue stuff, this has already been implemented on the
Sparc port because we were using SunOS Xsun binaries long ago, the
stock X11R6 sources use this mechanism anyways in the Sun frame buffer
support code, and their interface is very similar to IRIX's I think
(they call it VUID events).