RE: XServer

["Suhaib Siddiqi" <ssiddiqi at inspirepharm dot com>]

Mike,
I am going to forward your message to XF86 Developers list.  I think
"gang of D four" (as known at Xfree86) at Xfree86 (David, David,
David and Dirk) who are the
orginal authors of XF86 might be able to give a good advice.
Once I receive an answer I will forward it to cygwin-xfree list.

BTW.  I added your name to cygwin-xfree URl under Developers.

Thanks for hard work,

Suhaib


> -----Original Message-----
> From: cygwin-xfree-owner@sourceware.cygnus.com
> [mailto:cygwin-xfree-owner@sourceware.cygnus.com]On Behalf Of Mike
> MacDonald
> Sent: Monday, November 15, 1999 12:27 PM
> To: 'cygwin-xfree@sourceware.cygnus.com'
> Subject: XServer
>
>
> My thinking now, for initial Xserver stuff..
>
>
> modify the current vga256 x server to initialize a full
> screen Directx in a
> 256 color mode for now..
>
> do a lock in xf86MapVidMem
>
> do an unlock in xf86UnMapVidMem
>
> I don't know if those sync up to work, (I'm not sure when
> X calls those
> functions) but thats my current thinking..
>
> I'm not sure how to handle the message loop, etc, but I'm
> sure it will get
> figured out.   Then, later, I suppose use either asm
> calls, or gdi for 2d
> primitives.
> It should be easy to move to higher color depths after
> its up and running.
>
> For the accelerated, I'm going to try using/modifying
> mapmem to provide
> memory mapping functionality, and getio for port access.
>
> For mouse, keyboard, ttys - mapmem, and getio.
>
> getio may not be fast enough, and mapmem might not map
> memory properly, but
> I'll hit that when I get to it..
>
>