From: Brett Russ <russb@emc.com>
To: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata-2.6: verify cmd bug fixes/support
Date: Wed, 02 Feb 2005 08:19:27 -0500 [thread overview]
Message-ID: <4200D35F.5030200@emc.com> (raw)
In-Reply-To: <42004A0C.70809@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
Below is a resend of a patch which gets the read verify command working.
I moved the patch to the libata-2.6 tree since that seems to be where
Albert's patch ended up, so let's keep them together. Sending as an
attachment to avoid mailer interference.
Signed-off-by: Brett Russ <russb@emc.com>
[-- Attachment #2: libata-2.6.10-rc2-verify.diff --]
[-- Type: text/x-patch, Size: 933 bytes --]
===== drivers/scsi/libata-scsi.c 1.63 vs edited =====
--- 1.63/drivers/scsi/libata-scsi.c 2005-02-01 22:24:53 -05:00
+++ edited/drivers/scsi/libata-scsi.c 2005-02-02 08:03:50 -05:00
@@ -488,13 +488,18 @@
}
if (lba48) {
+ tf->command = ATA_CMD_VERIFY_EXT;
+
tf->hob_nsect = (n_sect >> 8) & 0xff;
tf->hob_lbah = (sect >> 40) & 0xff;
tf->hob_lbam = (sect >> 32) & 0xff;
tf->hob_lbal = (sect >> 24) & 0xff;
- } else
+ } else {
+ tf->command = ATA_CMD_VERIFY;
+
tf->device |= (sect >> 24) & 0xf;
+ }
tf->nsect = n_sect & 0xff;
===== include/linux/ata.h 1.21 vs edited =====
--- 1.21/include/linux/ata.h 2004-11-06 13:44:16 -05:00
+++ edited/include/linux/ata.h 2005-02-02 08:15:49 -05:00
@@ -123,6 +123,8 @@
ATA_CMD_PIO_WRITE_EXT = 0x34,
ATA_CMD_SET_FEATURES = 0xEF,
ATA_CMD_PACKET = 0xA0,
+ ATA_CMD_VERIFY = 0x40,
+ ATA_CMD_VERIFY_EXT = 0x42,
/* SETFEATURES stuff */
SETFEATURES_XFER = 0x03,
next prev parent reply other threads:[~2005-02-02 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 0:34 [PATCH] libata-dev-2.6: verify cmd bug fixes/support Brett Russ
2005-02-02 3:33 ` Jeff Garzik
2005-02-02 13:19 ` Brett Russ [this message]
2005-02-06 1:31 ` [PATCH] libata-2.6: " 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=4200D35F.5030200@emc.com \
--to=russb@emc.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).