From: "Andrew Vasquez" <email@example.com>
To: "James Bottomley" <James.Bottomley@SteelEye.com>
Cc: "Linux Kernel" <firstname.lastname@example.org>,
Subject: RE: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b7).
Date: Thu, 8 Jan 2004 08:47:51 -0800 [thread overview]
Message-ID: <B179AE41C1147041AA1121F44614F0B060EDD4@AVEXCH02.qlogic.org> (raw)
On Monday, December 29, 2003 9:33 AM, James Bottomley wrote:
> On Fri, 2003-12-05 at 19:15, Andrew Vasquez wrote:
> > False start. I've uploaded 8.00.00b8 to the SF site. This driver
> > instructs the mid-layer to perform its initial scan with
> > scsi_scan_host(). During testing, I disable the scan. Sorry for
> > the confusion.
> OK, I've begun the BK process again.
> This driver is now in BK at
> I didn't see any comments about Christoph's patches, so is it OK if I
> apply them?
Yes, I've been entrenched in several side projects. I have a beta 9
ready for release which includes Christoph's patches as well as a
couple of other changes as a result of his comments (qla_fo.cfg,
exioct.h dependencies). At this time though, I need to wait to
release until I receive another firmware drop.
> I plan to let it mature in it's own tree for a short while with the
> object being to get it into the right shape for a 2.6 inclusion
> The two items we still need to do something about are:
> - Multi Pathing. This really doesn't belong in the kernel
Yes, given the structure and form of recent patches, that certainly
does seem to be the case - which from QLogic's standpoint (now) seems
to be the proper path. Just for clarification, given the structure of
the driver now (failover completely separated), inclusion of the
qla2xxx driver would exclude the following failover files:
qla_fo.c qla_foln.c qla_cfg.c qla_cfgln.c
> - The odd ioctl set to the qla device...I'd much rather see something
> more standard that all FC drivers can use.
Are you proposing to standardize a transport by which a user-space
application communicates with a driver (beyond IOCTLs), or, are you
suggesting there be some commonality in functional interfaces (i.e.
SNIA) for all FC drivers?
Look, IOCTLs were mainly used and built upon due the platform agnostic
nature of the interface. All QLogic drivers (Linux, Solaris, Windows,
and Netware), use the platform's IOCTL interface with the QLogic
specific EXIOCT interfaces to pass information to/from user and driver
space. Several user-space APIs were then created which use the EXIOCT
interface, SNIA (or HBAAPI), and several internal APIs, which are
ultimately used by all QLogic applications.
next reply other threads:[~2004-01-08 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 16:47 Andrew Vasquez [this message]
2004-01-08 16:54 ` [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b7) Christoph Hellwig
2004-01-08 19:33 ` Mike Anderson
2004-01-08 19:34 ` Christoph Hellwig
2004-01-08 19:57 ` Mike Anderson
2004-01-08 20:06 ` Christoph Hellwig
2004-01-08 22:11 ` Mike Anderson
-- strict thread matches above, loose matches on Subject: below --
2004-01-08 19:29 Andrew Vasquez
2003-12-06 1:15 Andrew Vasquez
2003-12-09 13:28 ` Christoph Hellwig
2003-12-29 17:32 ` James Bottomley
2003-12-05 20:52 Andrew Vasquez
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).