diff options
| author | Sander Vanheule <sander@svanheule.net> | 2020-08-05 20:49:44 +0200 |
|---|---|---|
| committer | Alexander Couzens <lynxis@fe80.eu> | 2020-12-07 01:55:28 +0100 |
| commit | 1a211af2cb3be415a2c3454dea6fdc9a59bba334 (patch) | |
| tree | 591ed5889a9e785f4a14c0ceaa807cb6af0885a9 /package/boot/uboot-fritz4040 | |
| parent | 588933ae9a7651b53dc5fbc51b84218b6b8004fc (diff) | |
| download | upstream-1a211af2cb3be415a2c3454dea6fdc9a59bba334.tar.gz upstream-1a211af2cb3be415a2c3454dea6fdc9a59bba334.tar.bz2 upstream-1a211af2cb3be415a2c3454dea6fdc9a59bba334.zip | |
firmware-utils: tplink-safeloader: refactor meta-partition generation
TP-Link safeloader firmware images contain a number of (small)
partitions with information about the device. These consist of:
* The data length as a 32-bit integer
* A 32-bit zero padding
* The partition data, with its length set in the first field
The OpenWrt factory image partitions that follow this structure are
soft-version, support-list, and extra-para. Refactor the code to put all
common logic into one allocation call, and let the rest of the data be
filled in by the original functions.
Due to the extra-para changes, this patch results in factory images that
change by 2 bytes (not counting the checksum) for three devices:
* ARCHER-A7-V5
* ARCHER-C7-V4
* ARCHER-C7-V5
These were the devices where the extra-para blob didn't match the common
format. The hardcoded data also didn't correspond to TP-Link's (recent)
upgrade images, which actually matches the meta-partition format.
A padding byte is also added to the extra-para partition for EAP245-V3.
Signed-off-by: Sander Vanheule <sander@svanheule.net>
Diffstat (limited to 'package/boot/uboot-fritz4040')
0 files changed, 0 insertions, 0 deletions