linux-kernel - Re: Version number policy!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 8 Apr 2013 17:33:15 +0200
From:	Christian Lamparter <chunkeey@...glemail.com>
To:	Eugene Krasnikov <k.eugene.e@...il.com>
Cc:	Adrian Chadd <adrian@...ebsd.org>, Kalle Valo <kvalo@...rom.com>,
	"Luis R. Rodriguez" <mcgrof@...not-panic.com>,
	"linux-bluetooth" <linux-bluetooth@...r.kernel.org>,
	"linux-wireless" <linux-wireless@...r.kernel.org>,
	"ath9k_htc_fw" <ath9k_htc_fw@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Version number policy!

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/