From: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
To: Yu Luming <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: 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: [Acpi4asus-user] Re: Re: [PATCH] Fixed buffered ACPI events for a lot ASUS machines
Date: Tue, 13 Sep 2005 12:39:01 +0200 [thread overview]
Message-ID: <4326AC45.3080006@suse.de> (raw)
In-Reply-To: <200509131708.53544.luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Yu Luming wrote:
>> I used vanilla-2.6.13 with acpica-20050902 patches on it.
> Yes, this version has latest ec patch.
>> 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.
> It should be old behavior. Because, ec gpe will be wrongly disabled in some
> cases. I think the issue should be fixed in the latest ec patch. Because, ec
> gpe is always be enabled at run-time.
>
Yes, seems as if you are right.
I mixed up kernels during testing.
This seems to be sovled with latest 20050902 patch.
Sorry for this one, I am a bit in a pressure of time...
Could you please line out the change to the older ec_burst patch by some
code.
It's very hard to pitch on the big ACPICA commits for little fixes.
ec_burst patch will be enabled in SUSE Linux 10.0 by default.
Beside lost mouse/key-strokes on some specific machines (also happen with
ec_burst=0), I don't know of any greater harm ec_burst causes.
If you know any other issues I'd appreciate if you let me know.
Hmm, searching for something that could have fixed it in the to-akpm/broken-out
directory of Len, I don't find anything than the huge ACPICA-20050408 commit...
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 10:39 UTC|newest]
Thread overview: 6+ 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
[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 ` Thomas Renninger [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 14:21 [Acpi4asus-user] " Yu, Luming
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=4326AC45.3080006@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