From: Valdis.Kletnieks@vt.edu
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Dave Young <hidave.darkstar@gmail.com>,
Shaohua Li <shaohua.li@intel.com>,
Rene Herman <rene.herman@keyaccess.nl>,
yakui.zhao@intel.com, Chris Holvenstot <cholvenstot@comcast.net>,
linux-kernel@vger.kernel.org, trenn@suse.de,
Andrew Morton <akpm@osdl.org>
Subject: Re: pnpacpi : exceeded the max number of IO resources
Date: Tue, 18 Dec 2007 22:07:39 -0500 [thread overview]
Message-ID: <26206.1198033659@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 05 Dec 2007 13:39:04 MST." <200712051339.04936.bjorn.helgaas@hp.com>
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Wed, 05 Dec 2007 13:39:04 MST, Bjorn Helgaas said:
> > -#define PNP_MAX_PORT 24
> > +#define PNP_MAX_PORT 128
> > #define PNP_MAX_MEM 12
> > #define PNP_MAX_IRQ 2
> > #define PNP_MAX_DMA 2
>
> I don't think we can increase PNP_MAX_PORT to 128. Only one or two
> devices need that many, so just bumping the max wastes a LOT of space.
> A struct resource is seven longs, so on a 32-bit system with sixteen
> PNP devices, we'd be wasting (128-24)*7*4*16 = almost 47Kbytes.
>
> In hindsight, I should not have removed drivers/acpi/motherboard.c
> until we had dynamic PNP resource tables. We could revert that
> change [1], but the driver's been gone since 2.6.21, so I don't
> think it's that urgent. It's just that we used to silently ignore
> resources past the limits, and in -mm, we now print a KERN_ERR message.
>
> So I think we should either remove the message altogether (so we're
> exactly like 2.6.23 in this regard), or at least tone it down to
> a KERN_WARN or something.
>
> And we need to get Thomas' dynamic patch into -mm ASAP :-)
*ping*! :)
My laptop still hits the PNP_MAX_MEM=12 warning in -rc5-mm1 - what's the
status on Thomas's patch? No biggie - I just want to make sure it hasn't
been dropped through the cracks someplace....
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2007-12-19 3:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 13:14 pnpacpi : exceeded the max number of IO resources Chris Holvenstot
2007-11-30 22:22 ` Rene Herman
2007-12-03 17:02 ` Rene Herman
2007-12-03 22:51 ` Chris Holvenstot
2007-12-04 0:55 ` Shaohua Li
2007-12-04 1:15 ` Dave Young
2007-12-05 20:39 ` Bjorn Helgaas
2007-12-19 3:07 ` Valdis.Kletnieks [this message]
2008-01-09 3:50 ` Len Brown
2008-01-09 9:34 ` Frans Pop
2008-01-09 14:47 ` Rene Herman
2008-01-16 5:55 ` Dave Young
2008-01-16 8:00 ` Rene Herman
2008-01-16 13:04 ` Rene Herman
2008-01-19 11:03 ` Frans Pop
2008-01-19 18:38 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 9:11 Dave Young
2007-11-30 1:18 ` Dave Young
2007-11-30 2:21 ` Zhao Yakui
2007-11-30 6:40 ` Valdis.Kletnieks
2007-11-30 8:14 ` Zhao Yakui
2007-11-30 2:18 ` Rene Herman
2007-11-30 2:32 ` 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=26206.1198033659@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=cholvenstot@comcast.net \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--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;
as well as URLs for NNTP newsgroup(s).