2018-01-12 15:36:13 +00:00
|
|
|
include ./common-tp-link.mk
|
2017-05-31 14:31:44 +00:00
|
|
|
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-10 17:31:54 +00:00
|
|
|
define Device/archer-cxx
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | uImageArcher lzma
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
2017-06-30 22:28:39 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade | \
|
|
|
|
|
append-metadata | check-size $$$$(IMAGE_SIZE)
|
2017-06-10 17:31:54 +00:00
|
|
|
IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
|
|
|
|
|
endef
|
|
|
|
|
|
2017-04-22 16:21:47 +00:00
|
|
|
define Device/archer-c25-v1
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/archer-cxx)
|
2017-04-22 16:21:47 +00:00
|
|
|
DEVICE_TITLE := TP-LINK Archer C25 v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca9887
|
|
|
|
|
BOARDNAME := ARCHER-C25-V1
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := ARCHER-C25-V1
|
2017-04-22 16:21:47 +00:00
|
|
|
DEVICE_PROFILE := ARCHERC25V1
|
|
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
LOADER_TYPE := elf
|
|
|
|
|
MTDPARTS := spi0.0:128k(factory-uboot)ro,64k(u-boot)ro,1536k(kernel),6272k(rootfs),128k(config)ro,64k(art)ro,7808k@0x30000(firmware)
|
2017-06-30 22:28:39 +00:00
|
|
|
SUPPORTED_DEVICES := archer-c25-v1
|
2017-04-22 16:21:47 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c25-v1
|
2017-04-22 16:21:47 +00:00
|
|
|
|
2017-06-16 13:26:30 +00:00
|
|
|
define Device/archer-c58-v1
|
|
|
|
|
$(Device/archer-cxx)
|
|
|
|
|
DEVICE_TITLE := TP-LINK Archer C58 v1
|
2017-06-29 13:20:31 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca9888
|
2017-06-16 13:26:30 +00:00
|
|
|
BOARDNAME := ARCHER-C58-V1
|
2017-07-04 13:09:52 +00:00
|
|
|
TPLINK_BOARD_ID := ARCHER-C58-V1
|
2017-06-16 13:26:30 +00:00
|
|
|
DEVICE_PROFILE := ARCHERC58V1
|
|
|
|
|
IMAGE_SIZE := 7936k
|
2017-10-26 22:23:17 +00:00
|
|
|
MTDPARTS := spi0.0:64k(u-boot)ro,64k(mac)ro,7936k(firmware),64k(tplink)ro,64k(art)ro
|
2017-06-30 22:28:39 +00:00
|
|
|
SUPPORTED_DEVICES := archer-c58-v1
|
2017-06-16 13:26:30 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c58-v1
|
2017-06-16 13:26:30 +00:00
|
|
|
|
2016-12-27 21:41:41 +00:00
|
|
|
define Device/archer-c59-v1
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/archer-cxx)
|
2016-12-27 21:41:41 +00:00
|
|
|
DEVICE_TITLE := TP-LINK Archer C59 v1
|
2017-06-29 13:20:31 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k ath10k-firmware-qca9888
|
2016-12-27 21:41:41 +00:00
|
|
|
BOARDNAME := ARCHER-C59-V1
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := ARCHER-C59-V1
|
2016-12-27 21:41:41 +00:00
|
|
|
DEVICE_PROFILE := ARCHERC59V1
|
|
|
|
|
IMAGE_SIZE := 14528k
|
|
|
|
|
MTDPARTS := spi0.0:64k(u-boot)ro,64k(mac)ro,1536k(kernel),12992k(rootfs),1664k(tplink)ro,64k(art)ro,14528k@0x20000(firmware)
|
2017-06-30 22:28:39 +00:00
|
|
|
SUPPORTED_DEVICES := archer-c59-v1
|
2016-12-27 21:41:41 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c59-v1
|
2016-12-27 21:41:41 +00:00
|
|
|
|
|
|
|
|
define Device/archer-c60-v1
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/archer-cxx)
|
2016-12-27 21:41:41 +00:00
|
|
|
DEVICE_TITLE := TP-LINK Archer C60 v1
|
2017-06-29 13:20:31 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca9888
|
2016-12-27 21:41:41 +00:00
|
|
|
BOARDNAME := ARCHER-C60-V1
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := ARCHER-C60-V1
|
2016-12-27 21:41:41 +00:00
|
|
|
DEVICE_PROFILE := ARCHERC60V1
|
|
|
|
|
IMAGE_SIZE := 7936k
|
2017-10-26 22:23:17 +00:00
|
|
|
MTDPARTS := spi0.0:64k(u-boot)ro,64k(mac)ro,7936k(firmware),64k(tplink)ro,64k(art)ro
|
2017-06-30 22:28:39 +00:00
|
|
|
SUPPORTED_DEVICES := archer-c60-v1
|
2016-12-27 21:41:41 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c60-v1
|
2017-06-11 13:30:27 +00:00
|
|
|
|
2018-01-15 05:44:14 +00:00
|
|
|
define Device/archer-c60-v2
|
|
|
|
|
$(Device/archer-c60-v1)
|
|
|
|
|
DEVICE_TITLE := TP-LINK Archer C60 v2
|
|
|
|
|
BOARDNAME := ARCHER-C60-V2
|
|
|
|
|
TPLINK_BOARD_ID := ARCHER-C60-V2
|
|
|
|
|
DEVICE_PROFILE := ARCHERC60V2
|
|
|
|
|
IMAGE_SIZE := 7808k
|
|
|
|
|
MTDPARTS := spi0.0:192k(u-boot)ro,7808k(firmware),128k(tplink)ro,64k(art)ro
|
|
|
|
|
SUPPORTED_DEVICES := archer-c60-v2
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += archer-c60-v2
|
|
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/archer-c5-v1
|
|
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK Archer C5 v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := ARCHER-C5
|
|
|
|
|
DEVICE_PROFILE := ARCHERC7
|
|
|
|
|
TPLINK_HWID := 0xc5000001
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c5-v1
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/archer-c7-v1
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK Archer C7 v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := ARCHER-C7
|
|
|
|
|
DEVICE_PROFILE := ARCHERC7
|
|
|
|
|
TPLINK_HWID := 0x75000001
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c7-v1
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/archer-c7-v2
|
|
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK Archer C7 v2
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := ARCHER-C7-V2
|
|
|
|
|
DEVICE_PROFILE := ARCHERC7
|
|
|
|
|
TPLINK_HWID := 0xc7000002
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin factory-us.bin factory-eu.bin
|
|
|
|
|
IMAGE/factory-us.bin := append-rootfs | mktplinkfw factory -C US
|
|
|
|
|
IMAGE/factory-eu.bin := append-rootfs | mktplinkfw factory -C EU
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c7-v2
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/archer-c7-v2-il
|
|
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK Archer C7 v2 (IL)
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := ARCHER-C7-V2
|
|
|
|
|
DEVICE_PROFILE := ARCHERC7
|
|
|
|
|
TPLINK_HWID := 0xc7000002
|
|
|
|
|
TPLINK_HWREV := 0x494c0001
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c7-v2-il
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/tl-wdr7500-v3
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK Archer C7 v3
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := ARCHER-C7
|
|
|
|
|
DEVICE_PROFILE := ARCHERC7
|
|
|
|
|
TPLINK_HWID := 0x75000003
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wdr7500-v3
|
2017-07-25 11:32:47 +00:00
|
|
|
|
|
|
|
|
define Device/archer-c7-v4
|
|
|
|
|
$(Device/archer-cxx)
|
|
|
|
|
DEVICE_TITLE := TP-LINK Archer C7 v4
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := ARCHER-C7-V4
|
|
|
|
|
TPLINK_BOARD_ID := ARCHER-C7-V4
|
|
|
|
|
IMAGE_SIZE := 15104k
|
|
|
|
|
LOADER_TYPE := elf
|
|
|
|
|
MTDPARTS := spi0.0:128k(factory-uboot)ro,128k(u-boot)ro,1536k(kernel),13568k(rootfs),960k(config)ro,64k(art)ro,15104k@0x40000(firmware)
|
|
|
|
|
SUPPORTED_DEVICES := archer-c7-v4
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += archer-c7-v4
|
2016-12-27 21:41:41 +00:00
|
|
|
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
define Device/cpe510-520-v1
|
|
|
|
|
DEVICE_TITLE := TP-LINK CPE510/520 v1
|
2016-06-17 04:53:22 +00:00
|
|
|
DEVICE_PACKAGES := rssileds
|
2018-04-10 16:14:41 +00:00
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,64k(partition-table)ro,64k(product-info)ro,1792k(kernel),5888k(rootfs),192k(config)ro,64k(ART)ro,7680k@0x40000(firmware)
|
2016-05-22 20:57:32 +00:00
|
|
|
IMAGE_SIZE := 7680k
|
2016-05-29 00:02:19 +00:00
|
|
|
BOARDNAME := CPE510
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := CPE510
|
2016-05-23 01:17:00 +00:00
|
|
|
DEVICE_PROFILE := CPE510
|
2016-05-22 20:57:32 +00:00
|
|
|
LOADER_TYPE := elf
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | loader-kernel
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += cpe510-520-v1
|
2016-05-23 01:17:00 +00:00
|
|
|
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
define Device/cpe210-220-v1
|
|
|
|
|
$(Device/cpe510-520-v1)
|
|
|
|
|
DEVICE_TITLE := TP-LINK CPE210/220 v1
|
2016-05-29 00:02:19 +00:00
|
|
|
BOARDNAME := CPE210
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := CPE210
|
2016-05-23 01:17:00 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += cpe210-220-v1
|
2017-01-05 15:01:17 +00:00
|
|
|
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
define Device/wbs210-v1
|
|
|
|
|
$(Device/cpe510-520-v1)
|
|
|
|
|
DEVICE_TITLE := TP-LINK WBS210 v1
|
2017-01-05 15:01:17 +00:00
|
|
|
BOARDNAME := WBS210
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := WBS210
|
2017-01-05 15:01:17 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wbs210-v1
|
2017-01-05 15:01:17 +00:00
|
|
|
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
define Device/wbs510-v1
|
|
|
|
|
$(Device/cpe510-520-v1)
|
|
|
|
|
DEVICE_TITLE := TP-LINK WBS510 v1
|
2017-01-05 15:01:17 +00:00
|
|
|
BOARDNAME := WBS510
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := WBS510
|
2017-01-05 15:01:17 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += wbs510-v1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/eap120-v1
|
|
|
|
|
DEVICE_TITLE := TP-LINK EAP120 v1
|
2017-11-02 21:51:17 +00:00
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,64k(partition-table)ro,64k(product-info)ro,1536k(kernel),14336k(rootfs),192k(config)ro,64k(ART)ro,15872k@0x40000(firmware)
|
2017-06-11 13:30:27 +00:00
|
|
|
IMAGE_SIZE := 15872k
|
|
|
|
|
BOARDNAME := EAP120
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := EAP120
|
2017-06-11 13:30:27 +00:00
|
|
|
DEVICE_PROFILE := EAP120
|
|
|
|
|
LOADER_TYPE := elf
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | loader-kernel
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += eap120-v1
|
|
|
|
|
|
2018-02-06 21:08:28 +00:00
|
|
|
define Device/re355-v1
|
|
|
|
|
DEVICE_TITLE := TP-LINK RE355 v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,6016k(firmware),64k(partition-table)ro,64k(product-info)ro,1856k(config)ro,64k(art)ro
|
|
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
BOARDNAME := RE355
|
|
|
|
|
TPLINK_BOARD_ID := RE355
|
|
|
|
|
DEVICE_PROFILE := RE355
|
|
|
|
|
LOADER_TYPE := elf
|
|
|
|
|
TPLINK_HWID := 0x0
|
|
|
|
|
TPLINK_HWREV := 0
|
|
|
|
|
TPLINK_HEADER_VERSION := 1
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | tplink-v1-header
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
|
|
|
|
|
endef
|
|
|
|
|
TARGET_DEVICES += re355-v1
|
|
|
|
|
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
define Device/re450-v1
|
|
|
|
|
DEVICE_TITLE := TP-LINK RE450 v1
|
2016-12-15 19:24:37 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca988x
|
2017-11-06 22:17:24 +00:00
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,6016k(firmware),64k(partition-table)ro,64k(product-info)ro,1856k(config)ro,64k(art)ro
|
2016-12-15 19:24:37 +00:00
|
|
|
IMAGE_SIZE := 7936k
|
|
|
|
|
BOARDNAME := RE450
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := RE450
|
2016-12-15 19:24:37 +00:00
|
|
|
DEVICE_PROFILE := RE450
|
|
|
|
|
LOADER_TYPE := elf
|
2017-06-27 20:49:21 +00:00
|
|
|
TPLINK_HWID := 0x0
|
2017-07-06 16:24:37 +00:00
|
|
|
TPLINK_HWREV := 0
|
|
|
|
|
TPLINK_HEADER_VERSION := 1
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | tplink-v1-header
|
2016-12-15 19:24:37 +00:00
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
|
|
|
|
|
endef
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
TARGET_DEVICES += re450-v1
|
2016-12-15 19:24:37 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-mr6400-v1
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-MR6400 v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-net kmod-usb-net-rndis kmod-usb-serial kmod-usb-serial-option adb-enablemodem
|
|
|
|
|
BOARDNAME := TL-MR6400
|
|
|
|
|
DEVICE_PROFILE := TLMR6400
|
|
|
|
|
TPLINK_HWID := 0x64000001
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-06-11 13:30:27 +00:00
|
|
|
TARGET_DEVICES += tl-mr6400-v1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wdr3500-v1
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WDR3500 v1
|
2017-03-22 19:36:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2017-06-11 13:30:27 +00:00
|
|
|
BOARDNAME := TL-WDR3500
|
|
|
|
|
DEVICE_PROFILE := TLWDR4300
|
|
|
|
|
TPLINK_HWID := 0x35000001
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wdr3500-v1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wdr3600-v1
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/tl-wdr3500-v1)
|
2017-06-11 13:30:27 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WDR3600 v1
|
|
|
|
|
BOARDNAME := TL-WDR4300
|
|
|
|
|
TPLINK_HWID := 0x36000001
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | mktplinkfw factory -C US
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wdr3600-v1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wdr4300-v1
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/tl-wdr3600-v1)
|
2017-06-11 13:30:27 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WDR4300 v1
|
|
|
|
|
TPLINK_HWID := 0x43000001
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wdr4300-v1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wdr4300-v1-il
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/tl-wdr3500-v1)
|
2017-06-11 13:30:27 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WDR4300 v1 (IL)
|
|
|
|
|
BOARDNAME := TL-WDR4300
|
|
|
|
|
TPLINK_HWID := 0x43008001
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wdr4300-v1-il
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wdr4310-v1
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/tl-wdr4300-v1-il)
|
2017-06-11 13:30:27 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WDR4310 v1
|
|
|
|
|
TPLINK_HWID := 0x43100001
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wdr4310-v1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wdr4900-v2
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WDR4900 v2
|
2017-03-22 19:36:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
2017-06-11 13:30:27 +00:00
|
|
|
BOARDNAME := TL-WDR4900-v2
|
|
|
|
|
DEVICE_PROFILE := TLWDR4900V2
|
|
|
|
|
TPLINK_HWID := 0x49000002
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wdr4900-v2
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wdr6500-v2
|
2017-05-25 19:51:37 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
2017-06-11 13:30:27 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WDR6500 v2
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | uImage lzma
|
2017-07-06 16:10:22 +00:00
|
|
|
KERNEL_INITRAMFS := kernel-bin | patch-cmdline | lzma | uImage lzma | tplink-v1-header
|
2017-06-11 13:30:27 +00:00
|
|
|
BOARDNAME := TL-WDR6500-v2
|
|
|
|
|
DEVICE_PROFILE := TLWDR6500V2
|
|
|
|
|
TPLINK_HWID := 0x65000002
|
|
|
|
|
TPLINK_HEADER_VERSION := 2
|
2017-05-25 19:51:37 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wdr6500-v2
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/mw4530r-v1
|
|
|
|
|
$(Device/tl-wdr4300-v1)
|
|
|
|
|
DEVICE_TITLE := Mercury MW4530R v1
|
|
|
|
|
TPLINK_HWID := 0x45300001
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += mw4530r-v1
|
2017-05-25 19:51:37 +00:00
|
|
|
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
define Device/tl-wpa8630-v1
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WPA8630 v1
|
2017-03-22 19:36:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-ath10k ath10k-firmware-qca988x
|
|
|
|
|
BOARDNAME := TL-WPA8630
|
|
|
|
|
DEVICE_PROFILE := TL-WPA8630
|
|
|
|
|
TPLINK_HWID := 0x86300001
|
2016-11-07 14:37:25 +00:00
|
|
|
endef
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
TARGET_DEVICES += tl-wpa8630-v1
|
2016-11-07 14:37:25 +00:00
|
|
|
|
2017-09-25 09:38:49 +00:00
|
|
|
define Device/tl-wr1043n-v5
|
|
|
|
|
$(Device/archer-cxx)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR1043N v5
|
|
|
|
|
BOARDNAME := TL-WR1043N-v5
|
|
|
|
|
SUPPORTED_DEVICES := tl-wr1043n-v5
|
|
|
|
|
DEVICE_PROFILE := TLWR1043
|
|
|
|
|
MTDPARTS := spi0.0:128k(factory-uboot)ro,128k(u-boot)ro,15104k(firmware),128k(product-info)ro,640k(config)ro,64k(partition-table)ro,128k(logs)ro,64k(art)ro
|
|
|
|
|
IMAGE_SIZE := 15104k
|
|
|
|
|
TPLINK_BOARD_ID := TLWR1043NV5
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr1043n-v5
|
2017-09-25 09:38:49 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wr1043nd-v1
|
|
|
|
|
$(Device/tplink-8m)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR1043N/ND v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
BOARDNAME := TL-WR1043ND
|
|
|
|
|
DEVICE_PROFILE := TLWR1043
|
|
|
|
|
TPLINK_HWID := 0x10430001
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr1043nd-v1
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/tl-wr1043nd-v2
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR1043N/ND v2
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
BOARDNAME := TL-WR1043ND-v2
|
|
|
|
|
DEVICE_PROFILE := TLWR1043
|
|
|
|
|
TPLINK_HWID := 0x10430002
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr1043nd-v2
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/tl-wr1043nd-v3
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/tl-wr1043nd-v2)
|
2017-06-11 13:30:27 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WR1043N/ND v3
|
|
|
|
|
TPLINK_HWID := 0x10430003
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr1043nd-v3
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/tl-wr1043nd-v4
|
|
|
|
|
$(Device/tplink)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR1043N/ND v4
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
BOARDNAME := TL-WR1043ND-v4
|
|
|
|
|
DEVICE_PROFILE := TLWR1043
|
|
|
|
|
TPLINK_HWID := 0x10430004
|
|
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,1536k(kernel),14016k(rootfs),128k(product-info)ro,320k(config)ro,64k(partition-table)ro,128k(logs)ro,64k(ART)ro,15552k@0x20000(firmware)
|
|
|
|
|
IMAGE_SIZE := 15552k
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := TLWR1043NDV4
|
2017-07-06 16:10:22 +00:00
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | tplink-v1-header
|
2017-06-11 13:30:27 +00:00
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr1043nd-v4
|
2017-06-11 13:30:27 +00:00
|
|
|
|
|
|
|
|
define Device/tl-wr2543-v1
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR2543N/ND v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
BOARDNAME := TL-WR2543N
|
|
|
|
|
DEVICE_PROFILE := TLWR2543
|
|
|
|
|
TPLINK_HWID := 0x25430001
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | mktplinkfw sysupgrade -v 3.13.99
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | mktplinkfw factory -v 3.13.99
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr2543-v1
|
2017-06-11 13:30:27 +00:00
|
|
|
|
2016-05-22 20:57:32 +00:00
|
|
|
define Device/tl-wr710n-v1
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLE
There are currently several supported TP-Link devices without specified
version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510,
TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there
are already more than one version of them on the market.
For devices like Archer C5, which second version is based on a total
different platform, missing version number in DEVICE_TITLE (used in
menuconfig) might be misleading for users.
To make it less confusing for users and easier to maintain in future,
include version number in image name and DEVICE_TITLE for all TP-Link
devices, even if there is only one version of device at the moment.
Also, keep DEVICE_TITLE in same format for all TP-Link devices.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
Acked-by: John Crispin <john@phrozen.org>
2017-03-23 22:49:28 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WR710N v1
|
2017-03-22 19:36:22 +00:00
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := TL-WR710N
|
|
|
|
|
DEVICE_PROFILE := TLWR710
|
|
|
|
|
TPLINK_HWID := 0x07100001
|
|
|
|
|
CONSOLE := ttyATH0,115200
|
2017-07-12 17:22:51 +00:00
|
|
|
IMAGE/factory.bin := append-rootfs | mktplinkfw factory -C US
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr710n-v1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
|
|
|
|
define Device/tl-wr710n-v2.1
|
2017-06-10 17:31:54 +00:00
|
|
|
$(Device/tl-wr710n-v1)
|
2017-03-22 19:36:22 +00:00
|
|
|
DEVICE_TITLE := TP-LINK TL-WR710N v2.1
|
|
|
|
|
TPLINK_HWID := 0x07100002
|
|
|
|
|
TPLINK_HWREV := 0x00000002
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr710n-v2.1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
2017-06-11 13:30:27 +00:00
|
|
|
define Device/tl-wr810n-v1
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR810N v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2
|
|
|
|
|
BOARDNAME := TL-WR810N
|
|
|
|
|
DEVICE_PROFILE := TLWR810
|
|
|
|
|
TPLINK_HWID := 0x08100001
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr810n-v1
|
2016-10-21 09:47:15 +00:00
|
|
|
|
2017-11-10 21:18:09 +00:00
|
|
|
define Device/tl-wr810n-v2
|
|
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR810N v2
|
|
|
|
|
BOARDNAME := TL-WR810N-v2
|
|
|
|
|
DEVICE_PROFILE := TLWR810
|
|
|
|
|
TPLINK_HWID := 0x08100002
|
|
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr810n-v2
|
2017-11-10 21:18:09 +00:00
|
|
|
|
2016-05-22 20:57:32 +00:00
|
|
|
define Device/tl-wr842n-v1
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/tplink-8m)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR842N/ND v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
BOARDNAME := TL-MR3420
|
|
|
|
|
DEVICE_PROFILE := TLWR842
|
|
|
|
|
TPLINK_HWID := 0x08420001
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr842n-v1
|
2016-05-22 20:57:32 +00:00
|
|
|
|
|
|
|
|
define Device/tl-wr842n-v2
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/tplink-8mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR842N/ND v2
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
BOARDNAME := TL-WR842N-v2
|
|
|
|
|
DEVICE_PROFILE := TLWR842
|
|
|
|
|
TPLINK_HWID := 0x8420002
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr842n-v2
|
2016-05-22 20:57:32 +00:00
|
|
|
|
|
|
|
|
define Device/tl-wr842n-v3
|
2017-03-22 19:36:22 +00:00
|
|
|
$(Device/tplink-16mlzma)
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR842N/ND v3
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
BOARDNAME := TL-WR842N-v3
|
|
|
|
|
DEVICE_PROFILE := TLWR842
|
|
|
|
|
TPLINK_HWID := 0x08420003
|
2016-05-22 20:57:32 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr842n-v3
|
2016-05-22 20:57:32 +00:00
|
|
|
|
ar71xx: add support for TP-Link TL-WR902AC v1
TP-Link TL-WR902AC v1 is a pocket-size, dual-band (AC750), successor of
TL-MR3020 (both devices use very similar enclosure, in same size). New
device is based on Qualcomm QCA9531 v2 + QCA9887. FCC ID: TE7WR902AC.
Specification:
- 650/391/216 MHz (CPU/DDR/AHB)
- 1x 10/100 Mbps Ethernet
- 1x USB 2.0 (GPIO-controlled power)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz (QCA9531)
- 1T1R 5 GHz (QCA9887)
- 5x LED (GPIO-controlled), 2x button, 1x 3-pos switch
- UART pads on PCB (TP1 -> TX, TP2 -> RX, TP3 -> GND, TP4 -> 3V3, jumper
resitors are missing on TX/RX lines)
- 1x micro USB (for power only)
Flash instructions:
Use "factory" image under vendor GUI.
Recovery instructions:
This device contains tftp recovery mode inside U-Boot. You can use it to
flash LEDE (use "factory" image) or vendor firmware.
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ar71xx-generic-tl-wr902ac-v1-squashfs-factory.bin"
to "wr902acv1_un_tp_recovery.bin" and place it in tftp server dir.
3. Connect PC with LAN port, press the reset button, power up the router
and keep button pressed until WPS LED lights up.
4. Router will download file from server, write it to flash and reboot.
Root access over serial line in vendor firmware: root/sohoadmin.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-07-02 16:32:38 +00:00
|
|
|
define Device/tl-wr902ac-v1
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR902AC v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport \
|
|
|
|
|
kmod-ath10k ath10k-firmware-qca9887 -swconfig -uboot-envtools
|
|
|
|
|
BOARDNAME := TL-WR902AC-V1
|
|
|
|
|
DEVICE_PROFILE := TLWR902
|
|
|
|
|
TPLINK_BOARD_ID := TL-WR902AC-V1
|
|
|
|
|
TPLINK_HWID := 0x0
|
2017-07-06 16:24:37 +00:00
|
|
|
TPLINK_HWREV := 0
|
|
|
|
|
TPLINK_HEADER_VERSION := 1
|
ar71xx: add support for TP-Link TL-WR902AC v1
TP-Link TL-WR902AC v1 is a pocket-size, dual-band (AC750), successor of
TL-MR3020 (both devices use very similar enclosure, in same size). New
device is based on Qualcomm QCA9531 v2 + QCA9887. FCC ID: TE7WR902AC.
Specification:
- 650/391/216 MHz (CPU/DDR/AHB)
- 1x 10/100 Mbps Ethernet
- 1x USB 2.0 (GPIO-controlled power)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz (QCA9531)
- 1T1R 5 GHz (QCA9887)
- 5x LED (GPIO-controlled), 2x button, 1x 3-pos switch
- UART pads on PCB (TP1 -> TX, TP2 -> RX, TP3 -> GND, TP4 -> 3V3, jumper
resitors are missing on TX/RX lines)
- 1x micro USB (for power only)
Flash instructions:
Use "factory" image under vendor GUI.
Recovery instructions:
This device contains tftp recovery mode inside U-Boot. You can use it to
flash LEDE (use "factory" image) or vendor firmware.
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ar71xx-generic-tl-wr902ac-v1-squashfs-factory.bin"
to "wr902acv1_un_tp_recovery.bin" and place it in tftp server dir.
3. Connect PC with LAN port, press the reset button, power up the router
and keep button pressed until WPS LED lights up.
4. Router will download file from server, write it to flash and reboot.
Root access over serial line in vendor firmware: root/sohoadmin.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-07-02 16:32:38 +00:00
|
|
|
SUPPORTED_DEVICES := tl-wr902ac-v1
|
|
|
|
|
IMAGE_SIZE := 7360k
|
2017-07-06 16:24:37 +00:00
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | tplink-v1-header
|
ar71xx: add support for TP-Link TL-WR902AC v1
TP-Link TL-WR902AC v1 is a pocket-size, dual-band (AC750), successor of
TL-MR3020 (both devices use very similar enclosure, in same size). New
device is based on Qualcomm QCA9531 v2 + QCA9887. FCC ID: TE7WR902AC.
Specification:
- 650/391/216 MHz (CPU/DDR/AHB)
- 1x 10/100 Mbps Ethernet
- 1x USB 2.0 (GPIO-controlled power)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz (QCA9531)
- 1T1R 5 GHz (QCA9887)
- 5x LED (GPIO-controlled), 2x button, 1x 3-pos switch
- UART pads on PCB (TP1 -> TX, TP2 -> RX, TP3 -> GND, TP4 -> 3V3, jumper
resitors are missing on TX/RX lines)
- 1x micro USB (for power only)
Flash instructions:
Use "factory" image under vendor GUI.
Recovery instructions:
This device contains tftp recovery mode inside U-Boot. You can use it to
flash LEDE (use "factory" image) or vendor firmware.
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ar71xx-generic-tl-wr902ac-v1-squashfs-factory.bin"
to "wr902acv1_un_tp_recovery.bin" and place it in tftp server dir.
3. Connect PC with LAN port, press the reset button, power up the router
and keep button pressed until WPS LED lights up.
4. Router will download file from server, write it to flash and reboot.
Root access over serial line in vendor firmware: root/sohoadmin.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-07-02 16:32:38 +00:00
|
|
|
IMAGES += factory.bin
|
|
|
|
|
IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
|
|
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade | \
|
|
|
|
|
append-metadata | check-size $$$$(IMAGE_SIZE)
|
|
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,7360k(firmware),640k(tplink)ro,64k(art)ro
|
|
|
|
|
endef
|
2017-10-26 22:23:17 +00:00
|
|
|
TARGET_DEVICES += tl-wr902ac-v1
|
ar71xx: add support for TP-Link TL-WR902AC v1
TP-Link TL-WR902AC v1 is a pocket-size, dual-band (AC750), successor of
TL-MR3020 (both devices use very similar enclosure, in same size). New
device is based on Qualcomm QCA9531 v2 + QCA9887. FCC ID: TE7WR902AC.
Specification:
- 650/391/216 MHz (CPU/DDR/AHB)
- 1x 10/100 Mbps Ethernet
- 1x USB 2.0 (GPIO-controlled power)
- 64 MB of RAM (DDR2)
- 8 MB of FLASH
- 2T2R 2.4 GHz (QCA9531)
- 1T1R 5 GHz (QCA9887)
- 5x LED (GPIO-controlled), 2x button, 1x 3-pos switch
- UART pads on PCB (TP1 -> TX, TP2 -> RX, TP3 -> GND, TP4 -> 3V3, jumper
resitors are missing on TX/RX lines)
- 1x micro USB (for power only)
Flash instructions:
Use "factory" image under vendor GUI.
Recovery instructions:
This device contains tftp recovery mode inside U-Boot. You can use it to
flash LEDE (use "factory" image) or vendor firmware.
1. Configure PC with static IP 192.168.0.66/24 and tftp server.
2. Rename "lede-ar71xx-generic-tl-wr902ac-v1-squashfs-factory.bin"
to "wr902acv1_un_tp_recovery.bin" and place it in tftp server dir.
3. Connect PC with LAN port, press the reset button, power up the router
and keep button pressed until WPS LED lights up.
4. Router will download file from server, write it to flash and reboot.
Root access over serial line in vendor firmware: root/sohoadmin.
Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2017-07-02 16:32:38 +00:00
|
|
|
|
2017-03-08 20:10:05 +00:00
|
|
|
define Device/tl-wr942n-v1
|
|
|
|
|
DEVICE_TITLE := TP-LINK TL-WR942N v1
|
|
|
|
|
DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
|
|
|
|
|
BOARDNAME := TL-WR942N-V1
|
2017-06-27 12:48:00 +00:00
|
|
|
TPLINK_BOARD_ID := TLWR942NV1
|
2017-03-08 20:10:05 +00:00
|
|
|
DEVICE_PROFILE := TLWR942
|
|
|
|
|
IMAGE_SIZE := 14464k
|
|
|
|
|
KERNEL := kernel-bin | patch-cmdline | lzma | uImageArcher lzma
|
|
|
|
|
IMAGES := sysupgrade.bin factory.bin
|
2017-06-30 22:28:39 +00:00
|
|
|
IMAGE/sysupgrade.bin := append-rootfs | tplink-safeloader sysupgrade | \
|
|
|
|
|
append-metadata | check-size $$$$(IMAGE_SIZE)
|
2017-03-08 20:10:05 +00:00
|
|
|
IMAGE/factory.bin := append-rootfs | tplink-safeloader factory
|
2017-10-26 22:23:17 +00:00
|
|
|
MTDPARTS := spi0.0:128k(u-boot)ro,14464k(firmware),64k(product-info)ro,64k(partition-table)ro,256k(oem-config)ro,1344k(oem-vars)ro,64k(ART)ro
|
2017-06-30 22:28:39 +00:00
|
|
|
SUPPORTED_DEVICES := tl-wr942n-v1
|
2017-03-08 20:10:05 +00:00
|
|
|
endef
|
2017-12-10 22:45:20 +00:00
|
|
|
TARGET_DEVICES += tl-wr942n-v1
|