linux-kernel - Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0 sound card

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <47A2644B.4000905@shaw.ca>
Date:	Thu, 31 Jan 2008 18:14:03 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	avuton@...il.com, yakui.zhao@...el.com, shaohua.li@...el.com,
	bjorn.helgaas@...com, trenn@...e.de, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: a7839e96 (PNP: increase max resources) breaks my ALSA intel8x0
 sound card

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/