All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Andrew Morton <akpm@osdl.org>,
	ALSA devel <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.de>, "yakui.zhao" <yakui.zhao@intel.com>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	Thomas Renninger <trenn@suse.de>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] sound/isa: kill pnp_resource_change.
Date: Fri, 30 Nov 2007 01:49:00 +0100	[thread overview]
Message-ID: <474F5DFC.6040507@keyaccess.nl> (raw)
In-Reply-To: <200711291230.24323.bjorn.helgaas@hp.com>

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>...

Rene.

  reply	other threads:[~2007-11-30  0:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29  1:10 [PATCH] sound/isa: kill pnp_resource_change Rene Herman
2007-11-29 14:07 ` Takashi Iwai
2007-11-30  9:52   ` Jaroslav Kysela
2007-11-30 11:05     ` Takashi Iwai
2007-11-30 12:25       ` Jaroslav Kysela
2007-11-30 12:38         ` Takashi Iwai
2007-11-30 13:32           ` Jaroslav Kysela
2007-11-30 16:11             ` Takashi Iwai
2007-11-30 17:19             ` Rene Herman
2007-11-30 17:39               ` Thomas Renninger
2007-11-30 19:53                 ` Rene Herman
2007-11-29 16:20 ` Bjorn Helgaas
2007-11-29 17:34   ` Rene Herman
2007-11-29 17:35   ` Rene Herman
2007-11-29 19:30     ` Bjorn Helgaas
2007-11-30  0:49       ` Rene Herman [this message]
2007-11-30  9:07         ` Takashi Iwai
2007-11-30 17:07           ` Rene Herman
2007-11-30 16:27             ` Takashi Iwai
2007-11-30 17:33               ` Rene Herman

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=474F5DFC.6040507@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=shaohua.li@intel.com \
    --cc=tiwai@suse.de \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.