From: Arjan van de Ven <arjanv@redhat.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: 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: Sat, 17 Jan 2004 00:33:28 +0100 [thread overview]
Message-ID: <20040116233328.GB24093@devserv.devel.redhat.com> (raw)
In-Reply-To: <B179AE41C1147041AA1121F44614F0B0598E34@AVEXCH02.qlogic.org>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On Fri, Jan 16, 2004 at 12:02:50PM -0800, Andrew Vasquez wrote:
> I'll open up a request-for-response from the rest of the listers in
> asking if parceling out qlaAB00.ko modules based on firmware types is
> both practical and sensible from a user standpoint. Especially
> considering that many users aren't really concerned with the ISP chip
> type on their QLAXXXX or OEM-BRANDED ABC host bus adapter.
that is what operating system installers are for (and udev/hotplug), modules
load automatically based on the PCI table nowadays ;)
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)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-16 23:33 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 [this message]
2004-01-16 23:39 ` Jeff Garzik
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=20040116233328.GB24093@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=James.Bottomley@SteelEye.com \
--cc=andrew.vasquez@qlogic.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.