From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "Moore, Eric Dean" <Emoore@lsil.com>,
linux-scsi@vger.kernel.org, "Shirron,
Stephen" <Stephen.Shirron@lsil.com>
Subject: Re: IP over FC and qlogic workarounds in fusion
Date: Mon, 06 Sep 2004 21:16:18 -0700 [thread overview]
Message-ID: <1094530577.29434.7.camel@praka> (raw)
In-Reply-To: <20040906101349.GA17669@lst.de>
On Mon, 2004-09-06 at 03:13, Christoph Hellwig wrote:
> On Mon, Aug 30, 2004 at 06:29:47PM -0400, Moore, Eric Dean wrote:
> > Here is feedback from Stephen Shirron, co-worker here
> > at LSI Logic:
> >
> > To my knowledge QLogic has never even acknowledged that
> > they had a bug. In my opinion it is not
> > safe to remove this code. We do have versions of the FC
> > firmware that work around this QLogic bug, but it's hard
> > to know if the entire field is populated. It would not
> > be good to introduce a regression that decreases our
> > interoperability.
>
> Andrew, could you please try to to find the right people at Qlogic
> to ACK or even better fix this?
>
I'm not sure who Stephen originally worked with at QLogic, but yes, this
is a known problem (finally managed to track down several firmware
engineers) and unfortunately 'will not be addressed' in the future.
You'll also note that FC-IP support has effectively been extricated from
the 8.x series driver.
Regards,
Andrew Vasquez
next prev parent reply other threads:[~2004-09-07 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 22:29 IP over FC and qlogic workarounds in fusion Moore, Eric Dean
2004-09-06 10:13 ` Christoph Hellwig
2004-09-07 4:16 ` Andrew Vasquez [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-07 18:12 Shirron, Stephen
2004-09-07 18:14 ` Christoph Hellwig
2004-08-28 19:37 Christoph Hellwig
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=1094530577.29434.7.camel@praka \
--to=andrew.vasquez@qlogic.com \
--cc=Emoore@lsil.com \
--cc=Stephen.Shirron@lsil.com \
--cc=hch@lst.de \
--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.