From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: Li Shaohua <shaohua.li@intel.com>
Cc: ACPI-DEV <acpi-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Adam Belay <ambx1@neo.rr.com>,
Matthieu <castet.matthieu@free.fr>,
Bjorn Helgaas <bjorn.helgaas@hp.com>
Subject: Re: [PATCH 4/5]ACPI PNP driver
Date: Thu, 21 Oct 2004 09:01:26 +0300 [thread overview]
Message-ID: <417750B6.7000409@kolumbus.fi> (raw)
In-Reply-To: <1098327568.6132.226.camel@sli10-desk.sh.intel.com>
Li Shaohua wrote:
>Hi,
>This patch provides an ACPI based PNP driver. It is based on Matthieu
>Castet's original work. With this patch, legacy device drivers (floppy
>ACPI driver, COM ACPI driver, and ACPI motherboard driver) which
>directly use ACPI can be removed, since now we have unified PNP
>interface for legacy devices.
>
>Thanks,
>Shaohua
>
>Signed-off-by: Li Shaohua <shaohua.li@intel.com>
>
>The patch depends on previous 3 patches.
>
>--- 2.6/drivers/pnp/isapnp/Kconfig.stg3 2004-10-18 17:34:17.591712040
>+0800
>+++ 2.6/drivers/pnp/isapnp/Kconfig 2004-10-18 17:36:19.173228840 +0800
>
>
Are you supposed to list here _every_ device to which not to bind? Is
this feasible? Maybe take another approach and bind to the "default"
acpi pnp driver if no specific driver found ?
+static char excluded_id_list[] =
+ "PNP0C0A," /* Battery */
+ "PNP0C0C,PNP0C0E,PNP0C0D," /* Button */
+ "PNP0C09," /* EC */
+ "PNP0C0B," /* Fan */
+ "PNP0A03," /* PCI root */
+ "PNP0C0F," /* Link device */
+ "PNP0000," /* PIC */
+ "PNP0100," /* Timer */
+ ;
---Mika
next prev parent reply other threads:[~2004-10-21 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 3:00 [PATCH 4/5]ACPI PNP driver Li Shaohua
2004-10-21 3:00 ` Li Shaohua
2004-10-21 6:01 ` Mika Penttilä [this message]
2004-10-21 6:03 ` Li Shaohua
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=417750B6.7000409@kolumbus.fi \
--to=mika.penttila@kolumbus.fi \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=castet.matthieu@free.fr \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.