public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: Jim Summers <jsummers-5f/76mLIbwCHXe+LvDLADg@public.gmane.org>
Cc: Listacpi <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Learning ACPI
Date: Sat, 29 Jan 2005 17:13:34 +0100	[thread overview]
Message-ID: <20050129161334.GA28055@hell.org.pl> (raw)
In-Reply-To: <41FA9F93.4090105-5f/76mLIbwCHXe+LvDLADg@public.gmane.org>

Thus wrote Jim Summers:
> I guess I am not understanding how, if the acpid is correctly monitoring 
> the lid state then why would it not fire the events/actions?  I can 
> porvide more info, dmesg output etc...

Basically, the lid stat is polled, while the events are interrupt driven.
For the record, could you try with an older ( <= 2.6.7) kernel? There seems
to be an issue in handling EC interrupts in recent kernels, it might be
that.
Best regards,

-- 
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

  parent reply	other threads:[~2005-01-29 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 20:24 Learning ACPI Jim Summers
     [not found] ` <41FA9F93.4090105-5f/76mLIbwCHXe+LvDLADg@public.gmane.org>
2005-01-29 16:13   ` Karol Kozimor [this message]
     [not found]     ` <20050129161334.GA28055-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2005-01-31 14:17       ` Jim Summers

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=20050129161334.GA28055@hell.org.pl \
    --to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=jsummers-5f/76mLIbwCHXe+LvDLADg@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