From: David Woodhouse <dwmw2@infradead.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-kernel@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Vipin Mehta <Vipin.Mehta@atheros.com>
Subject: Re: Firmware versioning best practices II
Date: Sat, 20 Feb 2010 11:09:26 +0000 [thread overview]
Message-ID: <1266664166.1820.4165.camel@macbook.infradead.org> (raw)
In-Reply-To: <1266663639.10357.1.camel@jlt3.sipsolutions.net>
On Sat, 2010-02-20 at 12:00 +0100, Johannes Berg wrote:
> That doesn't make much sense anyway. If the firmware filename is
> foo-$APIVER-$CODEVER every code change would need a corresponding driver
> change. If it is just foo-$APIVER then the $CODEVER can be embedded in
> the firmware file and printed so you know which code you're using, but
> if it doesn't influence the API I don't see why it should be part of the
> filename?
The idea is that just like with shared libraries, you have a symlink
from the 'soname' foo-3.fw to the actual file foo-3-1.4.1.fw.
For shared libraries, it's easy to create those symlinks automatically
using ldconfig. For firmware that doesn't really work though -- since
the soname isn't encoded in the file like it is in ELF libraries.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-02-20 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 2:23 Luis R. Rodriguez
2010-02-20 10:35 ` David Woodhouse
2010-02-20 11:00 ` Johannes Berg
2010-02-20 11:09 ` David Woodhouse [this message]
2010-02-20 11:10 ` Johannes Berg
2010-02-20 11:32 ` David Woodhouse
2010-02-21 10:13 ` Marcel Holtmann
2010-02-22 19:14 ` Luis R. Rodriguez
2010-02-22 19:27 ` Marcel Holtmann
2010-02-22 21:03 ` Luis R. Rodriguez
2010-02-23 7:06 ` 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=1266664166.1820.4165.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=Vipin.Mehta@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mcgrof@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome