From: Robert Hancock <hancockr@shaw.ca>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: avuton@gmail.com, yakui.zhao@intel.com, shaohua.li@intel.com,
bjorn.helgaas@hp.com, trenn@suse.de,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org
Subject: Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0 sound card
Date: Thu, 31 Jan 2008 18:14:03 -0600 [thread overview]
Message-ID: <47A2644B.4000905@shaw.ca> (raw)
In-Reply-To: <20080131145820.44171af2.akpm@linux-foundation.org>
Andrew Morton wrote:
>> There was a patch floating around to ignore PnPACPI reservations which
>> conflict with PCI BARs, which appears to be what's happening in this
>> case. That patch originally worked for any board, but was later made
>> specific to a certain Supermicro motherboard which had the sata_nv
>> controller MMIO regions marked as reserved, preventing the driver from
>> loading. We may need a more general solution. See:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=313491
>
> Thanks. If we were to remove the supermicro-specificity, would this be a
> sufficiently general solution?
I think so. There was one objection that it introduced a dependency on
pnpacpi loading after PCI bus enumeration, though.
Linus also suggested that pnpacpi could be marking the resources as
"present but unused" so that drivers can request those regions but we
still prevent dynamically assigning resources into them.
next prev parent reply other threads:[~2008-02-01 0:14 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 [this message]
2008-02-01 0:50 ` Linus Torvalds
2008-02-04 17:39 ` Bjorn Helgaas
2008-02-04 18:18 ` Linus Torvalds
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=47A2644B.4000905@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=avuton@gmail.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=torvalds@linux-foundation.org \
--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