public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005-hi6Y0CQ0nG0@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: please test latest acpi patch
Date: Tue, 22 Mar 2005 00:04:14 +0100	[thread overview]
Message-ID: <423F52EE.4000703@gmx.net> (raw)
In-Reply-To: <423F08C5.3060405-hi6Y0CQ0nG0@public.gmane.org>

Carl-Daniel Hailfinger schrieb:
> Len Brown schrieb:
> 
>>There are some very important -- and in some cases,
>>potentially disruptive -- changes in the latest ACPI patch.
>>
>>EC Burst Mode -- battery status AE_TIME etc.
>>Binding ACPI power states to PCI devices -- power loss in S3
>>Generic Hot Key Driver -- needs configuration from user space
>>S3 Resume PCI Interrupt Link fix, requiring drivers to behave better
>>Poweroff fix -- compatible with kexec patch
>>Improved "Implicit Return" AML workaround -- toshiba, compaq etc.
>>Relaxed AE_AML_BUFFER_LIMIT code -- reflects proposed ACPI spec update
>>
>>Please try it out on a system near you!
> 
> 
> Tested on my Samsung P35 notebook:
> 
> Seems to work so far. I only tested S3 suspend/resume; my battery is
> unplugged right now.

I take that back. Adjusting display brightness is now at least 10x slower
than before. Normally, pressing the keys to change brightness resulted
in immediate action. Now, the machine needs 1 second and more to react.
Before anybody asks: I have ACPI debugging switched off since it became
unbearably slow, so that is not my problem.

Regards,
Carl-Daniel
-- 
http://www.hailfinger.org/


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  parent reply	other threads:[~2005-03-21 23:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-19  6:34 please test latest acpi patch Len Brown
2005-03-21 13:36 ` Jan Kasprzak
2005-03-21 17:47 ` Carl-Daniel Hailfinger
     [not found]   ` <423F08C5.3060405-hi6Y0CQ0nG0@public.gmane.org>
2005-03-21 23:04     ` Carl-Daniel Hailfinger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-22  2:42 Yu, Luming
2005-03-22  8:02 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=423F52EE.4000703@gmx.net \
    --to=c-d.hailfinger.devel.2005-hi6y0cq0ng0@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-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