All of lore.kernel.org
 help / color / mirror / Atom feed
From: lm@neteng.engr.sgi.com (Larry McVoy)
To: jwiede@blammo.engr.sgi.com (John Wiederhirn)
Cc: linux@morgaine.engr.sgi.com
Subject: Re: Good news: no more begging for HW
Date: Tue, 17 Jun 1997 23:37:15 -0700	[thread overview]
Message-ID: <199706180637.XAA09017@neteng.engr.sgi.com> (raw)

: 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?

Thanks.

WARNING: multiple messages have this Message-ID (diff)
From: lm@neteng.engr.sgi.com (Larry McVoy)
To: John Wiederhirn <jwiede@blammo.engr.sgi.com>
Cc: linux@morgaine.engr.sgi.com
Subject: Re: Good news: no more begging for HW
Date: Tue, 17 Jun 1997 23:37:15 -0700	[thread overview]
Message-ID: <199706180637.XAA09017@neteng.engr.sgi.com> (raw)
Message-ID: <19970618063715.5I4Itzzjmt4jzZ0cGUofKHA8Cfdsnzf1F_jrI2kbmrc@z> (raw)

: 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?

Thanks.

             reply	other threads:[~1997-06-18  6:38 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-06-18  6:37 Larry McVoy [this message]
1997-06-18  6:37 ` Good news: no more begging for HW Larry McVoy
1997-06-18  8:21 ` Getting X on Linux/SGI (2) Martin Knoblauch
1997-06-18 16:23   ` richard offer
1997-06-19 19:42   ` William J. Earl
  -- strict thread matches above, loose matches on Subject: below --
1997-06-17  6:22 Good news: no more begging for HW 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
     [not found] <199706170046.CAA17216@informatik.uni-koblenz.de>
1997-06-17  1:06 ` 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
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  2:47               ` Miguel de Icaza
1997-06-18 12:38               ` William J. Earl
1997-06-18 12:38                 ` William J. Earl
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=199706180637.XAA09017@neteng.engr.sgi.com \
    --to=lm@neteng.engr.sgi.com \
    --cc=jwiede@blammo.engr.sgi.com \
    --cc=linux@morgaine.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.