From mboxrd@z Thu Jan 1 00:00:00 1970 From: Len Brown Subject: Re: [PATCH] resend, early ACPI init Date: 15 Feb 2005 15:47:03 -0500 Message-ID: <1108500423.2096.285.camel@d845pe> References: <1108497779.7373.24.camel@tdi> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit In-Reply-To: <1108497779.7373.24.camel@tdi> Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Alex Williamson Cc: ACPI Developers List-Id: linux-acpi@vger.kernel.org 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. 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. I'm also nervous about enabling/disabling ACPI mode and then enabling it again -- this could risk unforseen firmware interactions. thanks, -Len ------------------------------------------------------- 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