From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: hpt366 driver oops or panic with HighPoint RocketRAID 1520 SATA (HPT372N)
Date: Mon, 03 Apr 2006 20:58:17 +0400 [thread overview]
Message-ID: <44315429.5090602@ru.mvista.com> (raw)
In-Reply-To: <43750851.1080306@ru.mvista.com>
Hello.
Sergei Shtylylov wrote:
> Alan Cox wrote:
>> I've got the correct timing tables and PLL tune information for the 302N
>> now which appears to be very similar if not identical for these needs so
>> if someone wants to hack the old drivers/ide/pci driver a bit I can
>> provide reasonably accurate chip id and chip pll base information to
>> enable a fix.
> I'm currently working on the old driver to bring in the HPT371N
> support and fix HPT371 clock setup (and make the other chip's clock
> setups correct along the way). Unfortunately I can test only on 371N and
> 370A, the board with 371 soldered in has PCI contreoller fried.
The driver rewrite is almost complete (after being preempted several
times), I'm awaiting it to also be tested on HPT302. The changes are HUGE, the
patch is about 70 KB in size...
Meanwhile, I've noticed (just now :-) a bug in HPT372N clock turnaround
code (it accesses extra DMA ports relative to dma_base, not dma_master which
would make it do BAD things if called on a secondary channel) -- guess I
should post them in a separate patch?
WBR, Sergei
next prev parent reply other threads:[~2006-04-03 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <436FB350.6020309@inap.se>
2005-11-08 16:37 ` hpt366 driver oops or panic with HighPoint RocketRAID 1520 SATA (HPT372N) Alan Cox
2005-11-11 21:08 ` Sergei Shtylylov
2006-04-03 16:58 ` Sergei Shtylyov [this message]
2006-05-04 19:53 ` Sergei Shtylyov
2006-05-04 22:25 ` Alan Cox
2006-05-04 22:21 ` 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=44315429.5090602@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@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).