+ - ap-dfu, ap-dfu.8 (internal developer's notes):
+ - what DFU really stands for (and that ap-dfu contains some extra
+ Atmel-specific functionality)
+ - only for ATMEL AT76C510-based hardware
+ - *hci stuff - at least on Linux (prerequisities)
+ - PIDs and VIDs for INTERSIL & RFMD based boards.
+ If the AP does not present itself with PID & VID in kernel
+ ring buffer (use dmesg for displaying) after it has been plugged
+ to USB interface, it means that the flash content is apparently
+ damaged and AP dead (the only solution in such case is to return
+ AP to the reseller for replacement).
+ - mandate user to read ap-tftp.8 warning sections first!
+ - it is safe (?) if AP experiences power outtage during upgrade, or
+ if ap-dfu bails out with error due to USB interface inconsistency.
+ In such case, it is safe to start ap-dfu again, and it will continue
+ where it left off - typically, when the AP is stuck in DFU mode with
+ steady LEDs light.
+* (WA* firmware support?): get_mib_details(): rename to get_fw_details(); add
+ FW (AP, WA) type detection (fw_type); rename ap_type to fw_eprises;
+ rename ap_vendorext to fw_vendorext; enterprises should be named
+ 410, 12350, NWN (strip down length)