From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
reinette chatre <reinette.chatre@intel.com>,
Kalle Valo <kalle.valo@nokia.com>,
Johannes Berg <johannes@sipsolutions.net>,
Christian Lamparter <chunkeey@web.de>,
Bob Copeland <me@bobcopeland.com>
Subject: Re: Firmware versioning best practices
Date: Tue, 29 Sep 2009 08:59:24 +0200 [thread overview]
Message-ID: <200909290859.25075.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <43e72e890909281517k23abaf8dvd3e84837ce307429@mail.gmail.com>
> Or shall we have the same firmware filename and simply query
> the firmware for a map of capabilities? Any other ideas?
Don't put the version into the filename. This is not a common
practice for Linux / BSD / whatever systems. Usually you have
a "kmail" file, not a kmail3.5, kmail4.0 and kmail4.2 file.
Versions or capability maps can be stored inside the firmware and
queried at load time. E.g. the libertas driver does it that way.
If you make your firmware redistributable (which I recommend),
the version will also be stored in the package metadata, e.g.
the rpm or deb file and the infrastructure for rpm/yum deb/apt.
--
http://www.holgerschurig.de
next prev parent reply other threads:[~2009-09-29 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 22:17 Firmware versioning best practices Luis R. Rodriguez
2009-09-28 22:33 ` Pavel Roskin
2009-09-28 23:05 ` Luis R. Rodriguez
2009-09-28 23:52 ` Marcel Holtmann
2009-09-29 0:42 ` John W. Linville
2010-02-20 2:14 ` Luis R. Rodriguez
2009-09-29 6:59 ` Holger Schurig [this message]
2009-09-29 10:45 ` Tomas Winkler
2009-09-29 11:01 ` Holger Schurig
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=200909290859.25075.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=chunkeey@web.de \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@nokia.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=reinette.chatre@intel.com \
/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.