From: Pete Zaitcev <zaitcev@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: socal
Date: Wed, 31 Dec 2003 23:35:02 +0000 [thread overview]
Message-ID: <20031231233502.GA2051@devserv.devel.redhat.com> (raw)
In-Reply-To: <200312311429.26841.awirtz@novapointe.com>
On Wed, Dec 31, 2003 at 03:19:03PM -0800, Aaron Wirtz wrote:
> On Wednesday 31 December 2003 15:07, C.Newport wrote:
> >
> > Have you tried checking the firmware Fcode ?.
> > http://www.splack.org/fibrechan.html has the procedure for the soc
> > cards, the socal stuff is very similar.
>
> Given that the Solaris driver (and ucode) work with it under Solaris 9, I
> don't think the fcode version is currently an issue. One thing I had
> considered was that if I have to use an older ucode version, I may have to
> roll back the fcode to match.
This just makes no sense. FCode carries its own ucode,
which has nothing to do with the one a driver carries.
For one thing, FCode always carries a debugging ucode,
which tops at about 1000 IOPS. A driver carries a normal
microcode, which reaches 5500 IOPS with small blocks,
17000 IOPS with null ops (for IP-over-SCSI, for instance).
They are different and do not have to match, even their
ABI may be slightly different.
-- Pete
next prev parent reply other threads:[~2003-12-31 23:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 22:29 socal Aaron Wirtz
2003-12-31 23:07 ` socal C.Newport
2003-12-31 23:18 ` socal Keith M Wesolowski
2003-12-31 23:19 ` socal Aaron Wirtz
2003-12-31 23:26 ` socal Keith M Wesolowski
2003-12-31 23:35 ` Pete Zaitcev [this message]
2003-12-31 23:43 ` socal Aaron Wirtz
2003-12-31 23:43 ` socal Pete Zaitcev
2003-12-31 23:49 ` socal Aaron Wirtz
2003-12-31 23:57 ` socal Aaron Wirtz
2004-01-01 0:54 ` socal C.Newport
2004-01-01 1:26 ` socal C.Newport
2004-01-01 1:34 ` socal Aaron Wirtz
2004-01-01 2:06 ` socal C.Newport
2004-01-01 2:41 ` socal Pete Zaitcev
2004-01-01 2:57 ` socal C.Newport
2004-01-01 3:10 ` socal Aaron Wirtz
2004-01-06 3:06 ` socal Aaron Wirtz
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=20031231233502.GA2051@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=sparclinux@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.