From owner-freebsd-acpi@FreeBSD.ORG Wed May 3 14:44:38 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EAFA16A40E for ; Wed, 3 May 2006 14:44:38 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id B452F43D68 for ; Wed, 3 May 2006 14:44:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k43EiSKw043858; Wed, 3 May 2006 10:44:29 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marcel Moolenaar Date: Wed, 3 May 2006 09:32:52 -0400 User-Agent: KMail/1.9.1 References: <20060502181804.GA93421@svm.csie.ntu.edu.tw> <200605021559.44121.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605030932.54775.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1437/Wed May 3 02:54:45 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.3 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx Cc: freebsd-acpi@freebsd.org, Rong-En Fan Subject: Re: acpi as kernel module on i386 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2006 14:44:38 -0000 On Tuesday 02 May 2006 18:51, Marcel Moolenaar wrote: > > On May 2, 2006, at 12:59 PM, John Baldwin wrote: > > > On Tuesday 02 May 2006 14:18, Rong-En Fan wrote: > >> Hi, > >> > >> Recently commit to ppc code that also decouples the isa+acpi > >> attachment into separate case, that makes my ppc and lpt disappear > >> if acpi is loaded as a module. (see the thread "lpt0 disappear (ppc > >> related) on -current) > >> > >> However, i386/conf/NOTES says that building acpi into module is > >> deprecated. Just wondering why amd64 uses acpi in kernel conf > >> (I'm not sure about other arch), and on i386 we said this is a > >> deprecated usage? > > > > ACPI is mandatory for amd64 and ia64, but it is optional on i386. > > Because it is optional, it is a module so that the loader can only > > load it on machines that support it. I think the ppc module should > > be changed to include the acpi attachment personally, assuming that > > the ppc module already includes the ppc isa attachment. > > On i386, it should be safe to compile the acpi(4) attachment when only > device isa is configured into the kernel. It should not be done for all > platforms. While acpi(4) is mandatory on ia64, isa(4) isn't and it's > my goal to get rid of isa(4) altogether on ia64. Well, the ppc acpi attachment can be optionally included in the module build for the archs that ppc acpi devices. > Alternatively, acpi(4) can be considered non-optional for current > x86 hardware and having acpi(4) configured into the kernel is not > such an odd thing to do for a modern x86 operating system. I personally compile 'device acpi' into my kernels on i386 and basically never use modules except for development anyway. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org