From: Jeff Garzik <jgarzik@pobox.com>
To: Greg Stark <gsstark@mit.edu>
Cc: Adrian Bunk <bunk@stusta.de>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [SATA] libata-dev queue updated
Date: Sat, 4 Jun 2005 15:19:58 -0400 [thread overview]
Message-ID: <20050604191958.GA13111@havoc.gtf.org> (raw)
In-Reply-To: <87psv2j5mb.fsf@stark.xeocode.com>
On Sat, Jun 04, 2005 at 03:15:24PM -0400, Greg Stark wrote:
> So my question is, if I did tackle this riddle trail and figured out how to
> fetch the passthru branch against 2.6.12, what would it buy me? Would SMART
> just start working? Or would it just confuse the SMART tools until they're
> updated? Or would it just crash my machine?
SMART should just start working. It adds the ioctls that existing smartd
and hdparm already know about.
The two reasons why passthru is not upstream are:
* I need to make sure that it is 100% up-to-date for the latest ATA
passthru spec, which clarified some SCSI CDB and descriptor codes.
* There was at least one report of ATA passthru use causing a device
under load to start timing out, which could possibly indicate a driver
bug. I need to do a serious analysis and final review of the patch, to
make sure that it is plugged into the ATA host state machine at the
correct places.
Jeff
next prev parent reply other threads:[~2005-06-04 19:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 6:08 Jeff Garzik
2005-06-04 15:17 ` Greg Stark
2005-06-04 17:48 ` Jeff Garzik
2005-06-04 18:50 ` Adrian Bunk
2005-06-04 19:05 ` Jeff Garzik
2005-06-04 19:15 ` Greg Stark
2005-06-04 19:19 ` Jeff Garzik [this message]
2005-06-05 2:25 ` Greg Stark
2005-06-05 2:30 ` Jeff Garzik
2005-06-05 5:30 ` Greg Stark
2005-06-22 16:15 ` Mark Lord
2005-06-22 20:23 ` Jeff Garzik
2005-06-23 3:39 ` Mark Lord
2005-06-05 2:40 ` Drew Winstel
2005-06-05 2:58 ` Jim Crilly
2005-06-06 16:01 ` Mark Lord
2005-06-07 1:57 ` Greg Stark
2005-06-07 11:20 ` Brad Campbell
2005-06-08 8:33 ` Mark Lord
2005-06-07 13:15 ` Brad Campbell
2005-06-08 8:37 ` Mark Lord
2005-06-07 13:51 ` Greg Stark
2005-06-08 10:30 ` Mark Lord
2005-06-08 8:51 ` Mark Lord
2005-06-07 13:09 ` Domenico Andreoli
2005-06-07 17:53 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 7:00 Bene Martin
2005-03-10 5:40 Jeff Garzik
2005-03-29 9:12 ` kern.petr
2005-03-08 11:20 Jeff Garzik
[not found] <3Ds62-5AS-3@gated-at.bofh.it>
2005-03-02 20:34 ` Joerg Sommrey
2005-03-02 22:43 ` Jeff Garzik
2005-03-03 19:32 ` Joerg Sommrey
2005-03-04 4:09 ` Jeff Garzik
2005-03-04 6:37 ` Joerg Sommrey
2005-03-04 7:10 ` Jeff Garzik
2005-03-04 17:49 ` Joerg Sommrey
2005-03-04 18:07 ` Jeff Garzik
2005-03-04 20:33 ` Joerg Sommrey
2005-03-04 20:43 ` Jeff Garzik
2005-03-04 22:06 ` Joerg Sommrey
2005-03-04 22:32 ` Joerg Sommrey
2005-03-02 2:40 Jeff Garzik
2005-02-19 8:40 Jeff Garzik
2005-02-19 16:58 ` Andre Tomt
2005-02-19 17:09 ` Jeff Garzik
2005-02-13 20:33 Jeff Garzik
2004-10-27 6:52 Jeff Garzik
2004-10-27 6:53 ` Jeff Garzik
2004-10-27 22:53 ` Rob van Nieuwkerk
2004-10-27 23:03 ` Jeff Garzik
2004-10-15 8:04 Jeff Garzik
2004-10-15 17:15 ` Jeff Garzik
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=20050604191958.GA13111@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--cc=gsstark@mit.edu \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®