From: Marcel Holtmann <marcel@holtmann.org>
To: Mark Lord <lkml@rtr.ca>
Cc: Duncan Sands <duncan.sands@math.u-psud.fr>,
Jon Masters <jonathan@jonmasters.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] binary firmware and modules
Date: Wed, 19 Apr 2006 15:37:22 +0200 [thread overview]
Message-ID: <1145453842.3564.16.camel@localhost> (raw)
In-Reply-To: <44463B11.6030005@rtr.ca>
Hi Mark,
> > I personally prefer full firmware names. This makes the dependency easy
> > and even an end user can call modinfo and see what firmware is expected
> > by a certain driver (without looking at the source code).
>
> How does one handle the case of updated firmware from the manufacturer,
> which requires *no* driver changes? If the driver has all of the previously
> known names/versions hardcoded, then would it refuse to use the new stuff?
if no driver change is needed, then you simply can replace the firmware
file and reload the driver. With the BlueFRITZ! USB driver we did this a
bunch of times and it worked out perfectly. The firmware name in this
case is only a placeholder.
Regards
Marcel
next prev parent reply other threads:[~2006-04-19 13:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 8:10 [RFC] binary firmware and modules Jon Masters
2006-04-15 9:54 ` Oliver Neukum
2006-04-17 14:22 ` John W. Linville
2006-04-17 14:29 ` Arjan van de Ven
2006-04-17 14:38 ` Marcel Holtmann
2006-04-17 15:15 ` Duncan Sands
2006-04-17 16:10 ` Marcel Holtmann
2006-04-18 13:16 ` Jon Masters
2006-04-18 13:37 ` Duncan Sands
2006-04-18 14:14 ` Jon Masters
2006-04-18 15:14 ` Duncan Sands
2006-04-19 0:01 ` Jon Masters
2006-04-18 14:22 ` Marcel Holtmann
2006-04-18 14:59 ` Duncan Sands
2006-04-18 15:41 ` Marcel Holtmann
2006-04-19 13:28 ` Mark Lord
2006-04-19 13:37 ` Marcel Holtmann [this message]
2006-04-19 14:10 ` Jon Masters
2006-04-18 14:25 ` Marcel Holtmann
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=1145453842.3564.16.camel@localhost \
--to=marcel@holtmann.org \
--cc=duncan.sands@math.u-psud.fr \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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