public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Wahlbrink <linux.wali-Mmb7MZpHnFY@public.gmane.org>
To: bperkins-ooduxAEi7gVg9hUCZPvPmw@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: IBM Thinkpad R32 and ACPI
Date: Wed, 16 Apr 2003 12:58:53 +0200	[thread overview]
Message-ID: <20030416125853.625072c6.linux.wali@gmx.de> (raw)
In-Reply-To: <200304151747.h3FHlUK07346-7GtV0IYKK74tA4QZiFxQkx2eb7JE58TQ@public.gmane.org>

On Tue, 15 Apr 2003 13:47:30 -0400
bperkins-ooduxAEi7gVg9hUCZPvPmw@public.gmane.org wrote:

> Michael Wahlbrink <linux.wali-Mmb7MZpHnFY@public.gmane.org> writes:
> 
> 
> > Hi Brian, Hmm, it have the same effect like commenting out these "if
> > (ec_ecdt && ec_ecdt->uid == uid) {...}" block in acpi_ec_add() of
> > ec.c. No errormessages anymore but also no events from the
> > powerbutton...  I'll no try for testing a kernel with both hacks ;-)
> 
> Nothing interesting will happen.  The ec_add is a hack, my fix is (at
> least closer to) a real fix.  If you comment it out the "fixed" code
> won't even get called.
> 
> > ...  And I'll give 2.5.66 a shot to see if it makes a difference
> > ....  thanks for the quick response regards micha
> 
>  I think I noticed the same problem, but I guess I didn't really care.
> I'm not sure it's worth the effort until the sleep functions are
> fixed.  You might be able to get somewhere if you looked at the DSDT
> table, I dunno.  It may be possible that the power button isn't
> controlled by acpi.
Hmmm, it seems that it is also controlled by acpi, because in a kernel without your fix the Powerbutton produces also these errormessages like the volume keys and all fn+Fx (only fn+F4) always gives the right action... So as I see the things in the moment, I prevent with the fix from giving the errors, but I'm not get any more usable events in /proc/acpi/events  cause fn+F4 and the LID-switch worked also before. The only difference in usability is that I can now use fn+F7 again to switch between the displays (internal/external).

> Good luck!
It seem that I'll need it for acpi on that Laptop....

Thanks to all who work on ACPI-support for linux

regards
micha


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      parent reply	other threads:[~2003-04-16 10:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-12 15:33 IBM Thinkpad R32 and ACPI Michael Wahlbrink
     [not found] ` <20030412173357.1e4ea127.linux.wali-Mmb7MZpHnFY@public.gmane.org>
2003-04-12 18:12   ` bperkins-ooduxAEi7gVg9hUCZPvPmw
     [not found]     ` <200304121812.h3CIC6g18608-7GtV0IYKK74tA4QZiFxQkx2eb7JE58TQ@public.gmane.org>
2003-04-13  4:31       ` Lu Tong
2003-04-15  9:05       ` Michael Wahlbrink
     [not found]         ` <200304151747.h3FHlUK07346@throb.netspace.org>
     [not found]           ` <200304151747.h3FHlUK07346-7GtV0IYKK74tA4QZiFxQkx2eb7JE58TQ@public.gmane.org>
2003-04-16 10:58             ` Michael Wahlbrink [this message]

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=20030416125853.625072c6.linux.wali@gmx.de \
    --to=linux.wali-mmb7mzphnfy@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=bperkins-ooduxAEi7gVg9hUCZPvPmw@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