From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 15 05:41:18 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 0E5D316A41A for ; Thu, 15 Jun 2006 05:41:18 +0000 (UTC) (envelope-from nate@root.org) Received: from ylpvm01.prodigy.net (ylpvm01-ext.prodigy.net [207.115.57.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9536143D45 for ; Thu, 15 Jun 2006 05:41:17 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout6-ext.prodigy.net (pimout6-int.prodigy.net [207.115.4.22]) by ylpvm01.prodigy.net (8.13.6 out spool5000 dk/8.12.10) with ESMTP id k5F5fCIV006642 for ; Thu, 15 Jun 2006 01:41:12 -0400 X-ORBL: [71.139.104.128] Received: from [10.0.5.50] (ppp-71-139-104-128.dsl.snfc21.pacbell.net [71.139.104.128]) by pimout6-ext.prodigy.net (8.13.6 out.dk/8.13.6) with ESMTP id k5F5fFTJ253004; Thu, 15 Jun 2006 01:41:16 -0400 Message-ID: <4490F291.9010406@root.org> Date: Wed, 14 Jun 2006 22:39:29 -0700 From: Nate Lawson User-Agent: Thunderbird 1.5.0.2 (X11/20060501) MIME-Version: 1.0 To: john@utzweb.net References: <86zmgi1zab.wl%john@utzweb.net> <86y7w21y3o.wl%john@utzweb.net> <448DA197.70707@root.org> <86wtbm1xgj.wl%john@utzweb.net> <448DD256.7040307@root.org> <34543.69.93.78.27.1150155257.squirrel@69.93.78.27> In-Reply-To: <34543.69.93.78.27.1150155257.squirrel@69.93.78.27> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: debug.acpi.avoid, how do i use it to tell acpi to not control the keyboard? 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, 15 Jun 2006 05:41:18 -0000 john@utzweb.net wrote: >> John L.Utz III wrote: >>> At Mon, 12 Jun 2006 10:17:11 -0700, >>> Nate Lawson wrote: >>> wouldnt this be the one to avoid, assuming that 'KBC' is >>> KeyboardController? >>> >>> Device (KBC) >>> { >>> Name (_HID, EisaId ("PNP0303")) >>> Name (CRS, ResourceTemplate () >>> { >>> IO (Decode16, 0x0060, 0x0060, 0x10, 0x01) >>> IO (Decode16, 0x0064, 0x0064, 0x04, 0x01) >>> IRQNoFlags () {1} >>> }) >>> Method (_CRS, 0, NotSerialized) >>> { >>> Return (CRS) >>> } >>> } >>> >>> >>> >>> can you clarify your comment a trifle? >> It would take a long time to explain it fully. ACPI is not controlling >> your keyboard. The BIOS just decides whether or not to send ACPI hotkey >> events (different from keystrokes) or consume them itself via SMI. > > so, the act of loading acpi.ko implements a callback for the bios that > informs it that an acpi cognizant os is available? > > it seems to me that i would like to tell it to not use acpi and stick with > smi because if i dont load acpi the buttons work almost perfectly. the > only bit of grief i have is that without acpi, the powerbutton shuts off > hard instead of performing a shutdown Yep, that's your choice. >> For some reason, the notify isn't getting delivered to ACPI along >> the way. > > some do, some dont, suspend get's responded to, power button get's > responded to. > > what commands do i use to break on buttons in acpidb? Just stick a printf in acpi_button.c? -- Nate