From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Sarjeant Subject: Re: Gateway 200X (again) - No power button events Date: Wed, 21 Jan 2004 10:25:14 -0500 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <1074698713.5964.23.camel@localhost> References: <1074630523.3313.17.camel@localhost> <1074633425.3317.20.camel@localhost> <20040121102356.GU25416@poupinou.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20040121102356.GU25416-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Ducrot Bruno Cc: "Grover, Andrew" , Nate Lawson , acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org On Wed, 2004-01-21 at 05:23, Ducrot Bruno wrote: > 1- At first, does this info file give accurate informations? Yes. When it detects the FF power button, I have this: type: Power Button (FF) When I comment out those lines in scan.c to get the CM button, it reads: type: Power Button (CM) > 2- What happens if in one terminal you do something like > watch -d 'cat /proc/interrupts' > then press this button? I tried this with the FF button. Interestingly, it does generate interrupts when I press it (I unloaded all of the ACPI modules except for button, so I imagine that this must be what caused the requests on the acpi interrupt). So, I do get some sort of response from the system. Should button.c acpi_button_notify_fixed() be called when I press the FF button? It isn't currently. > 3- also look into the ASL > if you have some Notify(PWRF, ...), then try to insert some > debug statements via Store ("PWRF notify xx", Debug) with > xx being the number of the notify. I don't have any Notify(PWRF, ...) methods in the ASL. They are all Notify(PWRB, ...). When the system detects the FF button, it refers to it as PWRF, and when it detects the CM button, it refers to it as PWRB. In fact, the DSDT doesn't define a PWRF at all. I imagine that that is specified in the FADT? As Andy said, the system disregards the CM button entirely when it finds the FF button. I submitted a bug (1920), so perhaps the behavior will change in the future. But I guess that that contradicts the spec, so maybe not. I wouldn't want to break a bunch of other machines just for the sake of a little convenience on my laptop :) Perhaps the real problem is that the FF button isn't generating events? Thanks, Greg ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn