9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: MoJoJoJo <MoJoJoJo@ppuff.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Are nvidia-cards working with plan9?
Date: Mon, 25 Sep 2000 09:22:40 +0000	[thread overview]
Message-ID: <a7vosssng0ubeiq18o9ktjrtnaeq2e0d63@4ax.com> (raw)
In-Reply-To: <E13c2BL-0007xX-0B@finch-post-11.mail.demon.net>

Looks like nVidia cards are supported by XFree with hardware
acceleration in versions 3.3.6 and 4.0.1 -- see:
http://www.xfree86.org/4.0.1/Status21.html#21

The latest plan9 hardware support document is at:
http://plan9.bell-labs.com/plan9dist/pchardware.html

Is the ultimate goal of this OS to be just a developer test platform?
I can't help but wonder where a lot of other OSes would have been
right now if they had not turned their noses up at 'gaming hardware'.
It's a good thing that 

--TNT2 Ultra Owner

On Thu, 21 Sep 2000 09:14:14 GMT, nigel@9fs.org wrote:

>In general, the more 3D oriented, and state-of-the-art,
>the less likely the card is to be supported. This is partially
>a function of the proprietary nature of 'gamers' cards,
>and partially the unlikelihood that researchers in Plan 9
>have found the need to support such cards.
>
>If you read the hardware compatibility specs, you will
>see what is supported in the current release. The usual
>line is 'ATi mach64 based cards are OK'. Of course, if
>you see it mentioned in /lib/vgadb then this is encouraging.
>
>Support is improving, though. If you check the archives,
>you will see that a Voodoo 3 and S3 Savage drivers have been
>done, but not yet released. Matrox G200/G400 may not be far away.
>
>On the flip side, no Ati 128 bit cards are supported.
>
>Another important rule of thumb is 'does XFree86 support
>it'. This is an indication as to whether the technical
>documentation needed to write a driver is available.
>At one time certainly, Nvidia were difficult.



  reply	other threads:[~2000-09-25  9:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-21  8:58 nigel
2000-09-25  9:22 ` MoJoJoJo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-05 15:10 David Gordon Hogan
2000-10-09  9:05 ` jiho
2000-10-09  9:49   ` Lucio De Re
2000-10-11  8:47 ` jiho
2000-10-05  0:29 okamoto
2000-10-04 13:07 Russ Cox
2000-10-04 13:21 ` Nigel Roles
2000-10-05  8:22 ` jiho
2000-10-05  9:00   ` Lucio De Re
2000-10-09  9:04     ` Douglas A. Gwyn
2000-10-09 10:02       ` Lucio De Re
2000-10-09 12:57         ` Rick Hohensee
2000-10-09 17:46         ` Matt
2000-09-25 10:57 forsyth
2000-09-25 13:38 ` Conor
2000-09-28 10:18   ` Douglas A. Gwyn
2000-10-02  9:01   ` root
2000-10-02 16:59     ` Scott Schwartz
2000-10-03  0:34       ` Rick Hohensee
2000-10-02  9:01   ` root
2000-10-03  8:49   ` Douglas A. Gwyn
2000-10-04  8:45   ` jiho
2000-10-04 11:55     ` sah
2000-10-04 12:06       ` sah
2000-10-04  9:08   ` jiho
2000-10-02  9:03 ` root
2000-09-21  8:27 Henri Philipps

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=a7vosssng0ubeiq18o9ktjrtnaeq2e0d63@4ax.com \
    --to=mojojojo@ppuff.com \
    --cc=9fans@cse.psu.edu \
    /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;
as well as URLs for NNTP newsgroup(s).