On Thu, Jan 08, 2004 at 08:47:51AM -0800, Andrew Vasquez wrote: > 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 > > correct? + qla_inioct.c qla_xioct.c and the associated headers for both the ioctl and failover code, of course > > - 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? the SNIA HBA-API spec is completely broken. But we should try to support a sanitized subset of the spec using the transport class work that's currently discussed on linux-scsi. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups: References:
- Prev by Date: Re: MegaRAID on AMD64 under 2.6.1
- Next by Date: [no subject]
- Previous by thread: RE: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b7).
- Next by thread: Re: [ANNOUNCE] QLogic qla2xxx driver update available (v8.00.00b7).
- Indexes:[Main][Thread]