From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 16 14:22:31 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 C391E16A407 for ; Tue, 16 Jan 2007 14:22:31 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.freebsd.org (Postfix) with ESMTP id 8CB7813C459 for ; Tue, 16 Jan 2007 14:22:31 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1H6pCo-0003Nh-00; Tue, 16 Jan 2007 15:22:30 +0100 Date: Tue, 16 Jan 2007 15:22:30 +0100 To: John Baldwin Message-ID: <20070116142230.GQ4945@poupinou.org> References: <87A429B7-46CD-426B-A56F-07D57F2E769E@patpro.net> <20070115165059.GP4945@poupinou.org> <200701151739.46792.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701151739.46792.jhb@freebsd.org> User-Agent: Mutt/1.5.9i From: Bruno Ducrot 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 14:22:31 -0000 On Mon, Jan 15, 2007 at 05:39:46PM -0500, 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. Well, I don't remember Intel released such information, but I've not checked that for a long time, being actually more interrested by AMD stuff. Do you have any pointer about that? -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.