public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Len Brown <len.brown@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Adam Belay <ambx1@neo.rr.com>
Subject: ACPIPNP and too large IO resources
Date: Wed, 05 Jul 2006 08:47:43 +0200	[thread overview]
Message-ID: <44AB608F.1060903@drzeus.cx> (raw)

Hi there!

Commit 1acfb7f2b0d460ee86bdb25ad0679070ec8a5f0d by Bjorn is causing me
some grief. Although the patch seems correct, it is triggering another
misfeature of the system and I am hoping you have a solution.

Before your patch, the PCI bridge didn't allocate many io ports as they
were mislabeled as iomem. But now it puts its dirty paws all over the
entire ISA io port address space, effectively disabling PNP.

On my machine it steals the ranges 0x0-0xcf7, 0xcf8-0xcff and
0xd00-0xffff. IOW, the entire range of 0x0-0xffff gets blocked and none
of the ISA PNP devices can use ports outside this range.

We can see the same effect in the example given in your commit where
only the range 0x3b0-0x3df is left open.

I don't know enough about PNP to determine the problem, but I guess it's
the section that checks overlaps with other PNP devices that is somehow
wrong. It could also be that everyone keeps coding their DSDTs wrong,
but if that's the case then I see little other choice than to be bug
compatible.

Rgds
Pierre

             reply	other threads:[~2006-07-05  6:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05  6:47 Pierre Ossman [this message]
2006-07-05 16:47 ` ACPIPNP and too large IO resources Bjorn Helgaas
2006-07-05 20:53   ` Pierre Ossman
2006-07-05 21:36     ` Bjorn Helgaas
2006-07-05 22:18       ` Andrew Morton
2006-07-06 15:29         ` Bjorn Helgaas
2006-07-07  1:03           ` Shaohua Li
2006-08-05  0:19             ` Pierre Ossman
2006-08-05  1:07               ` Andrew Morton

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=44AB608F.1060903@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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