From: Len Brown <lenb@kernel.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Ozan Çağlayan" <ozan@pardus.org.tr>, linux-acpi@vger.kernel.org
Subject: Re: Suggested readings about ACPI
Date: Sun, 16 Jan 2011 23:46:25 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.02.1101162344030.21642@x980> (raw)
In-Reply-To: <20110117020630.GA14058@srcf.ucam.org>
> > I want to get my hands dirty about ACPI and ACPI on Linux. I started
> > reading the spec but I don't know how far can I progress with it :)
>
> Try starting with version 1.0 of the spec - the core functionality
> hasn't changed much, and it's *much* shorter than the current version.
Good suggestion.
> > I also found some driver examples for ACPI and WMI on LWN. There's Colin
> > Ian King's blog which seems very rich in terms of debugging.
> >
> > Any other suggestions, readings, guidings, do's and dont-do's would be
> > very much appreciated.
http://www.acpica.org/
http://lesswatts.org/projects/acpi/
each has a couple of references that may be useful.
cheers,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2011-01-17 4:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-16 21:46 Suggested readings about ACPI Ozan Çağlayan
2011-01-17 2:06 ` Matthew Garrett
2011-01-17 4:46 ` Len Brown [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=alpine.LFD.2.02.1101162344030.21642@x980 \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=ozan@pardus.org.tr \
/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