This is the mail archive of the cygwin-xfree@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Setting up X




> Oh, I'm building this on NT..  I'm mainly afraid of
> making this NT specific
> rather than the other way around.   Win9x should actually
> be able to address
> the ram, and the io ports directly.
>
> I know I've done direct screen writes in Win9x.
>
> DX is a good way though to ensure compatability, and I'm
> pretty sure that
> other than the initialization time there isn't a hit for speed.
>
> I don't know how well getio will run under 98.
>
> Since a driver isn't required to do the directx stuff,
> the getio stuff may
> be an NT only thing..


That is possible.  But getting XF86 executables work first for
NT would a good start.  At some point either we or any other
contributr
may come up with solution for Win9x.

Beside XGGI drivers from John Fortin would definitely run on Win9x.
XGGI supposed to be platform independent, though it is not really
an XFree86 itselg.  It does use XF86 drivers and libs.

Suhaib
>
>
> -----Original Message-----
> From: cygwin-xfree-owner@sourceware.cygnus.com
> [mailto:cygwin-xfree-owner@sourceware.cygnus.com]On
> Behalf Of Suhaib
> Siddiqi
> Sent: Thursday, November 11, 1999 5:38 PM
> To: Mike MacDonald; cygwin-xfree@sourceware.cygnus.com
> Subject: Setting up X
>
>
>
>
> Your choice.  You decide what is best.
> However with DirectX we need to make sure we use DirectX
> 3.0, not a
> higher version otherwise NT 4.0 will be a problem.
>
> Suhaib
>
> > -----Original Message-----
> > From: cygwin-xfree-owner@sourceware.cygnus.com
> > [mailto:cygwin-xfree-owner@sourceware.cygnus.com]On
> Behalf Of Mike
> > MacDonald
> > Sent: Thursday, November 11, 1999 5:38 PM
> > To: 'cygwin-xfree@sourceware.cygnus.com'
> > Subject: FW: Returned mail: Host unknown
> >
> >
> > There is a good chance though, still, that I'll have to
> > use DirectX to get
> > the memory pointer..  I don't think that it will be easy
> > to get access to
> > video memory any other way, even with mapmem..  getio on
> > the other hand..
> > Thats cool!!  :)
> >
> > -----Original Message-----
> > From: Suhaib Siddiqi [mailto:sssiddiqi@ipass.net]
> > Sent: Thursday, November 11, 1999 5:25 PM
> > To: Mike MacDonald
> > Subject: RE: Setting up X Sources
> >
> >
> >
> >
> > I agree with your approach.  Take your time and see if you could
> > come up
> > with a solution.  Thanks
> > Suhaib
> >
> >
> > > -----Original Message-----
> > > From: Mike MacDonald [mailto:mmacdona@tsi.gte.com]
> > > Sent: Thursday, November 11, 1999 5:25 PM
> > > To: 'ssiddiqi@ipass.net'
> > > Subject: RE: Setting up X Sources
> > >
> > >
> > > Well, getio will definately take care of the io problem
> > > if it works..  I
> > > think it will..  MapMem should deal with the memory
> > > mapping..  If it works..
> > > I think MapMem does IO too, but I think that getio does
> > > it faster.  Its
> > > mostly just a matter of stitching them into the
> > > os_support stuff now, and
> > > debugging.  Later maybe combining mapmem and getio into
> > > one driver..  Its
> > > the cleanest solution, and enough like what os2 is doing
> > > that most of the
> > > same code should apply..   I think os2 calls drivers a
> > > little different than
> > > windows, but thats the most of it..
> > >
> > > In other words, getting really close to having something
> > > that might work..
> > >
> >
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]