Date: Mon, 12 Jun 2006 13:45:10 -0700 From: Nate Lawson <nate@root.org> To: "John L.Utz III" <john@utzweb.net> Cc: freebsd-acpi@freebsd.org Subject: Re: debug.acpi.avoid, how do i use it to tell acpi to not control the keyboard? Message-ID: <448DD256.7040307@root.org> In-Reply-To: <86wtbm1xgj.wl%john@utzweb.net> References: <86zmgi1zab.wl%john@utzweb.net> <86y7w21y3o.wl%john@utzweb.net> <448DA197.70707@root.org> <86wtbm1xgj.wl%john@utzweb.net>
next in thread | previous in thread | raw e-mail | index | archive | help
John L.Utz III wrote:
> At Mon, 12 Jun 2006 10:17:11 -0700,
> Nate Lawson wrote:
>> John L.Utz III wrote:
>>> oops, correction
>>>
>>> At Mon, 12 Jun 2006 09:47:08 +0000,
>>> John L.Utz III wrote:
>>>> Hello again;
>>>>
>>>> to quote man acpi:
>>>>
>>>>
>>>> It is also possible to avoid portions of the ACPI namespace which may be
>>>> causing problems, by listing the full path of the root of the region to
>>>> be avoided in the kernel environment variable debug.acpi.avoid. The
>>>> object and all of its children will be ignored during the bus/children
>>>> scan of the namespace. The ACPI CA code will still know about the
>>>> avoided region.
>>>>
>>>> so, if i wanted to let acpi drive the power button and the suspend keypress but ignore everything else, how would one do that?
>>>
>>> amend to read
>>>
>>> so, if i wanted to let acpi drive the power button and the suspend keypress
>>> but ignore everything else ON THE KEYBOARD, how would one do that?
>>>
>>>
>>>> or failing that, can someone provide a sample use of acpi.debug.avoid that i can work from?
>>>>
>> Nope, that's not how PCs work.
>
>
> hmm,
>
> 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. For
some reason, the notify isn't getting delivered to ACPI along the way.
Upgrade your BIOS?
--
Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448DD256.7040307>