public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan McDowell <noodles@earth.li>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Status of HPT372A driver?
Date: Tue, 18 Jul 2006 13:02:17 +0100	[thread overview]
Message-ID: <20060718120217.GF1485@earth.li> (raw)
In-Reply-To: <44BBDFBE.10800@ru.mvista.com>

On Mon, Jul 17, 2006 at 11:06:38PM +0400, Sergei Shtylyov wrote:
> >I've had a try with libata and Alan Cox's 2.6.17-ide1 patch (I'd
> >previously tried this and had issues, which turned out to be a faulty
> >drive I think). This seems to get better results (sda is the same drive
> >as was hde earlier):
> 
>    I wouldn't be so sure about the faulty drive. ;-)

No, the drive was definitely faulty - I ran the Western Digital test
tool on it and it indicated the drive should be returned for a
replacement.
 
>    No "HW reset results" -- SATA drives don't have valid word 93 as it 
>    seems, and so the eighty_ninty_three() returns 0 meaning that the device 
> reports 40c PATA cable.
>    I think you need to try this 2.6.18-rc1 patch from Alan:
> 
> http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1a1276e7b6cba549553285f74e87f702bfff6fac

Result! I've applied that patch and now get UDMA(133) reported and
speeds of 45MB/s+, so much better. Thanks!

J.

-- 
                                            jid: noodles@jabber.earth.li
"Then P=NP, and the world is a happier
                                            place." -- Steve Cameron
in a complexity tute.

      reply	other threads:[~2006-07-18 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17 14:27 Status of HPT372A driver? Jonathan McDowell
2006-07-17 17:22 ` Sergei Shtylyov
2006-07-17 18:26   ` Jonathan McDowell
2006-07-17 19:06     ` Sergei Shtylyov
2006-07-18 12:02       ` Jonathan McDowell [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=20060718120217.GF1485@earth.li \
    --to=noodles@earth.li \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    /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