+version above 0.2.2.19. More on firmware upgrade subject see next section.
+
+Firmware available free of charge for ATMEL12350 MIB devices:
+-------------------------------------------------------------
+If you own device that is detected as 'ATMEL12350 MIB' by ap-utils, chances
+are that free-of-charge EZYNET-enhanced firmware upgrade is eligible for you!
+Upgrading firmware in your AP may have following advantages for you:
+
+- supporting more options; apparently the richest set of them available
+ for ATMEL+RFMD devices to day
+
+- preventing 'death by reconfiguration bug' present in older firmwares.
+
+- RSSI diagnostics in both AP and client modes at no cost!
+
+Your device will qualify for free-of-charge firmware upgrade in case
+it would satisfy the following (SATISFYING ALL POINTS IS MANDATORY!):
+
+1. It is detected as 'ATMEL12350' MIB and 'GEMTEK' vendor MIB extension
+ by ap-utils.
+
+2. It has second SRAM chip. The sign of second SRAM chip availability
+ is presence of (poor, locky) web management interface.
+
+3. it runs firmware 0.2.x.x except 0.2.1.1
+
+Should it satisfy all three points above, you may now perform upgrading.
+
+0. READ MANPAGE FOR ap-tftp !!!
+
+1. download the AP firmware (*.rom files) by EZYNET from the following URL:
+ ftp://ftp.unob.cz/pub/firmware/wlan/atmel+rfmd/
+
+2. perform AP upgrade either by original windows-based ATMEL tftp client,
+ or by 'ap-tftp' utility supplied with ap-utils:
+
+ First, upgrade with 0.2.0.20.rom image. This one is so-called 'backup'
+ firmware. It lacks (needless) web, and is activated only if so-called
+ 'primary firmware fails for some reason.
+
+ Second, upgrade with 0.2.2.20.rom image. This is the 'primary' firmware
+ with web interface (which you apparently wont use at all).
+
+3. You now have device with ATMEL12350 MIB & EZYNET extensions !!!
+
+Should you observe that the device suddenly switched to 0.2.0.20 firmware
+after some time, it means that the 'primary' firmware has been damaged
+in flash by some odd circumstances, and you should repeat step 2. above
+to fix it.
+[Note: this may only happen under _extremely_ rare circumstances, when,
+for example, lightning stroke appears too close to the AP, or when AP
+power supply voltage suddenly drops below sane level and returns back]