From: egi <pfammatter-egi@swissonline.ch>
To: linux-scsi@vger.kernel.org
Subject: Re: LSIFC909 problem
Date: Tue, 23 Oct 2007 19:31:26 +0200 [thread overview]
Message-ID: <fflb5f$ik6$1@ger.gmane.org> (raw)
In-Reply-To: <20071022164255.GC27248@parisc-linux.org>
Matthew Wilcox wrote:
> On Mon, Oct 22, 2007 at 10:33:41AM -0600, Moore, Eric wrote:
>> On Monday, October 22, 2007 10:18 AM, Matthew Wilcox wrote:
>>> Sounds like we need a new driver written to support the FC909 then.
>>> Unless we could pretend the FC909 is a parallel scsi card or something
>>> ... that wasn't quite clear from Michael's mail.
>>>
>> ok, are you suggesting for FC909 we call scsi_scan_host, else chips we
>> "hook into transport layer"?
>
> Yes. That reminds me, I need to convert fusion to the parallel scanning
> regime. I haven't forgotten our conversation at OLS2006.
>
>> The way I understood from Stephen Shirron, is the FC909 is using mpi
>> version 1.0, and all the other FC cards are on mpi version 1.2 or 1.5.
>> The mpi defines the interface between driver and firmware. The older
>> mpi version 1.0 is missing feature needed for the FC transport to work.
>
> That sounds plausible.
>
Thank you a lot for your infos. You writes that this card isn't any more
supported.
What's suspectfor me is why the fc909 is still listed on the Kconfig as
supported controller. I request this lsi909 card 8 mnoth ago. This was a
new card and the seller told me that this card was often sold and he had
also a lot of this cards allways in his stock. (maybe i' m the first
user of this card which shuold run with linux ;-) ..
You wrote any changes which must be done to support this card with the
current kernel. Is this a lot of work for you?
prev parent reply other threads:[~2007-10-23 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 7:33 LSIFC909 problem egi
2007-10-22 16:11 ` Moore, Eric
2007-10-22 16:18 ` Matthew Wilcox
2007-10-22 16:33 ` Moore, Eric
2007-10-22 16:42 ` Matthew Wilcox
2007-10-23 17:31 ` egi [this message]
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='fflb5f$ik6$1@ger.gmane.org' \
--to=pfammatter-egi@swissonline.ch \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.