From: Thomas Renninger <trenn@suse.de>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "Moore, Robert" <robert.moore@intel.com>,
ak@linux.intel.com, lenb@kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Debug interface used for error message cleanups
Date: Fri, 1 Aug 2008 11:01:28 +0200 [thread overview]
Message-ID: <200808011101.29590.trenn@suse.de> (raw)
In-Reply-To: <1217554944.2969.166.camel@rzhang-dt>
On Friday 01 August 2008 03:42:24 Zhang Rui wrote:
> On Thu, 2008-07-31 at 17:59 +0800, Thomas Renninger wrote:
> > On Wednesday 30 July 2008 22:29:19 Moore, Robert wrote:
> > > I'm going to go ahead and remove these from ACPICA.
> > >
> > > We added an "obsolete" warning in the header file some time ago, and
> >
> > I
> >
> > > think the time has come to remove them, especially in light of these
> > > patches to Linux.
> >
> > Great thanks.
> > If you are at that, do you think it makes sense to intruduce a GPE
> > bit?
> > Just leaving it unused for now?
> >
> >
> > I didn't play with these much yet, Rui, do you think this makes sense?
> > The
> > fact there were several sever problems recently and GPEs possibly
> > must get debugged by people writting other device drivers who do not
> > know
> > and do not want to know about the output of the other debug flags I
> > thought
> > this could make sense.
>
> We used to get the GPE debug info by doing this,
> set debug_layer=0x44, debug_level=0x8800001f
> We can get the content of GPE Block Register once a GPE is fired.
> and it's the same for PM1 Event Register and Fixed Events.
> Is this what you want?
Ahh yes:
ACPI_LV_INTERRUPTS 0x08000000
ACPI_LV_EVENTS 0x80000000
I think this is what I am looking for.
Thanks,
Thomas
next prev parent reply other threads:[~2008-08-01 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 20:22 Debug interface used for error message cleanups Thomas Renninger
2008-07-30 20:22 ` [PATCH 1/9] ACPI cm_sbs: Debug interface used for error message cleanup Thomas Renninger
2008-07-30 20:22 ` [PATCH 2/9] ACPI memhotplug: " Thomas Renninger
2008-07-30 20:22 ` [PATCH 3/9] ACPI processor: " Thomas Renninger
2008-07-30 20:22 ` [PATCH 4/9] ACPI video: " Thomas Renninger
2008-07-30 20:22 ` [PATCH 5/9] ACPI scan: " Thomas Renninger
2008-07-30 20:22 ` [PATCH 6/9] ACPI fan: " Thomas Renninger
2008-07-30 20:22 ` [PATCH 7/9] ACPI osl: " Thomas Renninger
2008-07-30 20:22 ` [PATCH 8/9] ACPI thermal: " Thomas Renninger
2008-07-30 20:22 ` [PATCH 9/9] ACPI system: " Thomas Renninger
2008-07-30 20:29 ` Debug interface used for error message cleanups Moore, Robert
2008-07-30 20:55 ` Andi Kleen
2008-07-31 9:59 ` Thomas Renninger
2008-07-31 21:42 ` Moore, Robert
2008-08-01 1:42 ` Zhang Rui
2008-08-01 9:01 ` Thomas Renninger [this message]
2008-08-01 15:45 ` Moore, Robert
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=200808011101.29590.trenn@suse.de \
--to=trenn@suse.de \
--cc=ak@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=rui.zhang@intel.com \
/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