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

On 30-11-07 17:27, Takashi Iwai wrote:

> At Fri, 30 Nov 2007 18:07:27 +0100,
> Rene Herman wrote:

>> By the way, eventually I'd in fact probably like to move some of the drivers 
>> that now still support legacy ISA over to PnP only. After all, chips such as 
>> the CMI8330, CS4232+, ES1869+ and OPL3SA2 _are_ PnP only chips.
>>
>> Certainly for CS4232+ and ES1869+ that can't be done currently as we know 
>> people are in fact using isapnp=0 to work around PnPBIOS issues but from the 
>> previous report there it seemed that might actually just consist of the BIOS 
>> claiming no resource change is possible, which pnp_activate_dev (through 
>> pnp_autoconfig_dev) insist on anyway. This would be something to fix inside 
>> PnP instead...
> 
> Well, I'm not sure about that.  Certainly there are some users that
> use isapnp=no with explicit parameters.

Yes, currently, but as said, we might be able to al least make sure they 
don't _need_ to do that at the PnP layer after which it becomes somewhat 
debatable at least. But yes, sure, not now, once, maybe, perhaps, ...

>> Anyways, here's just a further Documentation update. You once told me to 
>> start new threads for patches, but that seems clumsy now... :-|
> 
> Thanks.  It seems that people do care more on explanations about the
> removal of options.  Could you add that, too?
> Just mention about sysfs as alternative way to change the
> parameters...

Yes. Documentation/pnp.txt wants to be a little more verbose after which 
ALSA documentation can refer to it. I'll cook something up...

Rene.

      reply	other threads:[~2007-11-30 17:34 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
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 [this message]

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=47504981.2080804@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.