From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 9 18:42:50 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7468616A4CE; Wed, 9 Feb 2005 18:42:50 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A0CF43D31; Wed, 9 Feb 2005 18:42:50 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j19IgCWk031560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 9 Feb 2005 10:42:15 -0800 Message-ID: <420A5983.4070302@root.org> Date: Wed, 09 Feb 2005 10:42:11 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <42068A5C.1030300@root.org> <42090EBE.1030202@root.org> <346a802205020909273c413d03@mail.gmail.com> <200502091304.17896.jkim@niksun.com> In-Reply-To: <200502091304.17896.jkim@niksun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-amd64@freebsd.org cc: cokane@cokane.org Subject: Re: HEADSUP: cpufreq import complete, acpi_throttling changed X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2005 18:42:50 -0000 Jung-uk Kim wrote: > On Wednesday 09 February 2005 12:27 pm, Coleman Kane wrote: > >>Ooops. Sorry, I knew this. Uhm in that case, is the acpi_ppc driver >>being brought in, or similar functionality? I really like the >>auto-scaling that ppc does. > > > We will be able to write a simple daemon to do the job, something like > cpufreqd: > > http://cpufreqd.sourceforge.net/ > > That's what the API is for... Please do. However, it would be good if you sent a design email outlining your plans before starting coding. -- Nate