Date: Mon, 28 Jan 2008 08:50:24 +1100 (EST)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Avuton Olrich <avuton@gmail.com>
cc: Zhao Yakui <yakui.zhao@intel.com>, Li Shaohua <shaohua.li@intel.com>,
       Bjorn Helgaas <bjorn.helgaas@hp.com>, Thomas Renninger <trenn@suse.de>,
       Andrew Morton <akpm@linux-foundation.org>,
       "Linux-Kernel," <linux-kernel@vger.kernel.org>,
       Alsa-Devel <alsa-devel@alsa-project.org>
Subject: Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0
 sound card
In-Reply-To: <3aa654a40801270640s59cfdcc4lfa3fb487e0d9b799@mail.gmail.com>
Message-ID: <alpine.LFD.1.00.0801280841440.4544@www.l.google.com>
References: <3aa654a40801270640s59cfdcc4lfa3fb487e0d9b799@mail.gmail.com>
User-Agent: Alpine 1.00 (LFD 882 2007-12-20)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1097
Lines: 27


On Sun, 27 Jan 2008, Avuton Olrich wrote:
>
> With v2.6.24 my second ALSA sound device stopped working.

Hmm. Why is PnP ACPI called before PCI probing? That seems to be the 
problem here - we should *never* have any firmware allocation block known 
hardware BARs, they should only be blocking new dynamic allocations.

Hmm. I wonder if the problem is that ACPIPnP marks the regions busy. That 
would be wrong. They shouldn't be busy, they should just "exist".

A busy region will stop a "request_region()" (incorrect for this case - 
thats' not what the PnP resurce allocation should be all about), but an 
*existing* resource will just stop a new resource being dynamically 
assigned to that address (not not stop a known resource from using it).

So maybe the ACPIPnP allocation is doen at the right moment, just doing 
the wrong thing..

		Linus
--
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/