Return-path: Received: from mail-vc0-f182.google.com ([209.85.220.182]:57401 "EHLO mail-vc0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934539Ab3DHJKb convert rfc822-to-8bit (ORCPT ); Mon, 8 Apr 2013 05:10:31 -0400 MIME-Version: 1.0 In-Reply-To: References: <201304051903.11215.chunkeey@googlemail.com> <8762008auk.fsf@purkki.adurom.net> Date: Mon, 8 Apr 2013 11:10:30 +0200 Message-ID: (sfid-20130408_111053_519003_FE80D6A0) Subject: Re: Version number policy! From: Eugene Krasnikov To: Adrian Chadd Cc: Kalle Valo , Christian Lamparter , "Luis R. Rodriguez" , linux-bluetooth , linux-wireless , ath9k_htc_fw , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=windows-1252 Sender: linux-wireless-owner@vger.kernel.org List-ID: Thanx Christian for a valuable input. 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. 2013/4/6 Adrian Chadd : > On 5 April 2013 22:52, Kalle Valo wrote: >> Eugene Krasnikov 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. > > Ok. Well, we've got plenty of time to finalise this before things get > established. There's still plenty of tidying up to do before we start > pushing in new features. > > Thanks for all your feedback so far! > > > > Adrian -- Best regards, Eugene