From: Mark Lord <lkml@rtr.ca>
To: Marcel Holtmann <marcel@holtmann.org>
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 09:28:49 -0400 [thread overview]
Message-ID: <44463B11.6030005@rtr.ca> (raw)
In-Reply-To: <1145374878.10255.69.camel@localhost>
Marcel Holtmann wrote:
..
> 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?
I'm probably misunderstanding something here.
next prev parent reply other threads:[~2006-04-19 13:28 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 [this message]
2006-04-19 13:37 ` Marcel Holtmann
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=44463B11.6030005@rtr.ca \
--to=lkml@rtr.ca \
--cc=duncan.sands@math.u-psud.fr \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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.