From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Bob Ham <rah@bash.sh>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: hpt374 sata (Highpoint Rocket 1540)
Date: Wed, 01 Aug 2007 22:19:44 +0400 [thread overview]
Message-ID: <46B0CEC0.60504@ru.mvista.com> (raw)
In-Reply-To: <1185988529.16340.5.camel@orchid.arb.net>
Bob Ham wrote:
>>>>>>>>>I've had a Highpoint Rocket 1540 (not "RocketRAID") SATA controller for
>>>>>>>>>a while now, using a proprietary binary driver from Highpoint in a linux
>>>>>>>>>2.4 kernel. The chipset is an hpt374. The hpt366 driver freezes on
>>>>>>>>>boot, as reported by others.
>>>>>>>> Can we see a bootlog please?
>>>>>>> ... and the output of 'lspci -v' too.
>>>> If possible, turn off that driver,
>>>>then post that output...
>>>This is the output of the boot using the pata_hpt37x driver:
>> Hrm... what I asked for was 'lspci -v' output. :-)
>>lspci gives:
>>00:0d.0 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)
>> Subsystem: Triones Technologies, Inc. Unknown device 0001
>> Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
>> I/O ports at efa0 [size=8]
>> I/O ports at ef9c [size=4]
>> I/O ports at ef90 [size=8]
>> I/O ports at ef98 [size=4]
>> I/O ports at ec00 [size=256]
>> Expansion ROM at fe700000 [disabled] [size=128K]
>> Capabilities: [60] Power Management version 2
>>
>>00:0d.1 RAID bus controller: Triones Technologies, Inc. HPT374 (rev 07)
>> Subsystem: Triones Technologies, Inc. Unknown device 0001
>> Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 16
>> I/O ports at eff0 [size=8]
>> I/O ports at efe4 [size=4]
>> I/O ports at efa8 [size=8]
>> I/O ports at efe0 [size=4]
>> I/O ports at ed00 [size=256]
>> Capabilities: [60] Power Management version 2
Too bad, this is the standard HPT subsystem ID of 0x0001... So, nothing
comes to my mind other than add a module parameter to hpt366.c to specify that
we're using the crippled SATA bridge... well, maybe it would also make sense
to scan the BIOS for the signatures...
WBR, Sergei
next prev parent reply other threads:[~2007-08-01 18:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 11:08 hpt374 sata (Highpoint Rocket 1540) Bob Ham
2007-07-31 12:23 ` Alan Cox
2007-07-31 20:12 ` Bob Ham
2007-07-31 13:29 ` Sergei Shtylyov
2007-07-31 15:35 ` Brad Campbell
2007-07-31 17:52 ` Sergei Shtylyov
2007-07-31 21:22 ` Bob Ham
2007-07-31 21:32 ` Bartlomiej Zolnierkiewicz
2007-07-31 22:06 ` Bob Ham
2007-08-01 13:40 ` Sergei Shtylyov
2007-08-01 15:52 ` Bob Ham
2007-08-01 15:58 ` Sergei Shtylyov
2007-08-01 17:15 ` Bob Ham
2007-08-01 18:19 ` Sergei Shtylyov [this message]
2007-08-01 22:43 ` Alan Cox
2007-08-02 12:41 ` Sergei Shtylyov
2007-08-02 13:12 ` Alan Cox
2007-08-01 21:03 ` Bob Ham
2007-08-01 21:08 ` Sergei Shtylyov
2007-08-01 22:42 ` Alan Cox
2007-08-05 18:10 ` Sergei Shtylyov
2007-08-01 21:07 ` Bartlomiej Zolnierkiewicz
2007-08-01 21:16 ` Sergei Shtylyov
2007-08-01 21:29 ` Bartlomiej Zolnierkiewicz
2007-08-01 16:14 ` Alan Cox
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=46B0CEC0.60504@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=rah@bash.sh \
/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).