From: Alex Williamson <alex.williamson-VXdhtT5mjnY@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Re: [PATCH] resend, early ACPI init
Date: Tue, 15 Feb 2005 14:56:54 -0700 [thread overview]
Message-ID: <1108504614.7373.92.camel@tdi> (raw)
In-Reply-To: <1108500423.2096.285.camel@d845pe>
On Tue, 2005-02-15 at 15:47 -0500, Len Brown wrote:
> Rather than add a CONFIG option to enable/disable ACPI extra early,
> could it be possible to simply enable ACPI earlier and leave it enabled
> on all platforms?
>
> I'm really not excited about yet another CONFIG option -- we need fewer,
> not more. And if earlier init is necessary on one machine, we may find
> over time that we need it on others too.
Yes, an early, one-time init would certainly make more sense than
doing the whole thing twice. I wasn't sure if anyone would be
interested in generically hooking ACPI in that early and deeply.
> Indeed, in 2.6 we moved most of the init earlier into acpi_early_init(),
> but that wasn't as early as this, and didn't include the object_init,
> which apparently is what you're looking for.
Yep, for my current usage, I just need to look through namespace for
a specific _HID value.
> I'm also nervous about enabling/disabling ACPI mode and then enabling it
> again -- this could risk unforseen firmware interactions.
I'm nervous about that too. In fact, my current usage is limited to
only running on an ia64 box with a specific ACPI static table OEM ID.
If it isn't an obvious dead-end, I'll look into a generic interface that
could be brought up early and stay up. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-02-15 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 20:02 [PATCH] resend, early ACPI init Alex Williamson
2005-02-15 20:47 ` Len Brown
2005-02-15 21:56 ` Alex Williamson [this message]
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=1108504614.7373.92.camel@tdi \
--to=alex.williamson-vxdhtt5mjny@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@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