From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Marcel Holtmann <marcel@holtmann.org>,
Vipin Mehta <Vipin.Mehta@atheros.com>
Subject: Firmware versioning best practices II
Date: Fri, 19 Feb 2010 18:23:47 -0800 [thread overview]
Message-ID: <43e72e891002191823h3245bc0cn7a8745ae77409aa8@mail.gmail.com> (raw)
Last year, with the help of the community we at Atheros opened up the
first (to my knowledge) firmware for a device driver used on the Linux
kernel. The community has been advancing the firmware and making
changes and even an alternative driver with more features is being
baked. We hadn't dealt with open firmware before and this itself
raises a few management questions about the firmware APIs, code
revision and general best practices which are likely not documented
anywhere. We reviewed this on linux-wireless last year [1] and Pavel
Roskin made a good suggestion for model to follow. I still have a few
more questions though and wanted a wider review on this.
I've documented a summary of what we have discussed and suggested so far here:
http://wireless.kernel.org/en/developers/Documentation/firmware-versioning
We should still address how drivers should deprecate firmware. Can we
deprecate old firmware APIs from drivers on each kernel release? Any
other comments or feedback?
[1] http://wireless.kernel.org/en/developers/Documentation/firmware-versioning
Luis
next reply other threads:[~2010-02-20 2:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-20 2:23 Luis R. Rodriguez [this message]
2010-02-20 10:35 ` David Woodhouse
2010-02-20 11:00 ` Johannes Berg
2010-02-20 11:09 ` David Woodhouse
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=43e72e891002191823h3245bc0cn7a8745ae77409aa8@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=Vipin.Mehta@atheros.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®