From: Moritz Heiber <moe@lunar-linux.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Issues with AHCI and SATAII using JMD360
Date: Sun, 7 May 2006 16:52:40 +0200 [thread overview]
Message-ID: <20060507165240.2c949d17.moe@lunar-linux.org> (raw)
In-Reply-To: <445DF4EF.3080509@gmail.com>
On Sun, 07 May 2006 22:23:59 +0900
Tejun Heo <htejun@gmail.com> wrote:
> The digit in the middle is the SPD limit and 0 means no limit.
> Hmm... wait, this is a hitachi disk. Have you tried the feature
> tool? Hitachi limits the spd of the harddrive tso 1.5 gbps, probably
> for compatibility reasons, and allows users to enable it with the
> feature tool.
>
> http://www.hitachigst.com/hdd/support/download.htm#FeatureTool
That did it. Thank you very much Tejun. I promise I'll be looking for
such a tool next time before I bother any of the kernel related
mailinglists. My Hitachi is now officially running at 3.0Gbps .. and I
even managed to enable some of the other features (Accustic Management
and Power Management).
As a sidenote: Hitachi also provides bootable CD images. Very
convenient!
> > Given your patch though .. your git-based code looks much simpler. I
> > wonder if that is a good or a bad thing and wether I should try a
> > more recent kernel .. (?)
>
> The patch was pulled from libata devel tree. I was being lazy again
> and didn't test it on 2.6.16.14. :p However, I can assure you
> libata doesn't play much role in PHY spd configuration.
Nevermind here, I'm a long term C lover .. so it wasn't all that
complicated to adjust the patch. Besides, you've been very kind in
providing a patch at least .. since otherwise I'd have to dig one up
myself (and I am lazy as well ;-).
Thanks again.
Regards,
Moritz
next prev parent reply other threads:[~2006-05-07 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 2:37 Issues with AHCI and SATAII using JMD360 Moritz Heiber
2006-05-07 2:59 ` Tejun Heo
2006-05-07 12:04 ` Moritz Heiber
2006-05-07 12:17 ` Mogens Valentin
2006-05-07 12:20 ` Tejun Heo
2006-05-07 12:19 ` Tejun Heo
2006-05-07 13:10 ` Moritz Heiber
2006-05-07 13:23 ` Tejun Heo
2006-05-07 14:52 ` Moritz Heiber [this message]
2006-05-07 12:14 ` Mogens Valentin
2006-05-07 15:02 ` Moritz Heiber
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=20060507165240.2c949d17.moe@lunar-linux.org \
--to=moe@lunar-linux.org \
--cc=htejun@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