Messages in this thread | | | Date | Fri, 13 Jan 2006 13:37:56 +0200 | From | Muli Ben-Yehuda <> | Subject | Re: [PATCH] Prevent trident driver from grabbing pcnet32 hardware |
| |
On Thu, Jan 12, 2006 at 05:42:10PM -0500, Lee Revell wrote: > 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?
... or use the known working OSS driver?
> 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.
So you advocate removing a known working driver in favor of a known not to be working driver? nice.
Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |