From owner-freebsd-acpi@FreeBSD.ORG Thu Oct 12 18:04:51 2006 Return-Path: X-Original-To: freebsd-acpi@freebsd.org 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 DE49916A4C8 for ; Thu, 12 Oct 2006 18:04:51 +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 5D23543E9F for ; Thu, 12 Oct 2006 18:03:11 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1GY4t4-0002FR-00; Thu, 12 Oct 2006 20:02:30 +0200 Date: Thu, 12 Oct 2006 20:02:30 +0200 To: John Utz Message-ID: <20061012180230.GA4945@poupinou.org> References: <26332441-4BC5-4392-806A-0179464E8D59@utzweb.net> <452D161A.5040509@root.org> <20061012160039.GY4945@poupinou.org> <9CBF3A89-3007-4752-9981-DECDDFE1A749@utzweb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9CBF3A89-3007-4752-9981-DECDDFE1A749@utzweb.net> User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-acpi@freebsd.org Subject: Re: if i was porting a linux kernel module that wrote out to /proc, where should i point it at in freebsd? 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: Thu, 12 Oct 2006 18:04:52 -0000 On Thu, Oct 12, 2006 at 09:41:33AM -0700, John Utz wrote: > > On Oct 12, 2006, at 9:00 AM, Bruno Ducrot wrote: > > >On Wed, Oct 11, 2006 at 09:04:42AM -0700, Nate Lawson wrote: > >>John Utz wrote: > >>>i've been working on i8k utils off and on for several months. > >>> > >>>(lately it's been what i've been doing whilst i sit at my daughter's > >>>gymnastics class) > >>> > >>>so several of the api's work, ie turning the fans on and off, etc. > >>> > >>>buttons *still* dont work. :-( > >>> > >>>at this point, i want to start working on hXRing the kernel module. > >>> > >>>as currently coded, it writes to /proc. > >>> > >>>i would prefer to not have to require the proc lkm for this to > >>>work, i'd > >>>rather do it the bsd way. > >>> > >>>so, umm, what *is* the bsd way ? :-) > >> > >>It looks like "i8k" is the Dell hotkeys/PM driver. Use sysctl as the > >>interface. See the other drivers in /sys/dev/acpi_support for a good > >>template (i.e., acpi_toshiba.c). > >> > > > >i8k is not an ACPI driver. I'm working on a acpi_dell one but I'm > >waiting a D620 (hint, hint :) > > > > yah, it's a combination of SMM and DMI, no acpi involved. I misunderstood Nate. I thought he suggested to put your driver under /sys/dev/acpi_support. I was wrong, he only suggested you should look at for example acpi_toshiba in order to implement some sysctl hooks. Sorry for confusion. > so technically, i suppose i shouldn't discuss it on this list. Well, on the other hand we discuss stuff that don't belong to ACPI, as for example cpufreq.. I guess we can discuss stuff related to power management in general. > however, this certainly seems like the best place to ask questions > about this since it's seems like SMM+DMI is the neanderthal fork > with ACPI > being the cromagnon fork (which i guess make PnP austrolopithicus). ACPI still need to go SMM at least for telling the BIOS to switch to ACPI mode (instead of Legacy). It's a transitional phase I believe, but the transition takes a very long time. Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care.