From owner-freebsd-arch@FreeBSD.ORG Thu Oct 28 18:15:47 2010 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72F43106564A for ; Thu, 28 Oct 2010 18:15:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 44C828FC32 for ; Thu, 28 Oct 2010 18:15:47 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id C039246B0C; Thu, 28 Oct 2010 14:15:46 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D1DEF8A009; Thu, 28 Oct 2010 14:15:45 -0400 (EDT) From: John Baldwin To: freebsd-arch@freebsd.org Date: Thu, 28 Oct 2010 13:59:31 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100819; KDE/4.4.5; amd64; ; ) References: <201010281254.39862.jhb@freebsd.org> <4CC9AB72.1000800@feral.com> In-Reply-To: <4CC9AB72.1000800@feral.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201010281359.31192.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 28 Oct 2010 14:15:45 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.9 required=4.2 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Matthew Jacob Subject: Re: Removing acpi.ko support X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2010 18:15:47 -0000 On Thursday, October 28, 2010 12:57:22 pm Matthew Jacob wrote: > Will there be still a a way to disable it from the OK prompt? Yes. Using 'hint.acpi.0.disabled=1' has always worked to do that and the 'safe mode' menu item will continue to disable ACPI via that tunable (though for many newer machines disabling ACPI is actually less safe, but that is the subject of a separate thread). > On 10/28/2010 9:54 AM, John Baldwin wrote: > > [ cc'ing acpi@ to be safe, but I think the topic warrants the wider audience > > of arch@ ] > > > > I think we should drop support for having acpi load as a module for i386. It > > adds extra complication and hacks to the i386 APIC and interrupt code that are > > gratuitously different from amd64 as a result. Originally it was made a > > module so that GENERIC on i386 did not include ACPI by default but would only > > use up memory to hold ACPI-related code if the machine supported ACPI. Now > > that acpi is part of GENERIC on i386 in 8.0 and later this argument is no > > longer relevant. I'd like to remove support for ACPI as a module to remove > > the various hacks on i386 and reduce differences with amd64. > > > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > -- John Baldwin