From: Shaohua Li <shaohua.li@intel.com>
To: matthieu castet <castet.matthieu@free.fr>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
acpi-devel@lists.sourceforge.net, Adam Belay <ambx1@neo.rr.com>,
linux-kernel@vger.kernel.org
Subject: Re: [ACPI] Re: [PATCH] PNPACPI: fix types when decoding ACPI resources [resend]
Date: Thu, 04 Aug 2005 08:51:52 +0800 [thread overview]
Message-ID: <1123116712.2929.8.camel@linux-hp.sh.intel.com> (raw)
In-Reply-To: <42F1343B.70707@free.fr>
On Wed, 2005-08-03 at 23:16 +0200, matthieu castet wrote:
>
> There are drivers/acpi/motherboard.c that done some stuff already handle
> by pnp/system.c.
Yes, it should be disabled if pnpacpi is enabled. The only concern is
motherboard.c also request some ACPI resources, which might not declaim
in ACPI motherboard device, but it's completely BIOS dependent. We might
could try remove it at -mm tree to see if it breaks any system later.
>
> PS : I saw in acpi ols paper that you plan once all dupe acpi drivers
> will be removed to register again the pnp device in acpi layer. Do you
> plan to add more check and for example add only device that have a CRS
> in pnp layer ?
For detecting PNP device? it's worthy trying.
Thanks,
Shaohua
next prev parent reply other threads:[~2005-08-04 0:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 15:55 [PATCH] PNPACPI: fix types when decoding ACPI resources [resend] Bjorn Helgaas
2005-08-03 1:01 ` Shaohua Li
2005-08-03 15:20 ` [ACPI] " Bjorn Helgaas
2005-08-03 21:16 ` matthieu castet
2005-08-03 21:41 ` Bjorn Helgaas
2005-08-04 12:38 ` matthieu castet
2005-08-04 15:57 ` Bjorn Helgaas
2005-08-04 16:08 ` matthieu castet
2005-08-04 0:51 ` Shaohua Li [this message]
2005-08-28 17:40 ` matthieu castet
2005-08-04 0:46 ` Shaohua Li
2005-08-03 1:05 ` [ACPI] " Kenji Kaneshige
2005-08-03 18:29 ` Bjorn Helgaas
2005-08-04 5:18 ` Kenji Kaneshige
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=1123116712.2929.8.camel@linux-hp.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--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