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: [Fwd: cygwin-xfree Digest 9 Nov 1999 08:53:09 -0000 Issue 59]



Sorry, I have no control over cygwin-xfree digest.
I maintain only URL and update cygwin-xfree source tree, and
binaries.
I am forwarding it to cygwin-xfree list.  I hope someone in-charge
will
reply to you.

regards
Suhaib

> -----Original Message-----
> From: Jeffrey Juliano [mailto:juliano@cs.unc.edu]
> Sent: Tuesday, November 09, 1999 10:20 AM
> To: ssiddiqi@inspirepharm.com
> Subject: [Fwd: cygwin-xfree Digest 9 Nov 1999 08:53:09
> -0000 Issue 59]
>
>
> Hi,
>
> I'm subscribed to the digest version of the cygwin-xfree
> list.  below is
> a copy of the last email I got from that list.  If you
> look at the last
> two messages, you'll see that the names on the To: and
> From: lines have
> the wrong names on them.  The names have been switched so that the
> message looks like it was sent *by* the person it was
> actually sent
> *to*.
>
>   (well, actually, the *last* message doesn't count.  I
> mean the 2nd and
> 3rd last messages)
>
> Didn't know who to report this to, so I'm sending to you
> hoping you
> forward to the appropriate party.
>
> -jeff
>
>
> cygwin-xfree-digest-help@sourceware.cygnus.com wrote:
> >
> > cygwin-xfree Digest 9 Nov 1999 08:53:09 -0000 Issue 59
> >
> > Topics (messages 286 through 297):
> >
> > Xlib porting
> >         286 by: Tõnis Vaga <tvaga@math.ut.ee>
> >         287 by: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
> >
> > Driver for X11
> >         288 by: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
> >         289 by: Mike MacDonald <mmacdona@tsi.gte.com>
> >         290 by: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
> >         291 by: Mike MacDonald <mmacdona@tsi.gte.com>
> >         292 by: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
> >
> > FW: DGA
> >         293 by: Mike MacDonald <mmacdona@tsi.gte.com>
> >
> > XF86Sup
> >         294 by: Mike MacDonald <mmacdona@tsi.gte.com>
> >         295 by: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
> >
> > XF86SUP.SYS
> >         296 by: Mike MacDonald <mmacdona@tsi.gte.com>
> >
> > DGA, DirectX, XF86Sup.sys style port, etc.
> >         297 by: Federico Bianchi <bianchi@www.arte.unipi.it>
> >
> > Administrivia:
> >
> > To subscribe to the digest, e-mail:
> >         cygwin-xfree-digest-subscribe@sourceware.cygnus.com
> >
> > To unsubscribe from the digest, e-mail:
> >         cygwin-xfree-digest-unsubscribe@sourceware.cygnus.com
> >
> > To post to the list, e-mail:
> >         cygwin-xfree@sourceware.cygnus.com
> >
> >
> ----------------------------------------------------------
> ------------
> >
> >
> ----------------------------------------------------------
> --------------
> >
> > Subject: RE: Driver for X11
> > Date: Mon, 8 Nov 1999 15:17:32 -0500
> > From: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
> > To: "Mike MacDonald" <mmacdona@tsi.gte.com>,
> >      <cygwin-xfree@sourceware.cygnus.com>
> >
> > Hi!
> >
> > What is the easiest way to port X app to cygwin (under
> win95)? Do i really
> > need get all these X client and server files? They
> about 30M. I remember
> > Moonlight Creator uses b19 dll but did'nt need X server
> for running.
> > So, what files i should get and what not?
> >
> >  tonis
> >
> >
> ----------------------------------------------------------
> --------------
> >
> > Subject: RE: Driver for X11
> > Date: Mon, 8 Nov 1999 15:38:02 -0500
> > From: Mike MacDonald <mmacdona@tsi.gte.com>
> > To: "'cygwin-xfree@sourceware.cygnus.com'"
> >      <cygwin-xfree@sourceware.cygnus.com>
> >
> > The X-server files are of no use at the moment because
> they X-server
> > is not functional yet.  read the FAQ at
> > http://sourceware.cygnus.com/cygwin/xfree.
> >
> > You need X11 libs which are part of cygwin-xfree
> archive and link
> > your code to X libs as you do on UNIX.
> >
> > Suhaib
> >
> > > -----Original Message-----
> > > From: cygwin-xfree-owner@sourceware.cygnus.com
> > > [mailto:cygwin-xfree-owner@sourceware.cygnus.com]On
> > > Behalf Of T=F5nis Vaga
> > > Sent: Monday, November 08, 1999 6:36 AM
> > > To: cygwin-xfree@sourceware.cygnus.com
> > > Subject: Xlib porting
> > >
> > >
> > >
> > > Hi!
> > >
> > > What is the easiest way to port X app to cygwin (under
> > > win95)? Do i really
> > > need get all these X client and server files? They about
> > > 30M. I remember
> > > Moonlight Creator uses b19 dll but did'nt need X server
> > > for running.
> > > So, what files i should get and what not?
> > >
> > >  tonis
> > >
> > >
> > >
> > >
> >
> >
> ----------------------------------------------------------
> --------------
> >
> > Subject: RE: Driver for X11
> > Date: Mon, 8 Nov 1999 15:45:04 -0500
> > From: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
> > To: "Mike MacDonald" <mmacdona@tsi.gte.com>,
> >      <cygwin-xfree@sourceware.cygnus.com>
> >
> > >
> > > I read some more on this.  Most things (video memory for
> > > sure) can be gotten
> > > using Direct X.  I'm not sure about the IO Ports.   I
> > > have to read the DX
> > > docs on that.  I am sure there is a way..  None of this
> > > should be to hard to
> > > do.
> > >
> >
> > Yes, it is true that video memory issue can be handle
> with DirectX.
> > The XF86SUP.SYS driver is as an example for you and
> others, so you
> > could come up with your ideas on how to achive those
> functionalities
> > more
> > efficiently on Win32
> >
> > > My biggest question is, do we want to load this driver at
> > > boot up, as a
> > > windows driver, as a cygwin driver, or as part of the X
> > > initialization?
> > >
> >
> > On OS/2 the driver loads at the boot time.  He
> explained it one of
> > his messages, which is also posted on Cygwin-Xfree URL.
> >
> > > I'm thinking that it should be associated with cygwin,
> > > and load up with the
> > > cygwin.dll - or load up with X..
> >
> > No it should not be associated with Cygwin or
> Cygwin1.dll otherwise
> > you would be sacrifiying performance.  We will need to
> add needed to
> > code in
> > xc/programs/Xserver/hw/os-support/cygwin.  This code
> will call the
> > driver when needed.  I would send you Holger's code from
> > xc/programs/Xserver/hw/os-support/os2, which could server as an
> > example on how he achived it.
> >
> > >
> > > I also need to find out what he's patching in X in
> > > memory..   Is he patching
> > > the source, or the memory locations?  I have to look into
> > > the X side..
> >
> > Will send you his code from X-server which uses this driver as
> > example.
> > It will help you understand how it is used.
> >
> > Suhaib
> >
> > >
> > > Any more info you got is cool :)
> > >
> > >
> > > -----Original Message-----
> > > From: Suhaib Siddiqi [mailto:sssiddiqi@ipass.net]
> > > Sent: Wednesday, November 03, 1999 11:06 AM
> > > To: Mike MacDonald
> > > Subject: RE: Cygwin CD
> > >
> > >
> > >
> > > Have a look at the http://sourceware.cygnus.com/cygwin/xfree.
> > > There is a XF86SUP.SYS driver from OS/2 which we need to port
> > > to Windows NT.  It should be ported using MSVC or other Win32
> > > compiler, but not Cygwin for peformance reasons.  It
> has a lot of
> > > ASM code
> > > in it,.  This what actually holding XFree86 port
> (X-server) for
> > > Cygwin (Windows).  I lack the expertise and knowledge of
> > > assembly language and devices drivers.
> > >
> > > If you could get it ported to Win32 using MSVc or
> another Win32
> > > compiler
> > > you would be of great help and would make X-servers
> functional.
> > >
> > > Suhaib
> > >
> > > > -----Original Message-----
> > > > From: cygwin-owner@sourceware.cygnus.com
> > > > [mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of
> > > > Mike MacDonald
> > > > Sent: Wednesday, November 03, 1999 10:55 AM
> > > > To: 'ssiddiqi@nspm.ipass.net';
> 'cygwin@sourceware.cygnus.com'
> > > > Subject: RE: Cygwin CD
> > > >
> > > >
> > > >
> > > > Is there anything I can do to help with XFree stuff?  I'm
> > > > kinda new to X,
> > > > and Cygwin, and I don't have alot of time to spend on
> > > > stuff, but I do have
> > > > about 20 years of programming experience including ASM,
> > > > and who knows what
> > > > else..  (12 years professional - I'm working at GTE now
> > > > as a developer)..
> > > >
> > > > My constraints are that this is not a part of my job
> > > > right now, and I don't
> > > > use my computer at home anymore - so anything I look at
> > > > has to be during
> > > > breaks, or when I have time...
> > > >
> > > >
> > > > --
> > > > Want to unsubscribe from this list?
> > > > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> > > >
> > >
> >
> >
> ----------------------------------------------------------
> --------------
> >
> > Subject: RE: Driver for X11
> > Date: Mon, 8 Nov 1999 16:03:19 -0500
> > From: Mike MacDonald <mmacdona@tsi.gte.com>
> > To: "'cygwin-xfree@sourceware.cygnus.com'"
> >      <cygwin-xfree@sourceware.cygnus.com>
> >
> > Ok, thanx.  Another question, I'm hearing something
> about the graphics
> > engine changing in newer versions of X, is that going
> to affect things if we
> > just try to mimic what is done with XF86SUP.SYS using
> DirectX, or something
> > that lets us get direct memory access?
> >
> > -----Original Message-----
> > From: Suhaib Siddiqi [mailto:ssiddiqi@inspirepharm.com]
> > Sent: Monday, November 08, 1999 3:18 PM
> > To: Mike MacDonald; cygwin-xfree@sourceware.cygnus.com
> > Subject: RE: Driver for X11
> >
> > >
> > > I read some more on this.  Most things (video memory for
> > > sure) can be gotten
> > > using Direct X.  I'm not sure about the IO Ports.   I
> > > have to read the DX
> > > docs on that.  I am sure there is a way..  None of this
> > > should be to hard to
> > > do.
> > >
> >
> > Yes, it is true that video memory issue can be handle
> with DirectX.
> > The XF86SUP.SYS driver is as an example for you and
> others, so you
> > could come up with your ideas on how to achive those
> functionalities
> > more
> > efficiently on Win32
> >
> > > My biggest question is, do we want to load this driver at
> > > boot up, as a
> > > windows driver, as a cygwin driver, or as part of the X
> > > initialization?
> > >
> >
> > On OS/2 the driver loads at the boot time.  He
> explained it one of
> > his messages, which is also posted on Cygwin-Xfree URL.
> >
> > > I'm thinking that it should be associated with cygwin,
> > > and load up with the
> > > cygwin.dll - or load up with X..
> >
> > No it should not be associated with Cygwin or
> Cygwin1.dll otherwise
> > you would be sacrifiying performance.  We will need to
> add needed to
> > code in
> > xc/programs/Xserver/hw/os-support/cygwin.  This code
> will call the
> > driver when needed.  I would send you Holger's code from
> > xc/programs/Xserver/hw/os-support/os2, which could server as an
> > example on how he achived it.
> >
> > >
> > > I also need to find out what he's patching in X in
> > > memory..   Is he patching
> > > the source, or the memory locations?  I have to look into
> > > the X side..
> >
> > Will send you his code from X-server which uses this driver as
> > example.
> > It will help you understand how it is used.
> >
> > Suhaib
> >
> > >
> > > Any more info you got is cool :)
> > >
> > >
> > > -----Original Message-----
> > > From: Suhaib Siddiqi [mailto:sssiddiqi@ipass.net]
> > > Sent: Wednesday, November 03, 1999 11:06 AM
> > > To: Mike MacDonald
> > > Subject: RE: Cygwin CD
> > >
> > >
> > >
> > > Have a look at the http://sourceware.cygnus.com/cygwin/xfree.
> > > There is a XF86SUP.SYS driver from OS/2 which we need to port
> > > to Windows NT.  It should be ported using MSVC or other Win32
> > > compiler, but not Cygwin for peformance reasons.  It
> has a lot of
> > > ASM code
> > > in it,.  This what actually holding XFree86 port
> (X-server) for
> > > Cygwin (Windows).  I lack the expertise and knowledge of
> > > assembly language and devices drivers.
> > >
> > > If you could get it ported to Win32 using MSVc or
> another Win32
> > > compiler
> > > you would be of great help and would make X-servers
> functional.
> > >
> > > Suhaib
> > >
> > > > -----Original Message-----
> > > > From: cygwin-owner@sourceware.cygnus.com
> > > > [mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of
> > > > Mike MacDonald
> > > > Sent: Wednesday, November 03, 1999 10:55 AM
> > > > To: 'ssiddiqi@nspm.ipass.net';
> 'cygwin@sourceware.cygnus.com'
> > > > Subject: RE: Cygwin CD
> > > >
> > > >
> > > >
> > > > Is there anything I can do to help with XFree stuff?  I'm
> > > > kinda new to X,
> > > > and Cygwin, and I don't have alot of time to spend on
> > > > stuff, but I do have
> > > > about 20 years of programming experience including ASM,
> > > > and who knows what
> > > > else..  (12 years professional - I'm working at GTE now
> > > > as a developer)..
> > > >
> > > > My constraints are that this is not a part of my job
> > > > right now, and I don't
> > > > use my computer at home anymore - so anything I look at
> > > > has to be during
> > > > breaks, or when I have time...
> > > >
> > > >
> > > > --
> > > > Want to unsubscribe from this list?
> > > > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> > > >
> > >
> >
> >
> ----------------------------------------------------------
> --------------
> >
> > Subject: XF86Sup
> > Date: Mon, 8 Nov 1999 16:39:30 -0500
> > From: Mike MacDonald <mmacdona@tsi.gte.com>
> > To: "'cygwin-xfree@sourceware.cygnus.com'"
> >      <cygwin-xfree@sourceware.cygnus.com>
> >
> > No, that will not affect any driver.  The XF86 4.0 has
> 3 mechanisms
> > of loaing Xserver, static X-server (which is same as 3.3.x),
> > loadable,
> > and dlopen loadable.  Regardless, each X-server still
> needs System
> > dependent drivers for accessing mouse, keyboard, and
> memomry etc.
> >
> > 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 08, 1999 3:38 PM
> > > To: 'cygwin-xfree@sourceware.cygnus.com'
> > > Subject: RE: Driver for X11
> > >
> > >
> > > Ok, thanx.  Another question, I'm hearing something about
> > > the graphics
> > > engine changing in newer versions of X, is that going to
> > > affect things if we
> > > just try to mimic what is done with XF86SUP.SYS using
> > > DirectX, or something
> > > that lets us get direct memory access?
> > >
> > > -----Original Message-----
> > > From: Suhaib Siddiqi [mailto:ssiddiqi@inspirepharm.com]
> > > Sent: Monday, November 08, 1999 3:18 PM
> > > To: Mike MacDonald; cygwin-xfree@sourceware.cygnus.com
> > > Subject: RE: Driver for X11
> > >
> > >
> > >
> > >
> > > >
> > > > I read some more on this.  Most things (video memory for
> > > > sure) can be gotten
> > > > using Direct X.  I'm not sure about the IO Ports.   I
> > > > have to read the DX
> > > > docs on that.  I am sure there is a way..  None of this
> > > > should be to hard to
> > > > do.
> > > >
> > >
> > >
> > > Yes, it is true that video memory issue can be handle
> > > with DirectX.
> > > The XF86SUP.SYS driver is as an example for you and
> others, so you
> > > could come up with your ideas on how to achive those
> > > functionalities
> > > more
> > > efficiently on Win32
> > >
> > > > My biggest question is, do we want to load this driver at
> > > > boot up, as a
> > > > windows driver, as a cygwin driver, or as part of the X
> > > > initialization?
> > > >
> > >
> > > On OS/2 the driver loads at the boot time.  He
> explained it one of
> > > his messages, which is also posted on Cygwin-Xfree URL.
> > >
> > > > I'm thinking that it should be associated with cygwin,
> > > > and load up with the
> > > > cygwin.dll - or load up with X..
> > >
> > > No it should not be associated with Cygwin or Cygwin1.dll
> > > otherwise
> > > you would be sacrifiying performance.  We will need to
> > > add needed to
> > > code in
> > > xc/programs/Xserver/hw/os-support/cygwin.  This code
> will call the
> > > driver when needed.  I would send you Holger's code from
> > > xc/programs/Xserver/hw/os-support/os2, which could
> server as an
> > > example on how he achived it.
> > >
> > > >
> > > > I also need to find out what he's patching in X in
> > > > memory..   Is he patching
> > > > the source, or the memory locations?  I have to look into
> > > > the X side..
> > >
> > > Will send you his code from X-server which uses this driver as
> > > example.
> > > It will help you understand how it is used.
> > >
> > >
> > > Suhaib
> > >
> > > >
> > > > Any more info you got is cool :)
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Suhaib Siddiqi [mailto:sssiddiqi@ipass.net]
> > > > Sent: Wednesday, November 03, 1999 11:06 AM
> > > > To: Mike MacDonald
> > > > Subject: RE: Cygwin CD
> > > >
> > > >
> > > >
> > > > Have a look at the
> http://sourceware.cygnus.com/cygwin/xfree.
> > > > There is a XF86SUP.SYS driver from OS/2 which we
> need to port
> > > > to Windows NT.  It should be ported using MSVC or
> other Win32
> > > > compiler, but not Cygwin for peformance reasons.  It
> > > has a lot of
> > > > ASM code
> > > > in it,.  This what actually holding XFree86 port
> (X-server) for
> > > > Cygwin (Windows).  I lack the expertise and knowledge of
> > > > assembly language and devices drivers.
> > > >
> > > > If you could get it ported to Win32 using MSVc or
> another Win32
> > > > compiler
> > > > you would be of great help and would make X-servers
> functional.
> > > >
> > > > Suhaib
> > > >
> > > > > -----Original Message-----
> > > > > From: cygwin-owner@sourceware.cygnus.com
> > > > > [mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of
> > > > > Mike MacDonald
> > > > > Sent: Wednesday, November 03, 1999 10:55 AM
> > > > > To: 'ssiddiqi@nspm.ipass.net';
> 'cygwin@sourceware.cygnus.com'
> > > > > Subject: RE: Cygwin CD
> > > > >
> > > > >
> > > > >
> > > > > Is there anything I can do to help with XFree stuff?  I'm
> > > > > kinda new to X,
> > > > > and Cygwin, and I don't have alot of time to spend on
> > > > > stuff, but I do have
> > > > > about 20 years of programming experience including ASM,
> > > > > and who knows what
> > > > > else..  (12 years professional - I'm working at GTE now
> > > > > as a developer)..
> > > > >
> > > > > My constraints are that this is not a part of my job
> > > > > right now, and I don't
> > > > > use my computer at home anymore - so anything I look at
> > > > > has to be during
> > > > > breaks, or when I have time...
> > > > >
> > > > >
> > > > > --
> > > > > Want to unsubscribe from this list?
> > > > > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> > > > >
> > > >
> > >
> >
> >
> ----------------------------------------------------------
> --------------
> >
> > Subject: RE: XF86Sup
> > Date: Mon, 8 Nov 1999 16:43:16 -0500
> > From: "Suhaib Siddiqi" <ssiddiqi@inspirepharm.com>
> > To: "Mike MacDonald" <mmacdona@tsi.gte.com>,
> >      <cygwin-xfree@sourceware.cygnus.com>
> >
> > Ok, good.  That makes sense.  Ok, then I need to look
> at as much source as
> > possible for the XF86SUP.SYS - The questions still in
> my mind are this, do
> > we need two drivers, one a windows driver, and the
> other a DOS driver for
> > the config.sys?  Or will just a Windows driver that
> works with NT and Win 98
> > be fine?  Then, something I prolly gotta figgure out
> myself, is can I call
> > directx functions from inside of a driver..  Thats
> gonna get a little
> > complicated..  Something like the driver sits there,
> then when X tries to
> > communicate with it it makes the DX calls or something..
> >
> > A dos driver could just open up video memory, but it
> would have to be
> > disabled and replaced when windows loads up..
> >
> > Basically, I have to dig around and get my hands
> dirty..  I think I got some
> > emails from someone else who is working on this..  I
> would like to hear more
> > about what hes doing, but I think I'm up to date.
> Theres someone else who
> > is supposedly trying to do this that he mentioned..  I
> don't want to
> > duplicate efforts with him either..
> >
> > -----Original Message-----
> > From: cygwin-xfree-owner@sourceware.cygnus.com
> > [mailto:cygwin-xfree-owner@sourceware.cygnus.com]On
> Behalf Of Suhaib
> > Siddiqi
> > Sent: Monday, November 08, 1999 3:45 PM
> > To: Mike MacDonald; cygwin-xfree@sourceware.cygnus.com
> > Subject: RE: Driver for X11
> >
> > No, that will not affect any driver.  The XF86 4.0 has
> 3 mechanisms
> > of loaing Xserver, static X-server (which is same as 3.3.x),
> > loadable,
> > and dlopen loadable.  Regardless, each X-server still
> needs System
> > dependent drivers for accessing mouse, keyboard, and
> memomry etc.
> >
> > 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 08, 1999 3:38 PM
> > > To: 'cygwin-xfree@sourceware.cygnus.com'
> > > Subject: RE: Driver for X11
> > >
> > >
> > > Ok, thanx.  Another question, I'm hearing something about
> > > the graphics
> > > engine changing in newer versions of X, is that going to
> > > affect things if we
> > > just try to mimic what is done with XF86SUP.SYS using
> > > DirectX, or something
> > > that lets us get direct memory access?
> > >
> > > -----Original Message-----
> > > From: Suhaib Siddiqi [mailto:ssiddiqi@inspirepharm.com]
> > > Sent: Monday, November 08, 1999 3:18 PM
> > > To: Mike MacDonald; cygwin-xfree@sourceware.cygnus.com
> > > Subject: RE: Driver for X11
> > >
> > >
> > >
> > >
> > > >
> > > > I read some more on this.  Most things (video memory for
> > > > sure) can be gotten
> > > > using Direct X.  I'm not sure about the IO Ports.   I
> > > > have to read the DX
> > > > docs on that.  I am sure there is a way..  None of this
> > > > should be to hard to
> > > > do.
> > > >
> > >
> > >
> > > Yes, it is true that video memory issue can be handle
> > > with DirectX.
> > > The XF86SUP.SYS driver is as an example for you and
> others, so you
> > > could come up with your ideas on how to achive those
> > > functionalities
> > > more
> > > efficiently on Win32
> > >
> > > > My biggest question is, do we want to load this driver at
> > > > boot up, as a
> > > > windows driver, as a cygwin driver, or as part of the X
> > > > initialization?
> > > >
> > >
> > > On OS/2 the driver loads at the boot time.  He
> explained it one of
> > > his messages, which is also posted on Cygwin-Xfree URL.
> > >
> > > > I'm thinking that it should be associated with cygwin,
> > > > and load up with the
> > > > cygwin.dll - or load up with X..
> > >
> > > No it should not be associated with Cygwin or Cygwin1.dll
> > > otherwise
> > > you would be sacrifiying performance.  We will need to
> > > add needed to
> > > code in
> > > xc/programs/Xserver/hw/os-support/cygwin.  This code
> will call the
> > > driver when needed.  I would send you Holger's code from
> > > xc/programs/Xserver/hw/os-support/os2, which could
> server as an
> > > example on how he achived it.
> > >
> > > >
> > > > I also need to find out what he's patching in X in
> > > > memory..   Is he patching
> > > > the source, or the memory locations?  I have to look into
> > > > the X side..
> > >
> > > Will send you his code from X-server which uses this driver as
> > > example.
> > > It will help you understand how it is used.
> > >
> > >
> > > Suhaib
> > >
> > > >
> > > > Any more info you got is cool :)
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: Suhaib Siddiqi [mailto:sssiddiqi@ipass.net]
> > > > Sent: Wednesday, November 03, 1999 11:06 AM
> > > > To: Mike MacDonald
> > > > Subject: RE: Cygwin CD
> > > >
> > > >
> > > >
> > > > Have a look at the
> http://sourceware.cygnus.com/cygwin/xfree.
> > > > There is a XF86SUP.SYS driver from OS/2 which we
> need to port
> > > > to Windows NT.  It should be ported using MSVC or
> other Win32
> > > > compiler, but not Cygwin for peformance reasons.  It
> > > has a lot of
> > > > ASM code
> > > > in it,.  This what actually holding XFree86 port
> (X-server) for
> > > > Cygwin (Windows).  I lack the expertise and knowledge of
> > > > assembly language and devices drivers.
> > > >
> > > > If you could get it ported to Win32 using MSVc or
> another Win32
> > > > compiler
> > > > you would be of great help and would make X-servers
> functional.
> > > >
> > > > Suhaib
> > > >
> > > > > -----Original Message-----
> > > > > From: cygwin-owner@sourceware.cygnus.com
> > > > > [mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of
> > > > > Mike MacDonald
> > > > > Sent: Wednesday, November 03, 1999 10:55 AM
> > > > > To: 'ssiddiqi@nspm.ipass.net';
> 'cygwin@sourceware.cygnus.com'
> > > > > Subject: RE: Cygwin CD
> > > > >
> > > > >
> > > > >
> > > > > Is there anything I can do to help with XFree stuff?  I'm
> > > > > kinda new to X,
> > > > > and Cygwin, and I don't have alot of time to spend on
> > > > > stuff, but I do have
> > > > > about 20 years of programming experience including ASM,
> > > > > and who knows what
> > > > > else..  (12 years professional - I'm working at GTE now
> > > > > as a developer)..
> > > > >
> > > > > My constraints are that this is not a part of my job
> > > > > right now, and I don't
> > > > > use my computer at home anymore - so anything I look at
> > > > > has to be during
> > > > > breaks, or when I have time...
> > > > >
> > > > >
> > > > > --
> > > > > Want to unsubscribe from this list?
> > > > > Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> > > > >
> > > >
> > >
> >
> >
> ----------------------------------------------------------
> --------------
> >
> > Subject: DGA, DirectX, XF86Sup.sys style port, etc.
> > Date: Tue, 9 Nov 1999 09:51:21 +0100 (CET)
> > From: Federico Bianchi <bianchi@www.arte.unipi.it>
> > To: Mike MacDonald <mmacdona@tsi.gte.com>
> > CC: Suhaib Siddiqi <ssiddiqi@inspirepharm.com>,
> >      Jan Rouvillain <veksthus@post3.tele.dk>, Emanuele
> Aliberti <ea@iol.it>,
> >      XFree86 over CygWin Mailing List
> <cygwin-xfree@sourceware.cygnus.com>
> >
> >                   Name: null
> >    null           Type: unspecified type
> (APPLICATION/octet-stream)
> >               Encoding: BASE64
> >        Download Status: Not downloaded with message
>


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