From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
To: ide <linux-ide@vger.kernel.org>
Subject: [RFC 0/5] ACPI methods for SATA
Date: Wed, 23 Nov 2005 15:40:55 -0800 [thread overview]
Message-ID: <20051123154055.6ab5cab2.randy_d_dunlap@linux.intel.com> (raw)
This is my current work-in-progress for comments on
ACPI methods for SATA (and PATA later on, unless a patch
from Shaohua Li on the mailing list handles PATA).
Quick status:
Working:
- find devices in namespace
- evaluate _SDD
- evaluate _GTF
- simulate writing taskfile to device
TODO:
- write taskfile to device in a generic, non-controller-specific way
- add more usage events for _SDD and _GTF (SATA) per
ACPI 3.0 spec, section 9.9.3.3, page 288.
---
~Randy
next reply other threads:[~2005-11-23 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 23:40 Randy Dunlap [this message]
2005-11-23 23:48 ` [RFC 1/5] ata_acpi: Makefile + Kconfig Randy Dunlap
2005-11-23 23:51 ` [RFC 2/5] ata_acpi: libata.h fields Randy Dunlap
2005-11-24 0:38 ` Edward Falk
2005-11-28 5:03 ` Randy.Dunlap
2005-11-23 23:52 ` [RFC 3/5] ata_acpi: invoke ACPI support functions Randy Dunlap
2005-11-23 23:53 ` [RFC 4/5] ata_acpi: kernel-doc Randy Dunlap
2005-11-23 23:54 ` [RFC 5/5] ata_acpi: add ACPI support functions Randy Dunlap
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=20051123154055.6ab5cab2.randy_d_dunlap@linux.intel.com \
--to=randy_d_dunlap@linux.intel.com \
--cc=linux-ide@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).