From: Florian Echtler <floe@butterbrot.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Corentin Chary <corentin.chary@gmail.com>,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: Looking for some pointers on WMI/EC access
Date: Fri, 23 Apr 2010 13:24:30 +0200 [thread overview]
Message-ID: <1272021870.29664.109.camel@pancake.fritz.box> (raw)
In-Reply-To: <20100422140518.GA32558@srcf.ucam.org>
Am Donnerstag, den 22.04.2010, 15:05 +0100 schrieb Matthew Garrett:
> Hm. Yeah, that looks pretty messed up. I think you'd be justified in
> just changing that entry yourself, to be honest, and then see if that
> makes things behave more usefully.
You mean, change the initial value for ERQ0 in the DSDT and load that
through the kernel? I'll try that. I'll also try a BIOS update and see
if there's a little more sense in the DSDT afterwards..
Florian
--
0666 - Filemode of the Beast
next prev parent reply other threads:[~2010-04-23 11:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 15:37 Looking for some pointers on WMI/EC access Florian Echtler
2010-04-18 19:21 ` Corentin Chary
2010-04-19 14:25 ` Florian Echtler
2010-04-19 15:46 ` Corentin Chary
[not found] ` <1271746353.16585.9.camel@flunder>
2010-04-20 7:21 ` Corentin Chary
2010-04-20 7:30 ` Corentin Chary
2010-04-20 11:21 ` Florian Echtler
2010-04-20 12:09 ` Corentin Chary
2010-04-21 12:46 ` Florian Echtler
2010-04-21 13:33 ` Matthew Garrett
2010-04-21 14:30 ` Florian Echtler
2010-04-21 14:32 ` Matthew Garrett
2010-04-22 8:21 ` Florian Echtler
2010-04-22 13:36 ` Matthew Garrett
[not found] ` <1271944219.29664.42.camel@pancake.fritz.box>
2010-04-22 13:53 ` Matthew Garrett
2010-04-22 14:05 ` Matthew Garrett
2010-04-23 11:24 ` Florian Echtler [this message]
2010-04-23 17:47 ` Matthew Garrett
2010-04-22 14:33 ` Corentin Chary
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=1272021870.29664.109.camel@pancake.fritz.box \
--to=floe@butterbrot.org \
--cc=corentin.chary@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).