linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Echtler <floe@butterbrot.org>
To: linux-acpi@vger.kernel.org
Subject: Looking for some pointers on WMI/EC access
Date: Sat, 17 Apr 2010 17:37:33 +0200	[thread overview]
Message-ID: <1271518653.4549.186.camel@flunder> (raw)

Hello everyone,

I've just bought an Ideapad S10-3t, and most features including ACPI
work fine. However, since neither thinkpad-acpi nor lenovo-sl-laptop
support this device, I've been looking around for some hints on how to
access the embedded controller in order to get the hotkeys working. I'll
post what I've found so far and hope that somebody could give me some
hints as to how to proceed.

First, I've dumped the DSDT and browsed through it. I've found a _WDT
section, and wmidump shows:

ABBC0F20-8EA1-11D1-00A0-C90629100000:
	object_id: �
	notify_id: 80
	reserved: 00
	instance_count: 1
	flags: 0x8 ACPI_WMI_EVENT 
ABBC0F40-8EA1-11D1-00A0-C90629100000:
	object_id: IO
	notify_id: 49
	reserved: 4F
	instance_count: 1
	flags: 0x1 ACPI_WMI_EXPENSIVE 
05901221-D566-11D1-B2F0-00A0C9062910:
	object_id: AE
	notify_id: 41
	reserved: 45
	instance_count: 1
	flags: 0

As this laptop also runs some kind of Splashtop instant-on Linux called
Lenovo Quickstart, I've decided to extract the initrd from its kernel
(*) and browse through the modules. Interestingly, I've found a
lenovo_ec.ko: strings shows that it accesses some DSDT elements which
are present on the S10-3t. Would it make sense to disassemble this?

Yours, Florian

(*) The Splashtop kernel is obfuscated in the most stupid way
imaginable: XOR "encryption" with 'QWER' as key. Need I say more?


--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2010-04-17 15:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 15:37 Florian Echtler [this message]
2010-04-18 19:21 ` Looking for some pointers on WMI/EC access 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
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=1271518653.4549.186.camel@flunder \
    --to=floe@butterbrot.org \
    --cc=linux-acpi@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).