From: Matthew Wilcox <matthew@wil.cx>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: egi <pfammatter-egi@swissonline.ch>,
linux-scsi@vger.kernel.org, mdr@sgi.com, "Shirron,
Stephen" <Stephen.Shirron@lsi.com>
Subject: Re: LSIFC909 problem
Date: Mon, 22 Oct 2007 10:42:55 -0600 [thread overview]
Message-ID: <20071022164255.GC27248@parisc-linux.org> (raw)
In-Reply-To: <664A4EBB07F29743873A87CF62C26D70A87BF1@NAMAIL4.ad.lsil.com>
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.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-10-22 16:42 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 [this message]
2007-10-23 17:31 ` egi
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=20071022164255.GC27248@parisc-linux.org \
--to=matthew@wil.cx \
--cc=Eric.Moore@lsi.com \
--cc=Stephen.Shirron@lsi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdr@sgi.com \
--cc=pfammatter-egi@swissonline.ch \
/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.