From owner-freebsd-acpi@FreeBSD.ORG Mon May 14 21:28:13 2007 Return-Path: X-Original-To: acpi@freebsd.org Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6759E16A405 for ; Mon, 14 May 2007 21:28:13 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id 3081313C48C for ; Mon, 14 May 2007 21:28:12 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 65545 invoked from network); 14 May 2007 21:28:13 -0000 Received: from 209-128-117-003.bayarea.net (HELO ?10.0.1.144?) (nate-mail@209.128.117.3) by root.org with ESMTPA; 14 May 2007 21:28:13 -0000 Message-ID: <4648D460.9040400@root.org> Date: Mon, 14 May 2007 14:28:00 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.7 (X11/20061027) MIME-Version: 1.0 To: Takanori Watanabe References: <200705141857.l4EIvr1l019810@sana.init-main.com> In-Reply-To: <200705141857.l4EIvr1l019810@sana.init-main.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: acpi@freebsd.org, Harald Schmalzbauer Subject: Re: acpi_hpet not found 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: Mon, 14 May 2007 21:28:13 -0000 Takanori Watanabe wrote: > In message <200705142056.05598.h.schmalzbauer@omnisec.de>, Harald Schmalzbauer > さんいわく: >> Hello, >> >> on my workstation the HPEtimer is not found, but it's enabled in 32-bit mode >> in BIOS, so I think there is one... It's a 965P (ich8) chipset. >> >> I can't find anything regarding HPET in tha man pages. Any hints? > > Show your acpi tables. It may have to support HPET table. Here's what I got from his post: /* HPET: Length=56, Revision=1, Checksum=232, OEMID=GBT, OEM Table ID=GBTUACPI, OEM Revision=0x42302e31, Creator ID=GBTU, Creator Revision=0x98 HPET Number=0 ADDR=0xfed00000:0[0] (Memory) HW Rev=0x1 Comparitors=2 Counter Size=1 Legacy IRQ routing capable={TRUE} PCI Vendor ID=0x8086 Minimal Tick=16 */ But he has no Device of type PNP0103. So we need to implement table-based HPET probing, not just AML PNP probing. This is similar to how we handle ECDT for the embedded controller. When we do that, we also need to work around the fact that the address bit width is wrong (0). -- Nate