From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 16 01:12:29 2007 Return-Path: X-Original-To: freebsd-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 5D41116A415 for ; Tue, 16 Jan 2007 01:12:29 +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 2914D13C471 for ; Tue, 16 Jan 2007 01:12:29 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 13406 invoked from network); 16 Jan 2007 00:11:32 -0000 Received: from ppp-71-139-39-138.dsl.snfc21.pacbell.net (HELO ?10.0.5.59?) (nate-mail@71.139.39.138) by root.org with ESMTPA; 16 Jan 2007 00:11:32 -0000 Message-ID: <45AC1826.6080307@root.org> Date: Mon, 15 Jan 2007 16:11:18 -0800 From: Nate Lawson User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: John Baldwin References: <87A429B7-46CD-426B-A56F-07D57F2E769E@patpro.net> <20070115165059.GP4945@poupinou.org> <200701151739.46792.jhb@freebsd.org> In-Reply-To: <200701151739.46792.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: acpi ok but cpufreq not supporting my CPUs 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: Tue, 16 Jan 2007 01:12:29 -0000 John Baldwin wrote: > On Monday 15 January 2007 11:51, Bruno Ducrot wrote: >> On Sun, Jan 14, 2007 at 10:02:06PM +0100, Patrick Proniewski wrote: >>> est0: on cpu0 >>> est: CPU supports Enhanced Speedstep, but is not recognized. >>> est: cpu_vendor GenuineIntel, msr a1e0a1e06000a1e >>> device_attach: est0 attach returned 6 >>> p4tcc0: on cpu0 >>> >>> (same for cpu1/2/3) >>> >>> Is there anything I can do to make "est" work with the sossaman CPU ? >>> >>> thanks in advance, >>> >> It's not possible, AFAIK, to build a static table for your processor, >> and in that case, we have to use an ACPI table in order to compute >> a custom table. If such information is not available, then there >> is little hope to make est working, being an SMP problem or not is >> not your problem I'm afraid. It maybe possible you forgot a >> BIOS option somewhat so such this configuration will be generated >> and exposed via ACPI though, or maybe you have to upgrade to a >> newer BIOS. > > One thing we can do is at least support the two modes encoded into the MSR > (the highest and lowest IIRC). I think I have a patch laying around > somewhere to do that. > That's a good idea. If you can send me a patch, I'd be happy to test. -- Nate