Path: utzoo!censor!geac!jtsv16!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!CUNYVM.BITNET!CCVQC
From: CCVQC@CUNYVM.BITNET (Christopher Vickery)
Newsgroups: comp.windows.x
Subject: Re: Does TIGA support X server well?
Message-ID: <8908021541.AA19196@ATHENA.MIT.EDU>
Date: 2 Aug 89 14:34:05 GMT
References: <erik!randy@UUNET.UU.NET>
Organization: The Internet
Lines: 49


        I can't say anything about TIGA, but I can pass on some of the
issues we're dealing with in porting X to an 82786 based board.

OS: Intel's RMX operating system.  "real-time, multitasking"
Display:  SBX-279 attached to SBC/386-24.  The SBX-279 has its own 80188
        processor, RAM, ROM, and graphics memory.  It also has an 82786
        graphics processor that draws from graphics memory.  Windows and
        bitmaps are '786 primitives.  The interface between the '386 and the
        '279 is an 8-bit bus (the "SBX bus").  The 80188 interprets the
        byte stream that passes over the SBX bus.  Mouse and keyboard are
        connected to the '279 and handled by the '188.  SBC/386-24 is a
        Multibus I board.

Some issues:
        1.  Where do you put the windows?  You could create a pseudo frame-
buffer in '386 memory, but then you would have to copy every change over the
SBX bus to get the display updated.  Advantage would be to be able to use
a lot of the sample server code from MIT to maintain the pseudo frame buffer.
Or, you could create a '786 window or bitmap for every X window or pixmap, but
the '786 can't handle large numbers of windows; more than a few being displayed
at a time causes problems.  How many depends on the bits per pixel and their
horizontal layout.  Our compromise:  after an initial implementation using
a pseudo framebuffer (we're working on it now), we'll use '786 windows for
the root and each first level window in the tree.  All windows below that
will be bitmaps that we'll blit into place on the first level windows.  Note
that this gives us automatic backing store for all windows.

        2.  The preliminary version of the '279 firmware does not give us
the control we need over mouse and keyboard events, but this is expected to
be cleared up in the next release.

        3.  There is no acoustic signal available with the '279 for a terminal
bell.

        4.  The ideal solution would be to program the X server in the 80188
directly, and use the SBX bus as the "reliable byte stream" used for the X
protocol.  We don't have the development tools to do that right now.

    I believe that there have been some PC-based X servers that use the '786.
AT&T?  Perhaps someone could pass on info about them.

    The '279 costs about $2k (less once you have the support software).

    I have a brief tech report on our work to date ("issues and strategies")
if you are interested.

Christopher Vickery
Queens College of CUNY