From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Geller Sandor <wildy@petra.hos.u-szeged.hu>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: HPT374 IDE problem with 2.6.21.* kernels
Date: Tue, 05 Jun 2007 18:14:46 +0400 [thread overview]
Message-ID: <46656FD6.6030305@ru.mvista.com> (raw)
In-Reply-To: <46655AEA.4020906@ru.mvista.com>
Hello, I wrote:
>> I felt inspired by this explanation (thanks!) and took a look at
>> hpt374-opensource-v2.10 vendor driver. Here is something interesting:
>> glbdata.c:
>> ...
>> #ifdef CLOCK_66MHZ
>> ULONG setting370_66[] = {
>> 0xd029d5e, 0xd029d26, 0xc829ca6, 0xc829c84, 0xc829c62,
>> 0x2c829d2c, 0x2c829c66, 0x2c829c62,
>> 0x1c829c62, 0x1c9a9c62, 0x1c929c62, 0x1c8e9c62, 0x1c8a9c62,
>> 0x1c8a9c62/*0x1cae9c62*/, 0x1c869c62, 0x1c869c62,
>> };
>> ...
>> hpt366.c:
>> ...
>> static u32 sixty_six_base_hpt37x[] = {
>> /* XFER_UDMA_6 */ 0x1c869c62,
>> /* XFER_UDMA_5 */ 0x1cae9c62, /* 0x1c8a9c62 */
>> ...
>> So we are using Dual ATA Clock for UDMA5 whereas vendor driver doesn't
> This is so in all other HPT drivers (and HPT371N datasheet has the
> same figures -- this chip is the only one supporting UDMA6 and having
> the default DPLL clock > 50 MHz).
What I meant to say was the only one I have a datasheet for. :-)
MBR, Sergei
next prev parent reply other threads:[~2007-06-05 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.62.0705301112170.1260@petra.hos.u-szeged.hu>
2007-06-01 20:46 ` HPT374 IDE problem with 2.6.21.* kernels Andrew Morton
2007-06-01 20:53 ` Sergei Shtylyov
2007-06-01 21:13 ` Geller Sandor
2007-06-01 21:26 ` Sergei Shtylyov
2007-06-01 22:41 ` Geller Sandor
2007-06-02 23:38 ` Bartlomiej Zolnierkiewicz
2007-06-03 10:37 ` Geller Sandor
2007-06-03 17:36 ` Sergei Shtylyov
2007-06-05 1:00 ` Bartlomiej Zolnierkiewicz
2007-06-05 12:45 ` Sergei Shtylyov
2007-06-05 14:14 ` Sergei Shtylyov [this message]
2007-06-08 12:33 ` Bartlomiej Zolnierkiewicz
2007-06-09 10:13 ` Sergei Shtylyov
2007-06-05 20:08 ` Sergei Shtylyov
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=46656FD6.6030305@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=akpm@linux-foundation.org \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wildy@petra.hos.u-szeged.hu \
/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).