From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata.h: Don't do a SATA check for 40wire_relaxed
Date: Fri, 23 Nov 2007 20:23:39 -0500 [thread overview]
Message-ID: <47477D1B.9050305@garzik.org> (raw)
In-Reply-To: <20071119152434.45363e5d@the-village.bc.nu>
Alan Cox wrote:
> Without the valid bits at least one set of TSScorp drives report 0 in
> word 93 for PATA 40 wire, which we (and the specs) say actually means
> SATA. (The SATA version seems to report 80 wire...)
>
> Signed-off-by: Alan Cox <alan@redhat.com>
SATA version on what controller? Have you verified where the bridge is,
if it's not reporting word93==0 ?
Is this for 2.6.24-rc, considering that we are late in -rc?
Jeff
next prev parent reply other threads:[~2007-11-24 1:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 15:24 [PATCH] ata.h: Don't do a SATA check for 40wire_relaxed Alan Cox
2007-11-24 1:23 ` Jeff Garzik [this message]
2007-11-24 13:46 ` Alan Cox
2007-12-04 19:20 ` Jeff Garzik
2007-12-04 20:29 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2007-12-08 14:55 Peter Missel
2007-12-15 17:35 Peter Missel
2007-12-15 17:49 ` Alan Cox
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=47477D1B.9050305@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).