From: Jeff Garzik <jgarzik@pobox.com>
To: "zhao, forrest" <forrest.zhao@intel.com>
Cc: htejun@gmail.com, linux-ide@vger.kernel.org,
randy_dunlap <rdunlap@xenotime.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Another project for you... :)
Date: Thu, 08 Jun 2006 23:11:50 -0400 [thread overview]
Message-ID: <4488E6F6.10306@pobox.com> (raw)
In-Reply-To: <1149820043.5721.7.camel@forrest26.sh.intel.com>
Forrest,
BTW, if you are looking for useful libata projects, it would really be
nice to resurrect Randy Dunlap's SATA ACPI patches, update those for the
current libata-dev.git#upstream, and get those in.
libata needs to execute the SATA taskfiles passed to us from ACPI BIOS
tables, in order to properly set up the hard drive in a way the user
expects (hard drive password, acoustic settings, etc.). There should be
a module option that allows the user to skip this step, and preserve
current behavior.
Also, a feature Alan requests on occasion: Call the ATA "set max"
command to fully address the hard drive, including HPA. The Linux
standard is to export the raw hardware directly, making 100% of the
hardware capability available to the user (and, in this case,
Linux-based BIOS and recovery tools).
Jeff
next prev parent reply other threads:[~2006-06-09 3:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 7:30 [RFC] AHCI Command Completion Coalescing(CCC) proposal zhao, forrest
2006-06-08 15:01 ` Jeff Garzik
2006-06-09 2:27 ` zhao, forrest
2006-06-09 3:11 ` Jeff Garzik [this message]
2006-06-09 3:13 ` Another project for you... :) zhao, forrest
2006-06-09 22:29 ` Greg Freemyer
2006-06-09 23:44 ` Alan Cox
2006-06-09 3:43 ` [RFC] ATA host-protected area (HPA) device mapper? Jeff Garzik
2006-06-09 4:51 ` Matthew Frost
2006-06-14 8:01 ` Another project for you... :) zhao, forrest
2006-06-14 15:19 ` Randy.Dunlap
2006-06-15 7:59 ` zhao, forrest
2006-06-15 11:47 ` Jeff Garzik
2006-06-09 3:30 ` [RFC] AHCI Command Completion Coalescing(CCC) proposal Jeff Garzik
2006-06-09 3:39 ` zhao, forrest
2006-06-09 3:43 ` Tejun Heo
2006-06-09 3:47 ` Tejun Heo
2006-06-09 3:51 ` zhao, forrest
2006-06-09 4:12 ` Jeff Garzik
2006-06-09 5:24 ` Tejun Heo
2006-06-09 11:49 ` Jens Axboe
2006-06-09 3:53 ` Jeff Garzik
2006-06-09 3:52 ` Jeff Garzik
2006-06-09 11:49 ` Jens Axboe
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=4488E6F6.10306@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=forrest.zhao@intel.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.