aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ath79/image/common-tp-link.mk
Commit message (Collapse)AuthorAgeFilesLines
* ath79: replace custom uImageArcher generationDavid Bauer2020-06-291-9/+1
| | | | | | | | | | | The replaces the custom uImageArcher build step with the generic uImage build step. The only different between these two is the difference in the generated name. Tested on: TP-Link Archer C59 v1 Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: do not build TP-Link tiny images by defaultAdrian Schmutzler2020-06-281-0/+2
| | | | | | | | | | | | | For quite some time, the tiny (4M flash) TP-Link sysupgrade and factory images cannot be built anymore by the buildbots, just the initramfs-kernel.bin files are still there. Disable these images for the buildbots and prevent useless builds. Note that these devices still build fine with default settings, even for kernel 5.4. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: image: fix initramfs for safeloader devicesPetr Štetiar2020-06-221-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently it's not possible to tftpboot initramfs image on archer-c7-v5 as the image contains tplink-v1-header which leads to: ath> bootm ## Booting image at 81000000 ... Bad Magic Number as U-Boot expects uImage wrapped image. This is caused by following inheritance issue: define Device/Init KERNEL_INITRAMFS = $$(KERNEL) define Device/tplink-v1 KERNEL := kernel-bin | append-dtb | lzma KERNEL_INITRAMFS := kernel-bin | append-dtb | lzma | tplink-v1-header define Device/tplink-safeloader $(Device/tplink-v1) define Device/tplink-safeloader-uimage $(Device/tplink-safeloader) KERNEL := kernel-bin | append-dtb | lzma | uImageArcher lzma define Device/tplink_archer-c7-v5 $(Device/tplink-safeloader-uimage) where tplink-v1 defines KERNEL_INITRAMFS with tplink-v1-header and it's then used by all devices inheriting from tplink-safeloader. Fix this by overriding KERNEL_INITRAMFS to KERNEL variable again. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* treewide: omit IMAGE_SIZE argument from check-sizeSungbo Eo2020-03-211-2/+2
| | | | | | | | | Now that check-size uses IMAGE_SIZE by default, we can skip the argument from image recipes to reduce redundancy. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: move TPLINK_HWID/_HWREV to parent for tplink-safeloaderAdrian Schmutzler2020-02-191-1/+4
| | | | | | | | | | | Several devices with tplink-safeloader contain default values (0x0) for TPLINK_HWID and TPLINK_HWREV in their device definitions. Move those to common tplink-safeloader definition so they do not have to be repeated each time. While at it, set default value for tplink-v1 and tplink-v2 as well. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add common definition for Device/tplink-v2Adrian Schmutzler2020-02-021-1/+12
| | | | | | | | | | | | | | | | This adds a shared definition Device/tplink-v2 to common-tp-link.mk. Though currently only one device in ath79 uses it, putting it in the common file seems more organized. The definitions are based on the implementation in ramips target, where a lot of devices is using tplink-v2-* commands already. The '-V "ver. 2.0"' suffix for Archer D50 v1 can be removed because it's default in Build/tplink-v2-image anyway. While at it, add TPLINK_HWREVADD and TPLINK_HVERSION to DEVICE_VARS, which seems to have been overlooked when adding Archer D50 v1. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: rename tplink-loader-okli to tplink-safeloader-okliAdrian Schmutzler2020-02-021-1/+1
| | | | | | | | | This renames Device/tplink-loader-okli to Device/tplink-safeloader-okli since the latter more accurately describes the combination of tplink-safeloader and loader-okli use there. The old version might be confused with other uses of the okli loader. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: rename Device/tplink to Device/tplink-v1Adrian Schmutzler2020-02-021-6/+6
| | | | | | | | | As we have tplink-v2-header and tplink-v2-image recipes as well, this patch renames the Device/tplink definition to Device/tplink-v1, as it's using the tplink-v1-* commands. This should provide easier distinction in the future. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: remove usused TPLINK_BOARD_NAME variable for DEVICE_VARSAdrian Schmutzler2020-01-211-1/+1
| | | | | | | | | | | | | | TPLINK_BOARD_NAME has been renamed to TPLINK_BOARD_ID a long time ago (7d6c63d87542: "build: rename TPLINK_BOARD_NAME to TPLINK_BOARD_ID" for ar71xx), and before introducing ath79 target at all. TPLINK_BOARD_NAME seems to have been introduced into ath79 target only by mistake. It has never been used. Remove it. Fixes: 53c474abbdfe ("ath79: add new OF only target for QCA MIPS silicon") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: remove unused Build/mktplinkfw-combinedAdrian Schmutzler2020-01-081-11/+0
| | | | | | Build/mktplinkfw-combined is not used anywhere, so remove it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: move mktplinkfw to tplink-v1-image in image-commands.mkAdrian Schmutzler2020-01-081-25/+2
| | | | | | | | | | | | | | | | | | | | | This move the slightly different target-specific implementations of mktplinkfw from the targets to include/image-commands.mk and renames it to tplink-v1-image. Having a common version will increase consistency between implementation and will complete the tplink build command already present in the new location. Due to the slight differences of the original implementations, this also does some adjustments to the device build commands/variables. This also moves rootfs_align as this is required as dependency. Tested on: - TL-WDR4300 v1 (ath79, factory) - TL-WDR4900 v1 (mpc85xx, sysupgrade) - RE210 v1 (ramips, see Tested-by) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Christoph Krapp <achterin@googlemail.com>
* ath79: harmonize line breaks in image MakefilesAdrian Schmutzler2019-12-201-18/+16
| | | | | | | | | | | | | | | | This harmonizes the line wrapping in image Makefile device definitions, as those are frequently copy-pasted and are a common subject of review comments. Having the treatment unifying should reduce the cases where adjustment is necessary afterwards. Harmonization is achieved by consistently (read "strictly") applying certain rules: - Never put more than 80 characters into one line - Fill lines up (do not break after 40 chars because of ...) - Use one tab for indent after wrapping by "\" - Only break after pipe "|" for IMAGE variables Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix IMAGE_SIZE for common TP-Link definitionsAdrian Schmutzler2019-10-271-3/+3
| | | | | | | | | | | | | | | | | | | So far, IMAGE_SIZE is set as follows: tplink-4m* 3904k 0x3d0000 tplink-8m* 7936k 0x7c0000 tplink-16m* 15872k 0xf80000 However, based on the size of firmware partitions in DTS it should be: tplink-4m* 3904k 0x3d0000 tplink-8m* 8000k 0x7d0000 tplink-16m* 16192k 0xfd0000 All (!) 8m*/16m* devices actually follow the latter scheme, which is also consistent in terms of left free space for other partitions. Thus, fix it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: create common definition tplink-loader-okliAdrian Schmutzler2019-08-071-0/+9
| | | | | | | The loader-okli is shared by several TP-Link CPExxx devices, so give it its own definition to prevent too much code duplication. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: split DEVICE_TITLE in multiple variablesPaul Spooren2019-07-041-0/+1
| | | | | | | | | | | | | | This allows the definition of DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT. All three are merged together to look the same as the current DEVICE_TITLE. Also, if DEVICE_TITLE is set it's directly used as a *fallback* for devices which weren't upgraded yet. This is based on the work of @sudhanshu16. The motivation is to create JSON files based on provided metadata, needing clear differentiation between vendor, model and revision. Signed-off-by: Paul Spooren <mail@aparcar.org>
* ath79: Utilize tplink-safeloader definitionAdrian Schmutzler2019-04-061-2/+3
| | | | | | | | | | | | | | | | | Currently, tplink-safeloader definition is only used a base for another common definition. This patch adjusts tplink-safeloader so it can be actually used for some targets in generic-tp-link.mk. This patch is cosmetic except for the order of "check-size $$$$(IMAGE_SIZE)" and "append-metadata" exchanged for the tplink_re350k-v1 . Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [dealed with tplink_cpe210-v2 and tplink_cpe210-v3, removed tplink-safeloader-uimage's extra IMAGE/sysupgrade.bin rule]
* ath79: proper indentation in image/common-tp-link.mkPaul Wassi2019-02-141-1/+1
| | | | | | Add two spaces for proper indentation in image/common-tp-link.mk Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* ath79: remove duplicate image build variablesMathias Kresin2018-12-061-1/+1
| | | | | | | Remove image build variables which are set to the same value as the default image build recipe. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath79: add support for Archer C58/C59 v1David Bauer2018-11-261-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the Archer C58 v1 and C59 v1, previously supported in the ar71xx target. CPU: Qualcomm QCA9561 RAM: 64M (C58) / 128M (C59) FLASH: 8M (C58) / 16M (C59) WiFi: QCA9561 bgn 3x3:3 QCA9888 nac 2x2:2 LED: Power, WiFi 2.4, WiFi 5, WAN green, WAN amber, LAN, WPS Only C59: USB BTN: WPS, WiFi, Reset Installation ------------ Via Web-UI: Update factory image via Web-UI. Via TFTP: Rename factory image to "tp_recovery.bin" and place it in the root-dir of your tftp server. Configure to listen on 192.168.0.66. Power up the router while holding down the reset-button. The router will flash itself and reboot. Note: For TFTP, you might need a switch between router and computer, as link establishment might take to long. Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for TP-Link RE450 v2Peter Lundkvist2018-07-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | TP-Link RE450 v2 is a dual band router/range-extender based on Qualcomm/Atheros QCA9563 + QCA9880. Specification: - 775 MHz CPU - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 3T3R 5 GHz - 1x 10/100/1000 Mbps Ethernet (AR8033 PHY) - 7x LED, 4x button - UART header on PCB (needs unmounted R64 & R69 0201 resistors/jumpers) Flash instruction: Apply factory image in OEM firmware web-gui. U-Boot does not seem to have any recovery functions, so debricking requires connection via UART. Signed-off-by: Peter Lundkvist <peter.lundkvist@gmail.com>
* ath79: add support for TP-Link Archer c7 v2Sibren Vasse2018-06-261-0/+6
| | | | Signed-off-by: Sibren Vasse <github@sibrenvasse.nl>
* ath79: lzma-loader: sync with ar71xx targetMatthias Schiffer2018-06-061-1/+1
| | | | | | | | | | | | | | Import all improvements made in the lzma-loader since development on the ath79 target started. This also reverts fe594bf90d09 ("ath79: fix loader-okli, lzma-loader"), as is obsoleted by 2ad60168b6af ("ar71xx: lzma-loader: move padding workaround to gzip step"). Likely, many of the changes should be ported to the ramips lzma-loader as well, but I don't have a device to test this. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ath79: add tiny subtargetAlex Maclean2018-06-011-0/+84
Signed-off-by: Alex Maclean <monkeh@monkeh.net>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 12:17:52 +0000