From: Rene Herman <rene.herman@keyaccess.nl>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
shaohua.li@intel.com, Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH]: PNP: Increase the value of PNP constant
Date: Fri, 16 Nov 2007 17:52:48 +0100 [thread overview]
Message-ID: <473DCAE0.9040401@keyaccess.nl> (raw)
In-Reply-To: <1195198798.2460.18.camel@yakui_zhao.sh.intel.com>
On 16-11-07 08:39, Zhao Yakui wrote:
> Subject: PNP: Increase the value of PNP constant
> From: Zhao Yakui <yakui.zhao@intel.com>
>
> On some systems the number of resources(IO,MEM) returnedy by PNP
> device is greater than the PNP constant, for example motherboard devices.
> It brings that some resources can't be reserved and resource confilicts.
> This will cause PCI resources are assigned wrongly in some systems, and
> cause hang. This is a regression since we deleted ACPI motherboard
> driver and use PNP system driver.
>
> Andrew, I thought this is an urgent issue and should be fixed ASAP, and
> this is a good candidate for -stable tree
>
> Signed-off-by: Li Shaohua <shaohua.li@intel.com>
> Signed-off-by: Zhao Yakui <yakui.zhao@intel.com>
>
> ---
> drivers/pnp/pnpacpi/rsparser.c | 18 ++++++++++++++++--
> include/linux/pnp.h | 4 ++--
> 2 files changed, 18 insertions(+), 4 deletions(-)
>
> Index: linux-2.6.24-rc2/include/linux/pnp.h
> ===================================================================
> --- linux-2.6.24-rc2.orig/include/linux/pnp.h
> +++ linux-2.6.24-rc2/include/linux/pnp.h
> @@ -13,8 +13,8 @@
> #include <linux/errno.h>
> #include <linux/mod_devicetable.h>
>
> -#define PNP_MAX_PORT 8
> -#define PNP_MAX_MEM 4
> +#define PNP_MAX_PORT 24
> +#define PNP_MAX_MEM 12
This fairly significantly grows (for example?) a struct pnp_resource_table.
Are 24 and 12 really sensible?
Rene.
next prev parent reply other threads:[~2007-11-16 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 7:39 [PATCH]: PNP: Increase the value of PNP constant Zhao Yakui
2007-11-16 16:52 ` Rene Herman [this message]
2007-11-16 20:46 ` Bjorn Helgaas
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=473DCAE0.9040401@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--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