From: Lee Revell <rlrevell@joe-job.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Jon Mason <jdmason@us.ibm.com>, Muli Ben-Yehuda <mulix@mulix.org>,
Jiri Slaby <slaby@liberouter.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Prevent trident driver from grabbing pcnet32 hardware
Date: Thu, 12 Jan 2006 17:42:10 -0500 [thread overview]
Message-ID: <1137105731.2370.94.camel@mindpipe> (raw)
In-Reply-To: <20060112220039.GX29663@stusta.de>
On Thu, 2006-01-12 at 23:00 +0100, Adrian Bunk wrote:
> CYBER5050 is discussed in ALSA bug #1293 (tester wanted).
OK I set that bug to FEEDBACK, but it's open 5 months now and no testers
are forthcoming. I think if we don't find one as a result of this
thread we can assume no one cares about this hardware anymore.
I'm still not sure that just adding it to the ALSA driver and hoping it
works is the best solution. Would we rather users see right away that
their hardware isn't supported, or have the driver load and get no sound
or hang the machine?
I think the best approach might just be to drop it in lieu of a tester.
It will be trivial to add support later if someone finds one of these
boxes.
Lee
next prev parent reply other threads:[~2006-01-12 22:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 17:50 [PATCH] Prevent trident driver from grabbing pcnet32 hardware Jon Mason
2006-01-12 19:28 ` Jiri Slaby
2006-01-12 19:34 ` Jiri Slaby
2006-01-12 20:07 ` Muli Ben-Yehuda
2006-01-12 21:15 ` Lee Revell
2006-01-12 21:58 ` Adrian Bunk
2006-01-12 22:06 ` Lee Revell
2006-01-12 22:11 ` Jon Mason
2006-01-12 22:46 ` Adrian Bunk
2006-01-12 21:47 ` Jon Mason
2006-01-12 22:00 ` Adrian Bunk
2006-01-12 22:09 ` Jan Engelhardt
2006-01-12 22:20 ` Jon Mason
2006-01-12 22:42 ` Lee Revell [this message]
2006-01-12 22:52 ` Adrian Bunk
2006-01-12 22:55 ` Lee Revell
2006-01-13 10:16 ` Alan Cox
2006-01-12 23:32 ` Old hardware (was Re: [PATCH] Prevent trident driver from grabbing pcnet32 hardware) Lee Revell
2006-01-12 23:52 ` Bob Copeland
2006-01-13 10:28 ` [PATCH] Prevent trident driver from grabbing pcnet32 hardware Alan Cox
2006-01-13 17:55 ` Lee Revell
2006-01-13 11:37 ` Muli Ben-Yehuda
2006-01-13 12:23 ` Adrian Bunk
2006-01-13 12:32 ` Muli Ben-Yehuda
2006-01-13 15:24 ` Adrian Bunk
2006-01-13 15:36 ` Muli Ben-Yehuda
2006-01-12 22:08 ` Jon Mason
2006-01-12 20:49 ` pcnet32 devices with incorrect trident vendor ID Daniel Drake
2006-01-12 20:57 ` Matthew Wilcox
2006-01-12 21:03 ` Daniel Drake
2006-01-12 21:05 ` Matthew Wilcox
2006-01-12 21:22 ` Bill Nottingham
2006-01-12 21:24 ` Bill Nottingham
2006-01-12 22:23 ` Don Fry
2006-01-12 22:33 ` Jon Mason
2006-01-12 21:05 ` Lennart Sorensen
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=1137105731.2370.94.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=bunk@stusta.de \
--cc=jdmason@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.org \
--cc=slaby@liberouter.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