From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: Yu Luming <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
jfvasconcelos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
"Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] Fixed buffered ACPI events for a lot ASUS machines
Date: Tue, 13 Sep 2005 09:18:27 +0200 [thread overview]
Message-ID: <43267D43.3070305@suse.de> (raw)
In-Reply-To: <200509131031.43570.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Yu Luming wrote:
> On Monday 12 September 2005 19:39, Thomas Renninger wrote:
>> Hi,
>>
>> I finally could resolve the buffering of ACPI events on
>> some ASUS (M6N, M6000, A3500N, A6000G, maybe more...)
>> when battery module is loaded.
>>
>> After hours of hopeless debugging I could track it down by comparing
>> with Yu Luming's previously patch posted on bugzilla.kernel.org.
> Do you mean the patch at http://bugzilla.kernel.org/show_bug.cgi?id=3851#c75?
> or http://bugzilla.kernel.org/show_bug.cgi?id=3851#c74
>> Yu, could you confirm that this is really fixing a bug and totally safe?
>>
> Now ec->burst.pending_gpe is useless. it will be cleaned up.
>
>> Or was this intended and could possibly lead to problems on other
>> machines?
>
> If the attached patch fixs the bug, I guess you are using old code.
>
I used vanilla-2.6.13 with acpica-20050902 patches on it.
So it still seems to be used, at least on ASUS machines.
One of your old EC-burst patches in
http://bugzilla.kernel.org/show_bug.cgi?id=3851
had this little change. After reports of working ASUS machines with
this one, I found that newer EC-burst version do not have this
change anymore, but behave as the non EC-burst code on these machines.
Therefore I asked whether this change was intended or whether it is
a bug that slipped in by accident. So I expect the latter?
Thanks,
Thomas
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next prev parent reply other threads:[~2005-09-13 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 11:39 [PATCH] Fixed buffered ACPI events for a lot ASUS machines Thomas Renninger
[not found] ` <432568E3.6040401-l3A5Bk7waGM@public.gmane.org>
2005-09-13 2:31 ` Yu Luming
[not found] ` <200509131031.43570.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2005-09-13 7:18 ` Thomas Renninger [this message]
[not found] ` <43267D43.3070305-l3A5Bk7waGM@public.gmane.org>
2005-09-13 9:08 ` Yu Luming
[not found] ` <200509131708.53544.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2005-09-13 10:39 ` [Acpi4asus-user] " Thomas Renninger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43267D43.3070305@suse.de \
--to=trenn-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=jfvasconcelos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox