From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Adam Belay <ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: PNP & ACPI
Date: 11 Aug 2004 18:16:15 -0400 [thread overview]
Message-ID: <1092262575.5021.129.camel@dhcppc4> (raw)
In-Reply-To: <566B962EB122634D86E6EE29E83DD808182C2317-N2PTB0HCzHJviC08c4yzC1DQ4js95KgL@public.gmane.org>
Adam,
Nice to meet you in Ottawa.
Do you have a patch to disable PNP when ACPI is running?
I think we could key off of acpi_disabled -- since that
will be set when ACPI is not configured, when Linux/ACPI
can't find ACPI support in the system, or any other problems
that cause ACPI to bail out.
I don't see a global pnp_disabled flag we can set.
Looks like we've got 3 subsystems with pnp, pnpbios and isapnp,
each with their own initcalls?
thanks,
-Len
ps. We discussed a more unified driver probe/register model.
Today we've got pnp_register_driver(), acpi_bus_register_driver()
etc. Thoughts on that?
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next parent reply other threads:[~2004-08-11 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <566B962EB122634D86E6EE29E83DD808182C2317@hdsmsx403.hd.intel.com>
[not found] ` <566B962EB122634D86E6EE29E83DD808182C2317-N2PTB0HCzHJviC08c4yzC1DQ4js95KgL@public.gmane.org>
2004-08-11 22:16 ` Len Brown [this message]
[not found] ` <20040816204058.GA3824@neo.rr.com>
[not found] ` <20040816204058.GA3824-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.org>
2004-08-17 4:57 ` PNP & ACPI Len Brown
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=1092262575.5021.129.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ambx1-IBH0VoN/3vPQT0dZR+AlfA@public.gmane.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