From: Jeff Garzik <jeff@garzik.org>
To: Fajun Chen <fajunchen@gmail.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Libata Sil3124 hybrid drive failure
Date: Thu, 02 Aug 2007 15:27:42 -0400 [thread overview]
Message-ID: <46B2302E.3090704@garzik.org> (raw)
In-Reply-To: <8202f4270708021052y166eddb9mbb8c46e63308b8dc@mail.gmail.com>
Fajun Chen wrote:
> Does anyone know if libata supports hybrid drive on Sil3124? I tried
> to play with Seagate hybrid drive and got protocol mismatch error when
> adding LBAs to pinned set or querying pinned set? Sil24 driver code
> does not set Protocol Override field in PRB, just wonder if we need to
> set protocol explicitly to get this work because the controller may
> not decode the protocol correctly for nv cache commands.
Yes, that's entirely possible for new commands...
Jeff
prev parent reply other threads:[~2007-08-02 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 17:52 Libata Sil3124 hybrid drive failure Fajun Chen
2007-08-02 19:27 ` Jeff Garzik [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=46B2302E.3090704@garzik.org \
--to=jeff@garzik.org \
--cc=fajunchen@gmail.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).