From: Kalle Valo <kvalo@adurom.com>
To: Eugene Krasnikov <k.eugene.e@gmail.com>
Cc: Christian Lamparter <chunkeey@googlemail.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
Adrian Chadd <adrian@freebsd.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath9k_htc_fw <ath9k_htc_fw@lists.infradead.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Version number policy!
Date: Sat, 06 Apr 2013 08:52:19 +0300 [thread overview]
Message-ID: <8762008auk.fsf@purkki.adurom.net> (raw)
In-Reply-To: <CAFSJ42bqquh+xekt8+V3wbG3MOUVFELTxR3mNPfS0Jn9J7OURQ@mail.gmail.com> (Eugene Krasnikov's message of "Fri, 5 Apr 2013 19:23:54 +0200")
Eugene Krasnikov <k.eugene.e@gmail.com> writes:
> Good point regarding timestamp.
>
> When it comes to feature bitmap do you have an example of such a
> bitmap from carl9170? Why not to rely always on major version?
I'm with Christian here. In ath6kl we switched to firmware advertising
feature capabilities and I have never looked back, it's so much easier.
You don't need to do any mapping between firmware versions and features,
you just deal one feature at a time.
--
Kalle Valo
next prev parent reply other threads:[~2013-04-06 6:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ-Vmo=LVSzdEo6DhfOVT_0JHCTMmdPU1zGfMuBmhmr8QuDmJQ@mail.gmail.com>
2013-04-05 8:19 ` Luis R. Rodriguez
2013-04-05 8:21 ` Adrian Chadd
2013-04-05 16:42 ` Eugene Krasnikov
2013-04-05 17:03 ` Christian Lamparter
2013-04-05 17:23 ` Eugene Krasnikov
2013-04-05 18:08 ` Christian Lamparter
2013-04-05 19:16 ` Adrian Chadd
2013-04-06 5:52 ` Kalle Valo [this message]
2013-04-06 7:08 ` Adrian Chadd
2013-04-08 9:10 ` Eugene Krasnikov
2013-04-08 15:33 ` Christian Lamparter
2013-04-08 19:00 ` Adrian Chadd
2013-04-08 20:37 ` Eugene Krasnikov
2013-04-08 22:03 ` Christian Lamparter
2013-04-08 23:12 ` Adrian Chadd
2013-04-09 0:37 ` Theodore Ts'o
2013-04-09 1:51 ` Adrian Chadd
2013-04-09 11:28 ` Theodore Ts'o
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=8762008auk.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=adrian@freebsd.org \
--cc=ath9k_htc_fw@lists.infradead.org \
--cc=chunkeey@googlemail.com \
--cc=k.eugene.e@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@do-not-panic.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
all inboxes | Powered by JetHome®