LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Thomas Renninger <trenn@suse.de>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
	Li Shaohua <shaohua.li@intel.com>,
	Matthew Hall <mhall@mhcomputing.net>,
	Willem Riede <wriede@riede.org>,
	Robert Hancock <hancockr@shaw.ca>,
	Karl Bellve <karl.bellve@umassmed.edu>,
	Avuton Olrich <avuton@gmail.com>
Subject: Re: [patch 0/2] PNP: disable PNP motherboard resources that overlap PCI BARs
Date: Wed, 12 Mar 2008 00:14:18 +0100	[thread overview]
Message-ID: <1205277258.8194.13.camel@linux-2bdv.site> (raw)
In-Reply-To: <20080311212439.293001409@ldl.fc.hp.com>


On Tue, 2008-03-11 at 15:24 -0600, Bjorn Helgaas wrote:
> The following two patches fix several problems caused by BIOSes that
> report PNP motherboard device resources that overlap with PCI BARs.
> 
> I think these should go in before 2.6.25 because some of these problems
> showed up in 2.6.24 when we increased PNP_MAX_MEM from 4 to 12, and
> there's no good way to work around them.

I cannot judge about the "cleanness" because of possible changes of
initialization time of pci/pnp or whatever.

I can confirm that ACPI resource declarations (especially (only?) in the
general motherboard devices) are often rather broken.
Therefore I like your general approach compared to the per machine dmi
match quirks. I expect the latter (dmi matching) is rather hopeless.


   Thomas


      parent reply	other threads:[~2008-03-11 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 21:24 Bjorn Helgaas
2008-03-11 21:24 ` [patch 1/2] PNP: revert Supermicro H8DCE motherboard quirk Bjorn Helgaas
2008-03-11 21:24 ` [patch 2/2] PNP: disable PNP motherboard resources that overlap PCI BARs Bjorn Helgaas
2008-03-11 23:14 ` Thomas Renninger [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=1205277258.8194.13.camel@linux-2bdv.site \
    --to=trenn@suse.de \
    --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=karl.bellve@umassmed.edu \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhall@mhcomputing.net \
    --cc=shaohua.li@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=wriede@riede.org \
    --subject='Re: [patch 0/2] PNP: disable PNP motherboard resources that overlap PCI BARs' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).