Understanding what files are what in a flash archive

[Brad Davidson]

For the benefit of the archives, here's what the Intersil PDF says about 
the firmware naming scheme:

---
There are two types of firmware builds, developer builds and library 
release builds. Developer builds are firmware builds that are not 
reproducible and are not intended for external use.Library release 
builds are supported builds that have gone through the release and 
Quality Assurance process and are made available for external use.

Developer builds use the following naming convention:
<developer><type><date><platform><build_number>.HEX
where:
* developer is a single initial
* type can be I (Initial), P (Primary), S (Secondary), or T (Tertiary)
* date is a 4-character month/day combination
* platform is a 1-character platform ID
* build_number is a 1-character build number
For example, WS0126F0.HEX represents build 0 on 1/26 of Station firmware 
for the F platform.

Library releases use the following naming convention:
<type><platform><Version_Major/Minor><Version_Variant>.HEX
where:
* type can be I (Initial), P (Primary), S (Secondary), or T (Tertiary)
* platform is a 1-character platform ID
* Version_Major/Minor consists of a 2-character major version and 
2-character minor version
* Version_Variant is a 2-character version variant.
For example, SF010000.HEX represents a library release version 01.00.00 
of Station firmware for the F platform.
---

Hopefully that will save someone a bit of looking next time it's needed.

-Brad

James B. Hiller wrote:
> Is there a secret decoder ring out there for the file naming?  I've
> gone through a little over 50% of the hostap archive, and so far
> I remain clueless on this.