[alsa-devel] [PATCH] sound/isa: kill pnp_resource_change.

[Takashi Iwai]

At Fri, 30 Nov 2007 01:49:00 +0100,
Rene Herman wrote:
> 
> On 29-11-07 20:30, Bjorn Helgaas wrote:
> 
> > OK, good.
> > 
> > Anyone who relies on the manual settings will have to change the
> > way it's done, so maybe the changelog and documentation update
> > should include some text along the lines of:
> > 
> >   - this removes module parameters for ISAPNP ALSA resources
> >   - the drivers *should* work with no manual resource settings
> >   - if you need manual resource settings (usually to work around
> >     a broken BIOS),
> 
> Actually, the ALSA drivers with PnPBIOS support (snd-cs4232, snd-es18xx and 
> snd-opl3sa2) do not in fact loose any parameters and the few known trouble 
> spots there are using
> 
> 	modprobe snd-foo isapnp=0 port=...
> 
> as their workaround, bypassing all of PnP, and this still works completely 
> the same as before.
> 
> I do not expect any trouble. A few users might have _mistakingly_ added 
> parameters to an ISAPnP only (as in, not also PnPBIOS) driver due to 
> googling up your generic bad-advice webforum that said that worked for 
> someone with a heavy sounding nickname, but we can deal with that.
> 
> Moreover, as I've been experiencing on the ALSA list for a while now (where 
> I've been somewhat responsive to ISA related issues) basically anything but 
> PnPBIOS/ACPI ISA is mostly dead and as said, with an isapnp=0 in the drivers 
> there which known issues are using, there's no difference.
> 
> Advice is always good, but I'd not put in the ALSA documentation (wrong 
> place) and even in the changelog it sounds a bit overly alarming in my own 
> opinion. The expected fall-out is... <crickets>...

Hm, but still some notes are needed for ALSA-Configuration.txt
mentioning that the resource parameters like port, io, etc can be used
only when isapnp=no on some drivers.  The parameters are still there,
so people may wonder if it has no use.


Takashi