From: Christian Lamparter <chunkeey@googlemail.com>
To: Eugene Krasnikov <k.eugene.e@gmail.com>
Cc: Adrian Chadd <adrian@freebsd.org>, Kalle Valo <kvalo@adurom.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"linux-bluetooth" <linux-bluetooth@vger.kernel.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: Mon, 8 Apr 2013 17:33:15 +0200 [thread overview]
Message-ID: <201304081733.15727.chunkeey@googlemail.com> (raw)
In-Reply-To: <CAFSJ42Zd3s8xKwt4X3LNcupCTntDULxNntMuD-_Xh6_csiGA4A@mail.gmail.com>
On Monday, April 08, 2013 11:10:30 AM Eugene Krasnikov wrote:
> It’s a good idea to pack bitmap into the tail/header of the firmware
> binary to get capabilities even before fw loading. The plan is to add
> 8 bytes for caps and also add time stamp. Let me play around with that
> and provide fw and driver patch for review.
Hm, come to think of it. Kalle, do you think ath9k_htc could use
some bits of the fw header format, parser or the complete infrastructure
from ath6kl? This could be great for Adrian, because he could
just point people to it and they could moved it into the code
into /drivers/net/wireless/ath/fw.c.
Regards,
Christian
next prev parent reply other threads:[~2013-04-08 15:33 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 ` Version number policy! 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
2013-04-06 7:08 ` Adrian Chadd
2013-04-08 9:10 ` Eugene Krasnikov
2013-04-08 15:33 ` Christian Lamparter [this message]
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=201304081733.15727.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=adrian@freebsd.org \
--cc=ath9k_htc_fw@lists.infradead.org \
--cc=k.eugene.e@gmail.com \
--cc=kvalo@adurom.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;
as well as URLs for NNTP newsgroup(s).