From owner-freebsd-acpi@FreeBSD.ORG Mon Jan 3 02:48:39 2005 Return-Path: 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 013D716A4CE for ; Mon, 3 Jan 2005 02:48:39 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B631443D1D for ; Mon, 3 Jan 2005 02:48:38 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-95.dsl.snfc21.pacbell.net [64.171.186.95]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j032mbGV025056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Jan 2005 18:48:37 -0800 Message-ID: <41D8B23E.9000503@root.org> Date: Sun, 02 Jan 2005 18:47:26 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <41D1C63E.5020201@nbritton.org> <20050101151558.L87126@carver.gumbysoft.com> In-Reply-To: <20050101151558.L87126@carver.gumbysoft.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org Subject: Re: HP OmniBook 6000 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Jan 2005 02:48:39 -0000 Doug White wrote: > On Tue, 28 Dec 2004, Nikolas Britton wrote: > > >>Any OmniBook 6000 owners out there that can comment on ACPI support in >>FreeBSD 5.x?... or any other problems with this system. I was thinking >>about getting one. As I'm sure there are meny variants of this model the >>specs for the system in question are: PIII@700Mhz, 12GB, 256 or 512MB, >>DVD drive, and 14" LCD > > > It used to be fatally broken, due to violating assumptions in the ACPICA > code at the time regarding probe order. But that was back when those > machines were new, and the code may now handle that case :-) > I don't know how well that system works but the sysresource issues were fixed a while back (before 5.3) -- Nate