From: Roman Kagan <rkagan@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: firmware and initrd [was Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts]
Date: Fri, 04 Mar 2005 11:16:47 +0000 [thread overview]
Message-ID: <20050304111646.GC2219@katya> (raw)
In-Reply-To: <20050224224343.B7339@banaan.localdomain>
On Fri, Feb 25, 2005 at 04:18:21PM -0800, Andrew Vasquez wrote:
> Actually, the qla2[123]00.ko, qla2322.ko and qla6312.ko files only
> existed as 'firmware-loader' modules. The core driver routines went
> into qla2xxx.ko. My hope is that once the driver transitions to the
> request_firmware() interface, the firmware-loader modules get dropped
> and the we're left with a single qla2xxx.ko module which will
> request_firmware() the proper image type based on device-id:
This brings up another question: if the only difference between the
devices is the firmware image they need, and otherwise the driver can be
made generic (dunno if this is the case for qla2xxx, but I've seen a few
drivers like this), should the driver request_firmware() by
device-specific names, or should it rather request a generic name, and
the hotplug firmware agent would have to provide the correct image based
on device IDs available via sysfs or environment?
In other words, where should the knowledge about the matching between
the device IDs and the required firmware go into: the driver or the
firmware agent?
Roman.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-03-04 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 21:43 firmware and initrd [was Re: [ANNOUNCE] yaird, a mkinitrd based on hotplug concepts] Erik van Konijnenburg
2005-02-25 23:29 ` Patrick Mansfield
2005-02-27 11:32 ` Erik van Konijnenburg
2005-03-04 11:16 ` Roman Kagan [this message]
2005-03-05 15:10 ` Erik van Konijnenburg
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=20050304111646.GC2219@katya \
--to=rkagan@mail.ru \
--cc=linux-hotplug@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).