From: Jeff Garzik <jgarzik@pobox.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
Christoph Hellwig <hch@lst.de>,
James Bottomley <James.Bottomley@SteelEye.com>,
Linux-SCSI <linux-scsi@vger.kernel.org>
Subject: Re: pulling failover out of qla2xxx
Date: Fri, 16 Jan 2004 18:39:29 -0500 [thread overview]
Message-ID: <20040116233929.GA30969@gtf.org> (raw)
In-Reply-To: <20040116233328.GB24093@devserv.devel.redhat.com>
On Sat, Jan 17, 2004 at 12:33:28AM +0100, Arjan van de Ven wrote:
> Another approach could be separate modules which ONLY have firmware, one
> module per firmware file (but that gets you really close to
> request_firmare() api)
That's what the upstream tree has right now... here's the complete
contents of ql2100.c...
/*
* QLogic ISP2100 device driver for Linux 2.6.x
* Copyright (C) 2003 Christoph Hellwig.
* Copyright (C) 2003 QLogic Corporation (www.qlogic.com)
*
* Released under GPL v2.
*/
#include <linux/init.h>
#include <linux/module.h>
#include <linux/pci.h>
#include "qla_os.h"
#include "qla_def.h"
static char qla_driver_name[] = "qla2100";
extern unsigned char fw2100tp_version[];
extern unsigned char fw2100tp_version_str[];
extern unsigned short fw2100tp_addr01;
extern unsigned short fw2100tp_code01[];
extern unsigned short fw2100tp_length01;
static struct qla_fw_info qla_fw_tbl[] = {
{
.addressing = FW_INFO_ADDR_NORMAL,
.fwcode = &fw2100tp_code01[0],
.fwlen = &fw2100tp_length01,
.fwstart = &fw2100tp_addr01,
},
{ FW_INFO_ADDR_NOMORE, },
};
static struct qla_board_info qla_board_tbl = {
.drv_name = qla_driver_name,
.isp_name = "ISP2100",
.fw_info = qla_fw_tbl,
};
static struct pci_device_id qla2100_pci_tbl[] = {
{
.vendor = PCI_VENDOR_ID_QLOGIC,
.device = PCI_DEVICE_ID_QLOGIC_ISP2100,
.subvendor = PCI_ANY_ID,
.subdevice = PCI_ANY_ID,
.driver_data = (unsigned long)&qla_board_tbl,
},
{0, 0},
};
MODULE_DEVICE_TABLE(pci, qla2100_pci_tbl);
static int __devinit
qla2100_probe_one(struct pci_dev *pdev, const struct pci_device_id *id)
{
return qla2x00_probe_one(pdev,
(struct qla_board_info *)id->driver_data);
}
static void __devexit
qla2100_remove_one(struct pci_dev *pdev)
{
qla2x00_remove_one(pdev);
}
static struct pci_driver qla2100_pci_driver = {
.name = "qla2100",
.id_table = qla2100_pci_tbl,
.probe = qla2100_probe_one,
.remove = __devexit_p(qla2100_remove_one),
};
static int __init
qla2100_init(void)
{
return pci_module_init(&qla2100_pci_driver);
}
static void __exit
qla2100_exit(void)
{
pci_unregister_driver(&qla2100_pci_driver);
}
module_init(qla2100_init);
module_exit(qla2100_exit);
MODULE_AUTHOR("QLogic Corporation");
MODULE_DESCRIPTION("QLogic ISP21xx FC-SCSI Host Bus Adapter driver");
MODULE_LICENSE("GPL");
next prev parent reply other threads:[~2004-01-16 23:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 20:02 pulling failover out of qla2xxx Andrew Vasquez
2004-01-16 20:24 ` Jeff Garzik
2004-01-17 16:53 ` Christoph Hellwig
2004-01-17 20:52 ` Andrew Vasquez
2004-01-17 21:08 ` Arjan van de Ven
2004-01-17 21:52 ` Andrew Vasquez
2004-01-18 10:37 ` Arjan van de Ven
2004-01-16 23:33 ` Arjan van de Ven
2004-01-16 23:39 ` Jeff Garzik [this message]
2004-01-17 16:52 ` Christoph Hellwig
2004-01-17 18:47 ` Arjan van de Ven
2004-01-17 18:51 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 1:36 Andrew Vasquez
2004-01-16 12:06 ` 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=20040116233929.GA30969@gtf.org \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@SteelEye.com \
--cc=andrew.vasquez@qlogic.com \
--cc=arjanv@redhat.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 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).