Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Martin Knoblauch <knobi@munich.sgi.com>
To: Larry McVoy <lm@neteng.engr.sgi.com>
Cc: John Wiederhirn <jwiede@blammo.engr.sgi.com>,
	linux@morgaine.engr.sgi.com
Subject: Getting X on Linux/SGI (2)
Date: Wed, 18 Jun 1997 10:21:29 +0200	[thread overview]
Message-ID: <33A79A89.1CFB@munich.sgi.com> (raw)
In-Reply-To: 199706180637.XAA09017@neteng.engr.sgi.com

[also changeing the subject]

Larry McVoy wrote:
> 
> : There are some very serious issues which come up even getting
> : Xfree to a moderate level of acceleration.
> 
> How about to a simple level of working?  Without any acceleration?
> For most people, just having xterms and netscape working is enough.
> 
> I'm not a graphics or X person.  Could someone who knows SGI's gfx
> devices tell us how hard it would be to make the basics work?
> 

  Probably not that hard if we gave away the documentation
(do we have *documentation*) on the GFX cards low level interfaces.
The major problem to me seems that each different architecture
(XL, XZ/Elan/Extreme, IMPACT, CRM) has different interfaces.
I am not sure that you can find a minimal subset of calls
to make a very simple Xserver work (is Peter Daifuku on this
list ? Mark Kilgard?).

  Personally I think that we don't loose anything if we give away
the stuff for the older boards (Newport, Express). I am not
sure, what we loose if we do the same for IMPACT/IR (OK, IR
is probably not such a big deal :-)


 Questions:

- How much HW dependent stuff is in Xsgi itself?
- Which of the DSOs in /usr/lib/X11/dyDDX are minimally
  needed to bring up an non-GLX Xserver?
- How much efforts would it cost to compile the dyDDX
  stuff for Linux and distribute the binaries only
  (assuming that there is not to much HW stuff in Xsgi itself)?


 And of course, we probably have to provide the microcode and
loader for the different GFX cards.

 I definitely agree with Ariel, that this is the most important
topic once we have Linux running stable.

Martin
-- 
+---------------------------------+-----------------------------------+
|Martin Knoblauch                 | Silicon Graphics GmbH             |
|Manager Technical Marketing      | Am Hochacker 3 - Technopark       |
|Silicon Graphics Computer Systems| D-85630 Grasbrunn-Neukeferloh, FRG|
|---------------------------------| Phone: (+int) 89 46108-179 or -0  |
|http://reality.sgi.com/knobi     | Fax:   (+int) 89 46107-179        |
+---------------------------------+-----------------------------------+
|e-mail: <knobi@munich.sgi.com>   | VM: 6-333-8197 | M/S: IDE-3150    |
+---------------------------------------------------------------------+

  parent reply	other threads:[~1997-06-18  8:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-18  6:37 Good news: no more begging for HW Larry McVoy
1997-06-18  6:37 ` Larry McVoy
1997-06-18  8:21 ` Martin Knoblauch [this message]
1997-06-18 16:23   ` Getting X on Linux/SGI (2) richard offer
1997-06-19 19:42   ` William J. Earl

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=33A79A89.1CFB@munich.sgi.com \
    --to=knobi@munich.sgi.com \
    --cc=jwiede@blammo.engr.sgi.com \
    --cc=linux@morgaine.engr.sgi.com \
    --cc=lm@neteng.engr.sgi.com \
    /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