From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Johan Palmqvist <johan.palmqvist@inap.se>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: hpt366 driver oops or panic with HighPoint RocketRAID 1520 SATA (HPT372N)
Date: Tue, 08 Nov 2005 16:37:56 +0000 [thread overview]
Message-ID: <1131467876.25192.51.camel@localhost.localdomain> (raw)
In-Reply-To: <436FB350.6020309@inap.se>
On Llu, 2005-11-07 at 21:04 +0100, Johan Palmqvist wrote:
> When used with a HighPoint RocketRAID 1520 SATA (HPT372N) the hpt366
> driver, compiled as a module, oops'es on loading. If the driver is
> compiled into the kernel it causes a kernel panic on boot while
> detecting the card. Kernels tested: 2.6.13.2, 2.6.13.4 and 2.6.14.
> Please CC any answers to me since I'm not on the list.
I'm working on this with the new libata drivers. The list of what is
broken in the old driver for 372N/302N is rather large as they are
actually very different to the other chips.
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.
PS: Anyone got a 371N (specifically 371N) can send me the pci id and
rev.
next parent reply other threads:[~2005-11-08 16:37 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 ` Alan Cox [this message]
2005-11-11 21:08 ` hpt366 driver oops or panic with HighPoint RocketRAID 1520 SATA (HPT372N) Sergei Shtylylov
2006-04-03 16:58 ` Sergei Shtylyov
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=1131467876.25192.51.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=johan.palmqvist@inap.se \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).