Re: [PATCH] Prevent trident driver from grabbing pcnet32 hardware

Adrian Bunk
2006-01-13T12:24:00Z

On Fri, Jan 13, 2006 at 01:37:56PM +0200, Muli Ben-Yehuda wrote:
> 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?
>...

In my experience with scheduling OSS drivers for removal, users simply
use the OSS drivers unless you tell them very explicitely that the OSS
driver will go.

It shouldn't be too hard to port the support to ALSA if someone with the
hardware is willing to test patches.

The goal is to get people still using OSS drivers where ALSA drivers
support the same hardware to use the ALSA drivers - and if there were
bugs in the ALSA drivers preventing them to switch to ALSA, to report
them to the ALSA bug tracking system.

This has the following advantages:
- better ALSA drivers
- get rid of some unmaintained code in the kernel

> Cheers,
> Muli

cu
Adrian

--

"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed