From: grundler@dsl2.external.hp.com (Grant Grundler)
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] FC driver?
Date: Mon, 17 Mar 2003 09:14:45 -0700 [thread overview]
Message-ID: <20030317161445.GA31378@dsl2.external.hp.com> (raw)
In-Reply-To: <20030317111801.GF17073@lug-owl.de>
On Mon, Mar 17, 2003 at 12:18:01PM +0100, Jan-Benedict Glaw wrote:
> So your device is called "PCI_DEVICE_ID_HP_TACHYON".
Please don't ever call a TachLite (TL) devices "Tachyon".
Tachyon (5000) was the first FC chip made by HP (now Agilent)
and was a nightmare to program. TachLite (5100/5166)
had a simpler programming model and fewer bugs. TachLite XL2
chips (5200) use the same programming model.
> See, it's quite easy to see if a PCI card seems to be supported:-)
Yes, but sometimes it's easier to start with "lspci -n" output.
cpqfc code suggests it supports all Tachlite HBAs.
But it depends on GBIC/HBA configuration and HPUX folks haven't
been interested in making cpqfc work with their XL2 HBA.
Jes Sorensen/Martin Petersen did get older (5100/5166) TL HBAs
from HP working with cpqfc driver.
grant
next prev parent reply other threads:[~2003-03-17 16:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 11:05 [parisc-linux] FC driver? Joel Soete
2003-03-17 11:18 ` Jan-Benedict Glaw
2003-03-17 13:58 ` Joel Soete
2003-03-17 15:52 ` Randolph Chung
2003-03-17 16:21 ` Grant Grundler
2003-03-17 16:34 ` Jan-Benedict Glaw
2003-03-18 9:16 ` Jan-Benedict Glaw
2003-03-17 16:14 ` Grant Grundler [this message]
2003-03-17 16:22 ` Ryan Bradetich
2003-03-17 16:36 ` Martin K. Petersen
2003-03-17 16:38 ` Grant Grundler
2003-03-18 15:18 ` Joel Soete
2003-03-21 15:24 ` Joel Soete
2003-03-22 21:58 ` Joel Soete
2003-03-23 6:24 ` Grant Grundler
2003-03-24 7:22 ` Joel Soete
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=20030317161445.GA31378@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=jbglaw@lug-owl.de \
--cc=parisc-linux@lists.parisc-linux.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.