Martin Knoblauch writes:
> [also changeing the subject]
> Larry McVoy wrote:
> > : There are some very serious issues which come up even getting
> > : Xfree to a moderate level of acceleration.
> > How about to a simple level of working? Without any acceleration?
> > For most people, just having xterms and netscape working is enough.
> > I'm not a graphics or X person. Could someone who knows SGI's gfx
> > devices tell us how hard it would be to make the basics work?
> Probably not that hard if we gave away the documentation
> (do we have *documentation*) on the GFX cards low level interfaces.
> The major problem to me seems that each different architecture
> (XL, XZ/Elan/Extreme, IMPACT, CRM) has different interfaces.
> I am not sure that you can find a minimal subset of calls
> to make a very simple Xserver work (is Peter Daifuku on this
> list ? Mark Kilgard?).
The kernel graphics driver is quite complex, although that is in
large part due to the support for direct rendering in GL. The
hardware, except for Starter, XL, and O2, requires downloaded firmware.
Fortunately, basic firmware is downloaded by the PROM, so that it can
write on the screen. I believe that an X server can simply do the
same operations as the PROM, in regard to manipulating the frame buffer,
using the firmware interfaces. I have to investigate this in more
> - How much HW dependent stuff is in Xsgi itself?
> - Which of the DSOs in /usr/lib/X11/dyDDX are minimally
> needed to bring up an non-GLX Xserver?
> - How much efforts would it cost to compile the dyDDX
> stuff for Linux and distribute the binaries only
> (assuming that there is not to much HW stuff in Xsgi itself)?
The interfaces are very different. I tried mixing IRIX X server
and XFree86 X server source and did not get very far.