mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brad Douglas <brad@neruo.com>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: James Simmons <jsimmons@suse.com>,
	Bob Lorenzini <hwm@ns.newportharbornet.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.2.18 vs Inspiron
Date: 18 Dec 2000 15:24:00 -0800	[thread overview]
Message-ID: <20001218235512Z129391-439+4806@vger.kernel.org> (raw)
In-Reply-To: <20001217050700.U3199@cadcamlab.org>
In-Reply-To: <Pine.LNX.4.21.0012121557330.2752-100000@newportharbornet.com>   <Pine.LNX.4.21.0012121631510.270-100000@euclid.oak.suse.com>   <20001217050700.U3199@cadcamlab.org>

On 17 Dec 2000 05:07:01 -0600, Peter Samuelson wrote:
> 
> [James Simmons]
> > Ah the infamous Rage Mobility chipset. Three versions of the same
> > chipset but each is very different.
> 
> I knew it was bad when ATI refuses to publish Windows drivers -- they
> basically say "get drivers from your laptop vendor, there is *no*
> generic driver that works for everyone".


That's not entirely correct.  True enough, they have a very confusing
naming scheme, but that shouldn't set us back too far.

Rage Mobility/M1 = Mach64
M3 = Rage128
M4 = Radeon

For ATI's Mach64 based cards, they chose to let the vendor pick the DAC
that best suited their needs.  While this is good from an economical
perspective, it caused massive support headaches.  Needless to say, ATI
no longer uses this model.  It's not that they refused to publish
drivers, they just screwed themselves out of being able to.

Brad Douglas
brad@neruo.com


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      parent reply	other threads:[~2000-12-18 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-13  0:03 Bob Lorenzini
2000-12-13  0:32 ` James Simmons
2000-12-17 11:07   ` Peter Samuelson
2000-12-18 23:24   ` Brad Douglas [this message]

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=20001218235512Z129391-439+4806@vger.kernel.org \
    --to=brad@neruo.com \
    --cc=hwm@ns.newportharbornet.com \
    --cc=jsimmons@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@cadcamlab.org \
    /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

all inboxes | Powered by JetHome®