From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 7 05:38:59 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1A6E16A4CE; Fri, 7 Nov 2003 05:38:59 -0800 (PST) Received: from sana.init-main.com (104.194.138.210.bn.2iij.net [210.138.194.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00B0C43FF7; Fri, 7 Nov 2003 05:38:58 -0800 (PST) (envelope-from takawata@init-main.com) Received: from init-main.com (localhost [127.0.0.1]) by sana.init-main.com (8.12.10/8.12.9) with ESMTP id hA7DVfkf026399; Fri, 7 Nov 2003 22:31:41 +0900 (JST) (envelope-from takawata@init-main.com) Message-Id: <200311071331.hA7DVfkf026399@sana.init-main.com> To: jhb@freebsd.org Date: Fri, 07 Nov 2003 22:31:41 +0900 From: Takanori Watanabe cc: hackers@freebsd.org cc: acpi-jp@jp.freebsd.org Subject: Re-enabling ACPI module. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Nov 2003 13:38:59 -0000 Hi, I looked in the new APIC code you commit. The thing that prevent ACPI subsystem from moduler is the way we aquire ACPI root pointer, I think. Right? If so, we can took this in way. 1. Move u_long i386_acpi_root; to machdep.c and madt.c use i386_acpi_root variable, instead of calling AcpiOsGetRootPointer. If Boot loader failed to detect ACPI root pointer, the MADT table is not used, even if the OS can detect it. 2. Re-imprement AcpiOsGetRootPointer so that it does not use AcpiFindRootPointer(). Which do you think better?