From: "Rog�rio Brito" <rbrito@ime.usp.br>
To: linux-kernel@vger.kernel.org
Subject: Re: Are we going too fast?
Date: Mon, 13 Aug 2001 18:41:50 -0300 [thread overview]
Message-ID: <20010813184150.A1938@iname.com> (raw)
In-Reply-To: <Pine.LNX.4.20.0108131656470.1037-100000@eriador.mirkwood.net> <E15WP7z-0008H0-00@the-village.bc.nu>
In-Reply-To: <E15WP7z-0008H0-00@the-village.bc.nu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 974 bytes --]
On Aug 13 2001, Alan Cox wrote:
> VIA has some chipset bugs, Matrox G400 cards seem to abuse the PCI spec for
> benchmarketing dirties.
If I had to purchase a motherboard and graphics card for a
desktop that were running Linux, which ones should I be
buying? Are AMD's chipsets better than those made by VIA? And
what about ATI's cards?
Of course, making business with an open source-friendly is a
requirement that I've beeing making for, say, 2 or 3 years.
[]s, Roger...
P.S.: I have an Asus A7V/VIA KT133 boarch here with a Matrox G400 card
and I wish the performance were better (especially when I'm playing a
DVD). At least, when I'm using the Promise IDE interface and ignore
the IDE interface supplied by the southbridge, Linux feels faster.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
next prev parent reply other threads:[~2001-08-13 21:42 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 21:07 Are we going too fast? PinkFreud
2001-08-13 21:20 ` Alan Cox
2001-08-13 21:41 ` Rog�rio Brito [this message]
2001-08-14 0:56 ` Ben Ford
2001-08-14 7:34 ` Peter Wächtler
2001-08-14 2:24 ` David Ford
2001-08-14 4:19 ` Nicholas Knight
2001-08-14 12:49 ` Alan Cox
2001-08-14 22:27 ` Paul G. Allen
-- strict thread matches above, loose matches on Subject: below --
2001-08-16 21:42 PinkFreud
2001-08-15 20:13 Roy Murphy
[not found] <no.id>
2001-08-13 20:24 ` Alan Cox
2001-08-13 21:06 ` Anthony Barbachan
2001-08-14 20:47 ` Alan Cox
2001-08-15 0:07 ` PinkFreud
2001-08-14 20:20 Per Jessen
2001-08-14 20:07 Per Jessen
2001-08-14 19:47 Per Jessen
2001-08-14 16:32 PinkFreud
2001-08-14 16:25 PinkFreud
2001-08-13 21:44 PinkFreud
2001-08-14 0:04 ` PinkFreud
2001-08-14 7:24 ` Francois Romieu
2001-08-15 23:24 ` Dr. Kelsey Hudson
2001-08-13 21:36 PinkFreud
2001-08-14 7:57 ` Helge Hafting
[not found] <fa.l9dq0tv.7gqnhh@ifi.uio.no>
[not found] ` <fa.g70as7v.1722ipv@ifi.uio.no>
2001-08-13 19:14 ` John Weber
2001-08-13 18:53 Petr Vandrovec
2001-08-13 18:46 Per Jessen
2001-08-14 13:58 ` Andrew Scott
2001-08-14 19:54 ` David Ford
2001-08-13 17:53 PinkFreud
2001-08-13 20:27 ` Gérard Roudier
2001-08-13 7:43 PinkFreud
2001-08-13 8:52 ` Brian
2001-08-13 8:55 ` Francois Romieu
2001-08-13 10:09 ` Chris Wilson
2001-08-13 11:09 ` szonyi calin
2001-08-14 4:21 ` Pete Toscano
2001-08-14 12:48 ` Alan Cox
2001-08-14 22:30 ` Paul G. Allen
2001-08-13 10:03 ` Gérard Roudier
2001-08-13 10:29 ` Justin Guyett
2001-08-13 12:56 ` Andrzej Krzysztofowicz
2001-08-13 16:54 ` Gérard Roudier
2001-08-13 13:11 ` Alan Cox
2001-08-14 18:51 ` Anders Larsen
2001-08-14 20:29 ` Anders Larsen
2001-08-13 13:46 ` hugang
2001-08-13 13:55 ` Anton Altaparmakov
2001-08-13 17:16 ` Stephen Satchell
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=20010813184150.A1938@iname.com \
--to=rbrito@ime.usp.br \
--cc=linux-kernel@vger.kernel.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