aboutsummaryrefslogtreecommitdiffstats
path: root/tools/firmware-utils/src/tplink-safeloader.c
Commit message (Collapse)AuthorAgeFilesLines
* firmware-utils: tplink-safeloader: update support lists for CPE210/510/...Matthias Schiffer2016-12-121-4/+14
| | | | | | | Adds support for new EU and US variants; removes a few strings that were never actually used and have been removed from the stock firmwares. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* firmware-utils: tplink-safeloader: keep per-device info on trailing charRafał Miłecki2016-11-201-5/+11
| | | | | | | | | | | | | | | | | Recent refactoring introduced a regression. It ignored second argument of make_support_list function which was originally true for C2600. The new generic build_image function always passes false. This patch allows specifying trailing char in a device specific info. It also switches Archer C9 to the \0 char to make it compliant with vendor images. I verified generated images to be binary identical to the ones that were created before whole refactoring. Reported-by: Jo-Philipp Wich <jo@mein.io> Fixes: fd924d2068f ("firmware-utils: tplink-safeloader: use one function for generating images") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* firmware-utils: tplink-safeloader: add Archer C9 supportRafał Miłecki2016-11-191-0/+33
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* firmware-utils: tplink-safeloader: use one function for generating imagesRafał Miłecki2016-11-191-79/+29
| | | | | | Thanks to the struct device_info we can now use one unified function. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* firmware-utils: tplink-safeloader: add struct device_infoRafał Miłecki2016-11-191-6/+19
| | | | | | | This struct stores all device specific info which allows making do_eap function more generic. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ar71xx: Add support to TP-Link EAP120Henryk Heisig2016-10-181-0/+101
| | | | Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* tools/tplink-safeloader: split CPE210 from CPE510 profileAlexander Couzens2016-05-271-10/+23
| | | | | | | | | The CPE210 was still described for the OEM upgrade as compatible, even the wireless configuration isn't compatible anymore between both series (2ghz and 5ghz). Update the CPE210 image profile to use the new profile. Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* fw-utils/tplink-safeloader.c: Add support for Archer C2600Ash Benz2016-05-271-3/+111
| | | | Signed-off-by: Ash Benz <ash.benz@bk.ru>
* tools/firmware-utils: tplink-safeloader: add version 1.1 support to ↵John Crispin2015-10-191-4/+4
| | | | | | | | | | | | | | CPE210/220/510/520 The hardware is identical to version 1.0, add the new models to the support list. Also remove the empty line at the end of the support list, the current stock images don't have it either. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> SVN-Revision: 47212
* tools/firmware-utils: tplink-safeloader: fix support-list format, clean up ↵John Crispin2015-10-191-17/+30
| | | | | | | | | | | vendor information The first 4 bytes of the support list and the vendor information are supposed to contain the length of these fields. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> SVN-Revision: 47211
* tools/firmware-utils: tplink-safeloader: clean up codeJohn Crispin2015-10-191-11/+11
| | | | | | | | There is no reason for the internal functions not to be static. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> SVN-Revision: 47210
* firmware-utils: remove dependency on error.h in tplink-safeloaderFelix Fietkau2014-11-271-1/+9
| | | | | | | | Fixes build on Mac OS X Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 43402
* firmware-utils: add new tool tplink-safeloader for the new TP-LINK Pharos ↵John Crispin2014-11-261-0/+538
devices (CPE210/220/510/520) The new TP-LINK Pharos series uses a new bootloader, the "TP-LINK Safeloader". It uses an advanced firmware image format, containing an image partition table and a flash partition table (and image partitions are mapped to the corresponding flash partitions). The exact image format is documented in the source code. Furthermore, the bootloader expects the kernel image as an ELF executable. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> SVN-Revision: 43384