From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Piotr Goczal <bilbo@mazurek.man.lodz.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Promise Fast Track SX6000 i2o driver.
Date: Sun, 22 Aug 2004 12:25:14 +0100 [thread overview]
Message-ID: <1093173914.24272.45.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0408211012500.2571@mazurek.man.lodz.pl>
On Sad, 2004-08-21 at 10:09, Piotr Goczal wrote:
> With old version of SX6000 firmware (Bios version 1.1.0 (Build 15),
> Firmware 77RM) driver's found controler but it's hanging durring
> initialisation.
It will pause during initialization with older firmware and it tends to
spew a few messages because Promise interpretation of the I2O spec is
somewhat different to other devices, as well as including some clear
mistakes
> With new version of firmware (Bios version 1.20.0.27) driver doesn't
> recognise hardware at all. The problem is: Promise's changed PCI_CLASS
> identifier from 0x0e00 (I2O controler) to 0x0104 (RAID bus controller).
> I've tried simply change PCI_CLASS number in source and recompile it but
> it doesn't work good (driver recognised hardware but hung whole machine!).
The new firmware isn't I2O any more. I've not found any public docs on
the newer firmware interface and since it was way slower than the 3ware
card I never looked.
Alan
next prev parent reply other threads:[~2004-08-22 12:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 9:09 PROBLEM: Promise Fast Track SX6000 i2o driver Piotr Goczal
2004-08-22 11:25 ` Alan Cox [this message]
2004-08-22 14:12 ` Piotr Goczal
2004-08-22 14:20 ` Alan Cox
2004-08-22 16:55 ` Piotr Goczal
2004-08-22 16:21 ` Alan Cox
2004-08-22 17:41 ` Piotr Goczal
2004-08-22 18:48 ` Alan Cox
2004-08-23 0:07 ` Matt Heler
[not found] ` <Pine.LNX.4.58.0408230832260.2571@mazurek.man.lodz.pl>
2004-08-23 11:44 ` Alan Cox
2004-09-09 10:39 ` Piotr Goczal
2004-11-12 9:05 ` Piotr Goczal
2004-12-05 11:03 ` Piotr Goczal
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=1093173914.24272.45.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bilbo@mazurek.man.lodz.pl \
--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