From: offer@sgi.com (richard offer)
To: Miguel de Icaza <miguel@nuclecu.unam.mx>
Cc: linux@morgaine.engr.sgi.com
Subject: Re: Good news: no more begging for HW
Date: Tue, 17 Jun 1997 10:53:12 -0700 [thread overview]
Message-ID: <9706171053.ZM9344@sgi.com> (raw)
In-Reply-To: Miguel de Icaza <miguel@nuclecu.unam.mx> "Re: Good news: no more begging for HW" (Jun 17, 12:10pm)
* $ from miguel@nuclecu.unam.mx at "17-Jun:12:10pm" | sed "1,$s/^/* /"
*
*
*
* > If someone takes the server, I'll try and get the clients libraries done
* > (assuming that I can get remote access to a box).
*
* I was interested in working on the X server for the SGI. I already
* did that for the Linux/SPARC, and I had a couple of questions to make,
* so this seems like a good time to ask them (please note that I haven't
* actually traced my SGI X server to see what it does).
The questions are good, but I'm not the person who can answer them, me I'm a
Motif hacker, anything at a level lower than Xt is akin to assembler for me.
So with that in mind take the rest with a pinch of salt.
*
* 1. On the SPARC, the X server mmap()s the frame buffer into its
* address space and uses a couple of ioctls to talk with the kernel
* (to ask the kernel to change the palette and the hardware cursor,
* on later versions, with got rid of that, and we just poked at the
* frame buffer control registers from the X server).
*
* How does this work on the SGI? Is the video card just a thing that
* can be mapped into the X server address space?
*
* If this is the case, getting the X11R6 server to work will just take
* a couple of days of coding.
*
*
* 2. What kind of acceleration features are available on the SGI
* machines? The X11R6 server has hooks for different set of
* features, so for example, bitblit can be easily hacked into the X
* server.
*
* But I imagine the SGI has more acceleration features that I can
* dream of.
The problem is that (I think) we have so many graphics cards that its done
differently in every one (some cards are simple frame buffers (8/24bit), then
there are some with multiple GE, oh and we also have extra visuals for overlay
and pop-ups.
The O2 has no graphics memory, everything is done in main memory.
*
*
* 3. How does OpenGL work on the SGIs? Is the OpenGL engine embedded in
* the X server, or it is something that is present on the video card?
*
* I looked yesterday at a program called glxinfo, which led me to
* believe that applications may have some of the GL code linked in
* trough the libraries and the other part resides on the X server.
Both :-) We don't do things the way easy here.
The is a GLX extension in the X server which allows GL to run in an X window.
There is also I think a DSO that holds the hardware specific GL calls.
*
* So, in this case, what are the specs for what needs to be on the X
* server to be able to run OpenGL applications.
*
*
* 4. Would it be possible for a free software company to redistribute
* the SGI's X server? In that case, we could concentrate on getting
* the IRIX emulation as good as possible and just use the SGI X
* server and let Red Hat/Debian/GNU ship the cd with that binary.
This would be my preferred solution, but I've had many an argument on this
subject that I felt very dubious about bringing it up again.
To me the quickest (and the best) way of getting an X server would be if we
could simply port the existing Irix X server to Linux/SGI. My suggestion would
be, now that we have backing for hardware to get official backing for software.
I don't think we should neccesarrily release the source code for the ddx part
of the X server to the public, but we should at least be able to get backing to
release .o files so the user could re-link the X server if they needed to (Sun
have done this before).
*
*
* Cheers,
* Miguel.
*
*
richard
-----------------------------------------------------------------------
Richard M. Offer Widget FAQ --> http://reality.sgi.com/widgetFAQ
MTS-Core Design (Motif)
___________________________________________http://reality.sgi.com/offer
next prev parent reply other threads:[~1997-06-17 17:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199706170046.CAA17216@informatik.uni-koblenz.de>
1997-06-17 1:06 ` Good news: no more begging for HW Ariel Faigon
1997-06-17 1:06 ` Ariel Faigon
1997-06-17 1:53 ` Alex deVries
1997-06-17 2:01 ` David S. Miller
[not found] ` <davem@jenolan.rutgers.edu>
1997-06-17 16:23 ` richard offer
1997-06-17 17:10 ` Miguel de Icaza
1997-06-17 17:49 ` Mike Shaver
1997-06-17 17:49 ` Mike Shaver
1997-06-17 17:53 ` richard offer [this message]
1997-06-17 18:00 ` Miguel de Icaza
1997-06-17 18:30 ` Martin Knoblauch
1997-06-17 18:45 ` David S. Miller
1997-06-18 0:00 ` John Wiederhirn
1997-06-18 0:15 ` richard offer
1997-06-18 0:32 ` Ralf Baechle
1997-06-18 0:32 ` Ralf Baechle
1997-06-19 19:23 ` William J. Earl
1997-06-18 0:34 ` Getting X on Linux/SGI Ariel Faigon
1997-06-18 0:34 ` Ariel Faigon
1997-06-18 16:28 ` Christopher W. Carlson
1997-06-18 19:30 ` Nigel Gamble
1997-06-18 2:47 ` Good news: no more begging for HW Miguel de Icaza
1997-06-18 12:38 ` William J. Earl
1997-06-18 12:38 ` William J. Earl
1997-06-18 6:37 Larry McVoy
1997-06-18 6:37 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
1997-06-17 6:22 Larry McVoy
1997-06-17 9:46 ` Ralf Baechle
1997-06-17 9:46 ` Ralf Baechle
1997-06-17 16:08 ` Miguel de Icaza
1997-06-17 2:25 Larry McVoy
1997-06-17 2:25 ` Larry McVoy
1997-06-17 5:31 ` Alex deVries
1997-06-16 23:25 Ariel Faigon
1997-06-17 3:59 ` Christopher W. Carlson
1997-06-17 8:15 ` Martin Knoblauch
1997-06-17 16:18 ` Miguel de Icaza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9706171053.ZM9344@sgi.com \
--to=offer@sgi.com \
--cc=linux@morgaine.engr.sgi.com \
--cc=miguel@nuclecu.unam.mx \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox