From: Douglas Gilbert <dougg@torque.net>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] aic94xx: convert to request_firmware interface
Date: Mon, 28 Aug 2006 18:09:36 -0400 [thread overview]
Message-ID: <44F369A0.3020409@torque.net> (raw)
In-Reply-To: <1156798794.3465.27.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Mon, 2006-08-28 at 16:43 -0400, Douglas Gilbert wrote:
>> What I'm angling at is a firmware file name like:
>> aic94xx-seq_10c6.req
>
> I don't think that's a good idea ... the current razor firmware is
> backwards compatible, so if I hard code a version into the file there'd
> be no upgrade ability.
>
>> and the driver attempts to read:
>> aic94xx-seq*.req
>
> It can't do that from the kernel ... this is all conditioned on how the
> user level firmware loader actually works
>
>> If there a multiple matches then it takes the one
>> with the most recent date (reporting this in syslog).
>
> The way you do this is to have a generic name (aic94xx-seq.fw) and then
> symbolically link it to the versioned file.
>
> The firmware itself is versioned, so if the driver comes to require a
> particular version (or later), it can be programmed to complain.
Which may explain why firmware for a WIFI card that
I have has a versioned filename with a README in the
distribution tarball. The README says to add a symlink.
The README also tells me which directory to put the
firmware file and symlink in.
Doug Gilbert
next prev parent reply other threads:[~2006-08-28 22:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 2:48 [PATCH] aic94xx: convert to request_firmware interface James Bottomley
2006-08-28 3:47 ` James Bottomley
2006-08-28 12:52 ` Douglas Gilbert
2006-08-28 14:05 ` James Bottomley
2006-08-28 20:43 ` Douglas Gilbert
2006-08-28 20:59 ` James Bottomley
2006-08-28 22:09 ` Douglas Gilbert [this message]
2006-08-28 15:52 ` Luben Tuikov
2006-08-28 15:58 ` Arjan van de Ven
2006-08-28 15:59 ` James Bottomley
2006-08-28 21:04 ` Mike Anderson
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=44F369A0.3020409@torque.net \
--to=dougg@torque.net \
--cc=James.Bottomley@SteelEye.com \
--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).