From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
Andrew Morton <akpm@linux-foundation.org>,
avuton@gmail.com, yakui.zhao@intel.com, shaohua.li@intel.com,
trenn@suse.de, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0 sound card
Date: Mon, 4 Feb 2008 10:18:09 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.1.00.0802041014410.3034@hp.linux-foundation.org> (raw)
In-Reply-To: <200802041039.36100.bjorn.helgaas@hp.com>
On Mon, 4 Feb 2008, Bjorn Helgaas wrote:
>
> I think the problem here is that the PCI BAR is bigger and spans the
> region reported by ACPI:
Ok, then it doesn't help that it's not busy.
In that case, the only real fix is to simply do the ACPI reservations
*after* PCI probing. Which is what it should have done to begin with.
> We can easily add more BIOSes to the PNP quirk.
No. Don't add quirks just because the basic ordering is shit.
> I really don't want to use the earlier quirk that scanned PCI devices
> from a PNP quirk. I think that's just wrong because PNP (which
> conceptually includes ACPI) is what tells us about PCI root bridges.
So? Do the bridge listing separately from resource marking. Why tie the
two together? They have absolutely *nothing* to do with each other.
The fact is, scanning devices should happen first. And AFTER the device
tree is scanned, we can then safely add all the special resources that
don't show up as normal devices.
Linus
next prev parent reply other threads:[~2008-02-04 18:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.Kmpf0B4W44W1VefIME7+BnfUouY@ifi.uio.no>
2008-01-27 18:17 ` a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0 sound card Robert Hancock
2008-01-31 22:58 ` Andrew Morton
2008-02-01 0:14 ` Robert Hancock
2008-02-01 0:50 ` Linus Torvalds
2008-02-04 17:39 ` Bjorn Helgaas
2008-02-04 18:18 ` Linus Torvalds [this message]
2008-02-04 20:41 ` Bjorn Helgaas
2008-02-04 21:16 ` Linus Torvalds
2008-02-05 7:03 ` Bjorn Helgaas
2008-02-05 16:46 ` Avuton Olrich
2008-02-05 18:15 ` Linus Torvalds
2008-02-05 20:12 ` Bjorn Helgaas
2008-02-13 22:33 ` Avuton Olrich
2008-02-14 18:51 ` Bjorn Helgaas
2008-02-14 19:42 ` Linus Torvalds
2008-02-14 20:07 ` Bjorn Helgaas
2008-02-14 20:26 ` Linus Torvalds
2008-02-14 21:01 ` Bjorn Helgaas
2008-02-14 21:37 ` Linus Torvalds
2008-02-14 22:28 ` Bjorn Helgaas
2008-02-14 22:57 ` Linus Torvalds
2008-02-14 23:14 ` Linus Torvalds
2008-02-15 0:13 ` Bjorn Helgaas
2008-02-15 0:40 ` Linus Torvalds
2008-02-27 17:43 ` Bjorn Helgaas
2008-01-27 14:40 Avuton Olrich
2008-01-27 21:50 ` Linus Torvalds
2008-01-28 1:15 ` Shaohua Li
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=alpine.LFD.1.00.0802041014410.3034@hp.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=avuton@gmail.com \
--cc=bjorn.helgaas@hp.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox