From: Timothy Miller <miller@techsource.com>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux and IBM : "unauthorized" mini-PCI : TCPA updates
Date: Tue, 03 Jun 2003 13:42:03 -0400 [thread overview]
Message-ID: <3EDCDDEB.3070701@techsource.com> (raw)
In-Reply-To: 200306040104.34954.mflt1@micrologica.com.hk
Michael Frank wrote:
> Solution: This community needs a white list of functioning hardware.
>
>
I could really use a white list for graphics cards. It's hard enough
finding something that works well in Windows. For Linux, it's
practically a lost cause unless you want to buy something more than 2
years old.
next prev parent reply other threads:[~2003-06-03 17:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 16:49 Linux and IBM : "unauthorized" mini-PCI : TCPA updates Lincoln Durey
2003-06-03 16:34 ` Alan Cox
2003-06-03 18:29 ` Josh Litherland
2003-06-03 17:04 ` Michael Frank
2003-06-03 17:42 ` Timothy Miller [this message]
2003-06-04 12:39 ` Derek Fawcus
2003-06-06 22:59 ` Martin List-Petersen
2003-06-09 12:57 ` Dana Lacoste
2003-06-09 16:56 ` Martin List-Petersen
2003-06-10 23:35 ` Theodore Ts'o
2003-07-07 18:12 ` Linux and IBM : "unauthorized" mini-PCI : Cisco mpi350 _way_ sub-optimal Lincoln D. Durey
2003-07-08 14:02 ` Alan Cox
2003-07-08 15:20 ` Gerald Britton
2003-07-08 15:42 ` Alan Cox
2003-07-08 17:24 ` Gerald Britton
2003-07-08 17:44 ` Russell King
2003-07-08 20:58 ` Jamie Lokier
2003-07-09 22:35 ` Gerald Britton
-- strict thread matches above, loose matches on Subject: below --
2003-06-03 19:35 Linux and IBM : "unauthorized" mini-PCI : TCPA updates Mark Grosberg
2003-06-03 19:40 ` Mike Dresser
2003-06-03 20:02 ` Josh Litherland
2003-06-03 20:40 ` Mike Dresser
2003-06-03 21:09 ` Josh Litherland
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=3EDCDDEB.3070701@techsource.com \
--to=miller@techsource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mflt1@micrologica.com.hk \
/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