ExternalVendorCode/openwrt
1
0
Fork 0
mirror of https://github.com/openwrt/openwrt.git synced 2024-12-25 00:11:13 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
b45ff2d023
openwrt/target/linux/bcm63xx/image/bcm63xx.mk

1243 lines
31 KiB
Makefile
Raw Normal View History

brcm63xx: add support for the Actiontec R1000H gateway SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.0 Known issues: - Unable to detect 53115 switch attached to MDIO. Not supported - No support for the cable port More info on the device and the research can be found at: http://www.actiontec.com/212.html Same FCC ID as: https://wikidevi.com/wiki/Actiontec_V1000H_(Telus) Signed-off-by: Anthony Sepa <anthonysepa@yahoo.ca> [jonas.gorski: fix commit subject/message] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-02-19 18:27:36 +00:00
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
#
# BCM33XX/BCM63XX Profiles
#
treewide: gather DEVICE_VARS into one place Place DEVICE_VARS assignments at the top of the file or above Device/Default to make them easier to find. For ramips, remove redundant values already present in parent file. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-03-10 06:41:09 +00:00
DEVICE_VARS += HCS_MAGIC_BYTES HCS_REV_MIN HCS_REV_MAJ
DEVICE_VARS += BLOCK_SIZE FLASH_MB IMAGE_OFFSET
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
DEVICE_VARS += CFE_BOARD_ID CFE_EXTRAS
treewide: gather DEVICE_VARS into one place Place DEVICE_VARS assignments at the top of the file or above Device/Default to make them easier to find. For ramips, remove redundant values already present in parent file. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-03-10 06:41:09 +00:00
DEVICE_VARS += NETGEAR_BOARD_ID NETGEAR_REGION
DEVICE_VARS += REDBOOT_PREFIX
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
define Device/bcm33xx
KERNEL_INITRAMFS := kernel-bin | append-dtb | lzma | loader-lzma bin | hcs-initramfs
IMAGES :=
HCS_MAGIC_BYTES :=
HCS_REV_MIN :=
HCS_REV_MAJ :=
endef
define Device/bcm63xx
FILESYSTEMS := squashfs jffs2-64k jffs2-128k
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
KERNEL := kernel-bin | append-dtb | relocate-kernel | lzma
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
KERNEL_INITRAMFS := kernel-bin | append-dtb | lzma | loader-lzma elf
IMAGES := cfe.bin
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGE/cfe.bin := cfe-bin --pad $$$$(shell expr $$$$(FLASH_MB) / 2)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGE/cfe-4M.bin := cfe-bin --pad 2
IMAGE/cfe-8M.bin := cfe-bin --pad 4
IMAGE/cfe-16M.bin := cfe-bin --pad 8
IMAGE/cfe-bc221.bin := cfe-bin --layoutver 5
IMAGE/cfe-old.bin := cfe-old-bin
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGE/sysupgrade.bin := cfe-bin
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
BLOCK_SIZE := 0x10000
IMAGE_OFFSET :=
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 4
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID :=
brcm63xx: fix image generation with offsets/blocksizes != 64K Defer the CFE_EXTRAs evaluation to allow overriden BLOCK_SIZE and IMAGE_OFFSET take effect, and replace the unused IMAGE_SIZE with IMAGE_OFFSET in DEVICE_VARS. This fixes image generation for targets using different offsets or blocksizes. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-07-09 11:10:08 +00:00
CFE_EXTRAS = --block-size $$(BLOCK_SIZE) --image-offset $$(if $$(IMAGE_OFFSET),$$(IMAGE_OFFSET),$$(BLOCK_SIZE))
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
define Device/bcm63xx-legacy
$(Device/bcm63xx)
KERNEL := kernel-bin | append-dtb | relocate-kernel | lzma-cfe
endef
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
define Device/bcm63xx_netgear
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := NETGEAR
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES := factory.chk sysupgrade.bin
IMAGE/factory.chk := cfe-bin | netgear-chk
NETGEAR_BOARD_ID :=
NETGEAR_REGION :=
endef
define Device/bcm63xx_redboot
FILESYSTEMS := squashfs
brcm63xx: Livebox 1: relocate the kernel to fix boot Fix Image generation for the Livebox 1 - missing "relocate-kernel", wrong "LOADADDR", fix it Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-08-29 14:03:33 +00:00
KERNEL := kernel-bin | append-dtb | relocate-kernel | gzip
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
KERNEL_INITRAMFS := kernel-bin | append-dtb | lzma | loader-lzma elf
IMAGES := redboot.bin
IMAGE/redboot.bin := redboot-bin
treewide: rename IMAGE_PREFIX/IMAGE_NAME to DEVICE_IMG_* We so far had two variables IMG_PREFIX and IMAGE_PREFIX with different content. Since these names are obviously quite confusing, this patch renames the latter to DEVICE_IMG_PREFIX, as it's a device-dependent variable, while IMG_PREFIX is only (sub)target-dependent. For consistency, also rename IMAGE_NAME to DEVICE_IMG_NAME, as that's a device-dependent variable as well. Cc: Paul Spooren <mail@aparcar.org> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2021-02-22 14:55:43 +00:00
REDBOOT_PREFIX := $$(DEVICE_IMG_PREFIX)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
### Generic ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm963281tan
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 963281TAN
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES := cfe-4M.bin cfe-8M.bin cfe-16M.bin
CFE_BOARD_ID := 963281TAN
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm963281tan
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96328avng
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96328avng
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES := cfe-4M.bin cfe-8M.bin cfe-16M.bin
CFE_BOARD_ID := 96328avng
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96328avng
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96338gw
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96338GW
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 6338GW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6338
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96338gw
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96338w
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96338W
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 6338W
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6338
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96338w
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96345gw2
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96345GW2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES += cfe-bc221.bin
CFE_BOARD_ID := 96345GW2
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6345
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96345gw2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96348gw
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96348GW
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES += cfe-bc221.bin
CFE_BOARD_ID := 96348GW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96348gw
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96348gw-10
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96348GW-10
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW-10
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96348gw-10
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96348gw-11
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96348GW-11
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW-11
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96348gw-11
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96348r
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96348R
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348R
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96348r
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96358vw
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96358VW
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96358VW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96358vw
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96358vw2
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96358VW2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96358VW2
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96358vw2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96368mvngr
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96368MVNgr
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96368MVNgr
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96368mvngr
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96368mvwg
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Generic
DEVICE_MODEL := 96368MVWG
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96368MVWG
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96368mvwg
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: add support for the Actiontec R1000H gateway SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.0 Known issues: - Unable to detect 53115 switch attached to MDIO. Not supported - No support for the cable port More info on the device and the research can be found at: http://www.actiontec.com/212.html Same FCC ID as: https://wikidevi.com/wiki/Actiontec_V1000H_(Telus) Signed-off-by: Anthony Sepa <anthonysepa@yahoo.ca> [jonas.gorski: fix commit subject/message] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-02-19 18:27:36 +00:00
### Actiontec ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/actiontec_r1000h
brcm63xx: add support for the Actiontec R1000H gateway SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.0 Known issues: - Unable to detect 53115 switch attached to MDIO. Not supported - No support for the cable port More info on the device and the research can be found at: http://www.actiontec.com/212.html Same FCC ID as: https://wikidevi.com/wiki/Actiontec_V1000H_(Telus) Signed-off-by: Anthony Sepa <anthonysepa@yahoo.ca> [jonas.gorski: fix commit subject/message] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-02-19 18:27:36 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Actiontec
DEVICE_MODEL := R1000H
brcm63xx: add support for the Actiontec R1000H gateway SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.0 Known issues: - Unable to detect 53115 switch attached to MDIO. Not supported - No support for the cable port More info on the device and the research can be found at: http://www.actiontec.com/212.html Same FCC ID as: https://wikidevi.com/wiki/Actiontec_V1000H_(Telus) Signed-off-by: Anthony Sepa <anthonysepa@yahoo.ca> [jonas.gorski: fix commit subject/message] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-02-19 18:27:36 +00:00
FILESYSTEMS := squashfs
CFE_BOARD_ID := 96368MVWG
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: add support for the Actiontec R1000H gateway SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.0 Known issues: - Unable to detect 53115 switch attached to MDIO. Not supported - No support for the cable port More info on the device and the research can be found at: http://www.actiontec.com/212.html Same FCC ID as: https://wikidevi.com/wiki/Actiontec_V1000H_(Telus) Signed-off-by: Anthony Sepa <anthonysepa@yahoo.ca> [jonas.gorski: fix commit subject/message] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-02-19 18:27:36 +00:00
FLASH_MB := 32
IMAGE_OFFSET := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES) $(BRCMWL_PACKAGES)
brcm63xx: add support for the Actiontec R1000H gateway SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.0 Known issues: - Unable to detect 53115 switch attached to MDIO. Not supported - No support for the cable port More info on the device and the research can be found at: http://www.actiontec.com/212.html Same FCC ID as: https://wikidevi.com/wiki/Actiontec_V1000H_(Telus) Signed-off-by: Anthony Sepa <anthonysepa@yahoo.ca> [jonas.gorski: fix commit subject/message] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-02-19 18:27:36 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += actiontec_r1000h
brcm63xx: add support for the Actiontec R1000H gateway SOC: Broadcom BCM6368 (2 * Broadcom BMIPS4350 V3.1 / 400 MHz) Flash size: 32MB (split 16/16 dual boot) RAM size: 64MB Wireless: BCM432x 802.11a/b/g/n(pci) Ethernet: Broadcom BCM53115 USB: 1 x USB 2.0 Known issues: - Unable to detect 53115 switch attached to MDIO. Not supported - No support for the cable port More info on the device and the research can be found at: http://www.actiontec.com/212.html Same FCC ID as: https://wikidevi.com/wiki/Actiontec_V1000H_(Telus) Signed-off-by: Anthony Sepa <anthonysepa@yahoo.ca> [jonas.gorski: fix commit subject/message] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-02-19 18:27:36 +00:00
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### ADB ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/adb_a4001n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := ADB
DEVICE_MODEL := P.DG A4001N
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96328dg2x2
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += adb_a4001n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/adb_a4001n1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := ADB
DEVICE_MODEL := P.DG A4001N1
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGES += sysupgrade.bin
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 963281T_TEF
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 16
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += adb_a4001n1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: add support for ADB P.DG A4001N A-000-1A1-AX ADB P.DG A4001N A-000-1A1-AX a.k.a. Telecom Italia ADSL2+ Wi-Fi N (AGPWI) has the same PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. OpenWrt's ADB P.DG A4001N image is made for the ADB P.DG A4001N A-000-1A1-AE. It has different LEDs configuration and flash size/layout w.r.t the ADB P.DG A4001N A-000-1A1-AX. Hardware: * Board ID: 96328avng * SoC: Broadcom BCM6328 * RAM DDR2-800: 32 Mbyte - winbond W9725G6KB-25 * Serial flash: 16 Mbyte - MXIC MX25L 12845EMI-10G * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43224/5 Wireless Network Adapter (rev 01) * LEDs: 2x Power, 2x ADSL, 2x Internet, 2x Wi-Fi, 2x Service * Buttons: 1x Reset, 1x WPS (named WiFi/LED) * UART: 1x TTL 115200n8, TX NC RX, on J5 connector (short R192 and R193) NC GND NC Installation via CFE: * Stock CFE has to be overwriten with one for 96328avng boards that can upload .bin images with no signature check (cfe-A4001N-V0000_96328avng.bin) * connect a serial port to the board * Stop the boot process after power on by pressing enter * set static IP 192.168.1.2 and subnet mask 255.255.255.0 * navigate to http://192.168.1.1/ * upload the OpenWrt image file Signed-off-by: Daniele Castro <danielecastro@hotmail.it> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2019-12-02 15:13:44 +00:00
define Device/adb_pdg-a4001n-a-000-1a1-ax
$(Device/bcm63xx)
DEVICE_VENDOR := ADB
DEVICE_MODEL := P.DG A4001N A-000-1A1-AX
IMAGES += sysupgrade.bin
CFE_BOARD_ID := 96328avng
CHIP_ID := 6328
FLASH_MB := 16
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
endef
TARGET_DEVICES += adb_pdg-a4001n-a-000-1a1-ax
bcm63xx: add support for ADB P.DG A4101N A-000-1A1-AE ADB P.DG A4101N A-000-1A1-AE has a similar PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. Hardware: * Board ID: 96328avngv * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - Winbond W9751G6KB-25 * Serial flash: 16 Mbyte - Winbond 25Q128BVFG * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43225 Wireless Network Adapter (rev 23) * LEDs: 1x Power, 1x DSL, 1x Internet, 4x ETH, 1x USB, 1x WLAN, 1x WPS, 1x TEL * Buttons: 1x Reset, 1x WPS, 1x unnamed * UART: 1x TTL 115200n8, VCC RX TX GND, on J502 connector Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the cfe boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file A4101N GPIO LAYOUT: Power always on DSL GPIO483(03) Internet GPIO491(11) ETH1 GPIO505(25) ETH2 GPIO506(26) ETH3 GPIO507(27) ETH4 GPIO508(28) USB GPIO490(10) WLAN controlled by BCM43225 WPS GPIO489(09) TEL GPIO511(31) Key RESET GPIO503(23) Key WPS GPIO504(24) Key unnamed GPIO492(12) Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [Amend commit description, DTS improvements, refresh patches] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-09-09 01:21:14 +00:00
define Device/adb_pdg-a4101n-a-000-1a1-ae
$(Device/bcm63xx)
DEVICE_VENDOR := ADB
DEVICE_MODEL := P.DG A4101N A-000-1A1-AE
IMAGES += sysupgrade.bin
CFE_BOARD_ID := 96328avngv
CHIP_ID := 6328
FLASH_MB := 16
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
endef
TARGET_DEVICES += adb_pdg-a4101n-a-000-1a1-ae
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/adb_av4202n
brcm63xx: add support for Pirelli/ADB P.DG AV4202N This patch adds support for the ADB P.DG AV4202N aka Pirelli PRG AV4202N. Signed-off-by: Paul Wassi <p.wassi@gmx.at> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-23 23:24:44 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := ADB
DEVICE_MODEL := P.DG AV4202N
brcm63xx: add support for Pirelli/ADB P.DG AV4202N This patch adds support for the ADB P.DG AV4202N aka Pirelli PRG AV4202N. Signed-off-by: Paul Wassi <p.wassi@gmx.at> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-23 23:24:44 +00:00
IMAGE_OFFSET := 0x20000
CFE_BOARD_ID := 96368_Swiss_S1
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
brcm63xx: add support for Pirelli/ADB P.DG AV4202N This patch adds support for the ADB P.DG AV4202N aka Pirelli PRG AV4202N. Signed-off-by: Paul Wassi <p.wassi@gmx.at> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-23 23:24:44 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += adb_av4202n
brcm63xx: add support for Pirelli/ADB P.DG AV4202N This patch adds support for the ADB P.DG AV4202N aka Pirelli PRG AV4202N. Signed-off-by: Paul Wassi <p.wassi@gmx.at> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-23 23:24:44 +00:00
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Alcatel ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/alcatel_rg100a
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Alcatel
DEVICE_MODEL := RG100A
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96358VW2
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
BLOCK_SIZE := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += alcatel_rg100a
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Asmax ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/asmax_ar-1004g
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Asmax
DEVICE_MODEL := AR 1004g
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW-10
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += asmax_ar-1004g
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Belkin ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/belkin_f5d7633
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Belkin
DEVICE_MODEL := F5D7633
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW-10
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
BLOCK_SIZE := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += belkin_f5d7633
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Broadcom ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96318ref
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Broadcom
DEVICE_MODEL := BCM96318REF reference board
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES :=
CFE_BOARD_ID := 96318REF
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6318
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES) kmod-bcm63xx-udc
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96318ref
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm96318ref-p300
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Broadcom
DEVICE_MODEL := BCM96318REF_P300 reference board
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES :=
CFE_BOARD_ID := 96318REF_P300
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6318
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES) kmod-bcm63xx-udc
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm96318ref-p300
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm963268bu-p300
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Broadcom
DEVICE_MODEL := BCM963268BU_P300 reference board
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES :=
CFE_BOARD_ID := 963268BU_P300
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 63268
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES) kmod-bcm63xx-udc
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm963268bu-p300
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/brcm_bcm963269bhr
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Broadcom
DEVICE_MODEL := BCM963269BHR reference board
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES :=
CFE_BOARD_ID := 963269BHR
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 63268
brcm63xx: be more specific about SOC names This uses the specific SOC names for several devices where the Chip ID was used incorrectly before. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-01-05 12:14:43 +00:00
SOC := bcm63269
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES) kmod-bcm63xx-udc
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += brcm_bcm963269bhr
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### BT ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/bt_home-hub-2-a
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := BT
DEVICE_MODEL := Home Hub 2.0
DEVICE_VARIANT := A
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := HOMEHUB2A
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
BLOCK_SIZE := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += bt_home-hub-2-a
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/bt_voyager-2110
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := BT
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
DEVICE_MODEL := Voyager 2110
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := V2110
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --layoutver 5
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += bt_voyager-2110
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/bt_voyager-2500v-bb
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := BT
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
DEVICE_MODEL := Voyager 2500V
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := V2500V_BB
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --layoutver 5
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += bt_voyager-2500v-bb
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Comtrend ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_ar-5315u
brcm63xx: Add Comtrend AR-5315u support Add support for the Comtrend AR-5315u router This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: refreshed patch] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-12 10:40:22 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := AR-5315u
brcm63xx: Add Comtrend AR-5315u support Add support for the Comtrend AR-5315u router This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: refreshed patch] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-12 10:40:22 +00:00
IMAGES += sysupgrade.bin
CFE_BOARD_ID := 96318A-1441N1
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6318
brcm63xx: Add Comtrend AR-5315u support Add support for the Comtrend AR-5315u router This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: refreshed patch] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-12 10:40:22 +00:00
FLASH_MB := 16
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: Add Comtrend AR-5315u support Add support for the Comtrend AR-5315u router This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: refreshed patch] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-12 10:40:22 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_ar-5315u
brcm63xx: Add Comtrend AR-5315u support Add support for the Comtrend AR-5315u router This a BCM6318 based board, 64 MB RAM, 16 MB SPI flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: refreshed patch] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-12 10:40:22 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_ar-5381u
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := AR-5381u
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGES += sysupgrade.bin
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96328A-1241N
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 16
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_ar-5381u
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_ar-5387un
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := AR-5387un
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGES += sysupgrade.bin
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96328A-1441N1
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 16
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_ar-5387un
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_ct-536plus
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := CT-536+
DEVICE_ALT0_VENDOR := Comtrend
DEVICE_ALT0_MODEL := CT-5621
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW-11
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_ct-536plus
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_ct-5365
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := CT-5365
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348A-122
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_ct-5365
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_ct-6373
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := CT-6373
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := CT6373-1
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_ct-6373
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_vr-3025u
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := VR-3025u
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGES += sysupgrade.bin
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96368M-1541N
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
BLOCK_SIZE := 0x20000
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 32
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_vr-3025u
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_vr-3025un
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := VR-3025un
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96368M-1341N
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_vr-3025un
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_vr-3026e
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := VR-3026e
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96368MT-1341N1
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_vr-3026e
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/comtrend_wap-5813n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Comtrend
DEVICE_MODEL := WAP-5813n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96369R-1231N
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: be more specific about SOC names This uses the specific SOC names for several devices where the Chip ID was used incorrectly before. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-01-05 12:14:43 +00:00
SOC := bcm6369
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += comtrend_wap-5813n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### D-Link ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/d-link_dsl-2640b-b
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DSL-2640B
DEVICE_VARIANT := B2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := D-4P-W
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += d-link_dsl-2640b-b
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/d-link_dsl-2640u
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DSL-2640U
DEVICE_VARIANT := C1
DEVICE_ALT0_VENDOR := D-Link
DEVICE_ALT0_MODEL := DSL-2640U/BRU/C
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96338W2_E7T
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6338
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += d-link_dsl-2640u
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/d-link_dsl-2650u
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DSL-2650U
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96358VW2
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += d-link_dsl-2650u
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/d-link_dsl-274xb-c2
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DSL-2740B
DEVICE_VARIANT := C2
DEVICE_ALT0_VENDOR := D-Link
DEVICE_ALT0_MODEL := DSL-2741B
DEVICE_ALT0_VARIANT := C2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96358GW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += d-link_dsl-274xb-c2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/d-link_dsl-274xb-c3
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DSL-2740B
DEVICE_VARIANT := C3
DEVICE_ALT0_VENDOR := D-Link
DEVICE_ALT0_MODEL := DSL-2741B
DEVICE_ALT0_VARIANT := C3
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
DEVICE_DTS := bcm6358-d-link-dsl-274xb-c2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := AW4139
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += d-link_dsl-274xb-c3
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/d-link_dsl-274xb-f1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DSL-2740B
DEVICE_VARIANT := F1
DEVICE_ALT0_VENDOR := D-Link
DEVICE_ALT0_MODEL := DSL-2741B
DEVICE_ALT0_VARIANT := F1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := AW4339U
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: merge DSL-274X-F1 profiles The only difference is a field in the image tag header, so just define two images for it instead of treating them as separate devices. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-06-18 11:38:46 +00:00
IMAGES := cfe-EU.bin cfe-AU.bin
IMAGE/cfe-AU.bin := cfe-bin --signature2 "4.06.01.AUF1" --pad 4
IMAGE/cfe-EU.bin := cfe-bin --signature2 "4.06.01.EUF1" --pad 4
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(ATH9K_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += d-link_dsl-274xb-f1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
bcm63xx: Add support for D-Link DSL-2750u rev C1 This adds support for the D-Link DSL-2750u rev C1. (https://deviwiki.com/wiki/D-Link_DSL-2750U_rev_C1) It uses the same hardware as ADB P.DG A4001N. CPU: Broadcom BCM63281 (320 MHz) RAM: 32M (Winbond W9725G6JB) Flash: 8M (MXIC MX25L6445E) Ethernet: 4x 100 Mbps Wireless: 802.11b/g/n: BCM43225 USB: 1x 2.0 Flash instructions: 1. Assign static IP 192.168.1.100 to PC 2. Unplug the power source 3. Press the RESET button at the router, don't release it yet! 4. Plug the power source.Wait some seconds 5. Release the RESET button 6. Browse to http://192.168.1.1 7. Send the openwrt-bcm63xx-generic-DSL2750U-C1-squashfs-cfe.bin and wait some minutes until the firmware upgrade finish. Signed-off-by: Ahmed Naseef <naseefkm@gmail.com> [DTS improvements, proper board patch, refresh patches] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-08-18 12:22:20 +00:00
define Device/d-link_dsl-2750u-c1
$(Device/bcm63xx)
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DSL-2750U
DEVICE_VARIANT := C1
IMAGES += sysupgrade.bin
CFE_BOARD_ID := 963281TAVNG
CHIP_ID := 6328
FLASH_MB := 8
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
endef
TARGET_DEVICES += d-link_dsl-2750u-c1
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/d-link_dsl-275xb-d1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DSL-2750B
DEVICE_VARIANT := D1
DEVICE_ALT0_VENDOR := D-Link
DEVICE_ALT0_MODEL := DSL-2751
DEVICE_ALT0_VARIANT := D1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := AW5200B
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6318
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += d-link_dsl-275xb-d1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/d-link_dva-g3810bn-tl
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := D-Link
DEVICE_MODEL := DVA-G3810BN/TL
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96358VW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += d-link_dva-g3810bn-tl
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Davolink ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/davolink_dv-201amr
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Davolink
DEVICE_MODEL := DV-201AMR
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES := cfe-old.bin
CFE_BOARD_ID := DV201AMR
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += davolink_dv-201amr
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Dynalink ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/dynalink_rta770bw
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Dynalink
DEVICE_MODEL := RTA770BW
DEVICE_ALT0_VENDOR := Siemens
DEVICE_ALT0_MODEL := SE515
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES =
CFE_BOARD_ID := RTA770BW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6345
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --layoutver 5
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += dynalink_rta770bw
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/dynalink_rta770w
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Dynalink
DEVICE_MODEL := RTA770W
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES =
CFE_BOARD_ID := RTA770W
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6345
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --layoutver 5
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += dynalink_rta770w
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/dynalink_rta1025w
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Dynalink
DEVICE_MODEL := RTA1025W
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := RTA1025W_16
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --layoutver 5
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += dynalink_rta1025w
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/dynalink_rta1320
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Dynalink
DEVICE_MODEL := RTA1320
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := RTA1320_16M
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6338
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --layoutver 5
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += dynalink_rta1320
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Huawei ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/huawei_echolife-hg520v
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Huawei
DEVICE_MODEL := EchoLife HG520v
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := HW6358GW_B
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --rsa-signature "EchoLife_HG520v"
brcm63xx: be more specific about SOC names This uses the specific SOC names for several devices where the Chip ID was used incorrectly before. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-01-05 12:14:43 +00:00
SOC := bcm6359
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += huawei_echolife-hg520v
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/huawei_echolife-hg553
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Huawei
DEVICE_MODEL := EchoLife HG553
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := HW553
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --rsa-signature "EchoLife_HG553" --tag-version 7
BLOCK_SIZE := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += huawei_echolife-hg553
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/huawei_echolife-hg556a-a
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Huawei
DEVICE_MODEL := EchoLife HG556a
DEVICE_VARIANT := A
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
DEVICE_DESCRIPTION = Build firmware images for Huawei HG556a version A (Atheros)
CFE_BOARD_ID := HW556
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --rsa-signature "EchoLife_HG556a" --tag-version 8
IMAGE_OFFSET := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(ATH9K_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += huawei_echolife-hg556a-a
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/huawei_echolife-hg556a-b
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Huawei
DEVICE_MODEL := EchoLife HG556a
DEVICE_VARIANT := B
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
DEVICE_DESCRIPTION = Build firmware images for Huawei HG556a version B (Atheros)
CFE_BOARD_ID := HW556
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --rsa-signature "EchoLife_HG556a" --tag-version 8
BLOCK_SIZE := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(ATH9K_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += huawei_echolife-hg556a-b
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/huawei_echolife-hg556a-c
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Huawei
DEVICE_MODEL := EchoLife HG556a
DEVICE_VARIANT := C
brcm63xx: fix typo image/Makefile This typo was introduced in c6990347 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-05 13:42:27 +00:00
DEVICE_DESCRIPTION = Build firmware images for Huawei HG556a version C (Ralink)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := HW556
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --rsa-signature "EchoLife_HG556a" --tag-version 8
BLOCK_SIZE := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(RT28_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += huawei_echolife-hg556a-c
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/huawei_echolife-hg622
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Huawei
DEVICE_MODEL := EchoLife HG622
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGES += sysupgrade.bin
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96368MVWG_hg622
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --tag-version 7
BLOCK_SIZE := 0x20000
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 16
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(RT28_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += huawei_echolife-hg622
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/huawei_echolife-hg655b
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Huawei
DEVICE_MODEL := EchoLife HG655b
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := HW65x
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --tag-version 7
IMAGE_OFFSET := 0x20000
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(RT28_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += huawei_echolife-hg655b
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
bcm63xx: add support for Innacomm W3400V6 Innacomm W3400V6 is an xDSL B/G wireless router based on Broadcom BCM6328 SoC. Hardware: SoC: Broadcom BCM6328 CPU: BMIPS4350 V8.0, 320 MHz, 1 core Flash: SPI-NOR 8MB, MX25L6406E RAM: 64 MB Ethernet: 4x 10/100 Mbps Switch: Integrated Wireless: 802.11b/g, BCM4312 LEDs/Buttons: 9x / 2x Flash instruction, web UI: 1) Set a static IP on your computer compatible with 192.168.1.1, i.e 192.168.1.100 2) Connect the ethernet cable from your computer to the router. 3) Make sure the router is powered off. 4) Press the reset button, don't release it yet! 5) While pressing reset, power on the router. 6) Wait 10 seconds or more. Note: The power LED is red at first then turns to solid green when ready. 8) Release the reset button. 9) Browse to 192.168.1.1 10) Select .bin file. 10) Upgrade the image. 11) Wait for it to reboot. Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> [Ammend commit description, merge patches, DT improvements] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-10-09 09:04:03 +00:00
### Innacomm ###
define Device/innacomm_w3400v6
$(Device/bcm63xx)
DEVICE_VENDOR := Innacomm
DEVICE_MODEL := W3400V6
CFE_BOARD_ID := 96328ang
CHIP_ID := 6328
FLASH_MB := 8
DEVICE_PACKAGES := $(B43_PACKAGES)
endef
TARGET_DEVICES += innacomm_w3400v6
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Inteno ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/inteno_vg50
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Inteno
DEVICE_MODEL := VG50 Multi-WAN CPE
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES :=
CFE_BOARD_ID := VW6339GU
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 63268
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += inteno_vg50
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Inventel ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/inventel_livebox-1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx_redboot)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Inventel
DEVICE_MODEL := Livebox 1
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
SOC := bcm6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB1_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += inventel_livebox-1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Netgear ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/netgear_cvg834g
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm33xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := NETGEAR
DEVICE_MODEL := CVG834G
bcm63xx: image: add CVG834G CHIP_ID Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:23:10 +00:00
CHIP_ID := 3368
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
HCS_MAGIC_BYTES := 0xa020
HCS_REV_MIN := 0001
HCS_REV_MAJ := 0022
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += netgear_cvg834g
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/netgear_dg834gt-pn
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := NETGEAR
DEVICE_MODEL := DG834GT
DEVICE_ALT0_VENDOR := NETGEAR
DEVICE_ALT0_MODEL := DG834PN
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW-10
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(ATH5K_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += netgear_dg834gt-pn
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/netgear_dg834g-v4
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := NETGEAR
DEVICE_MODEL := DG834G
DEVICE_VARIANT := v4
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES :=
CFE_BOARD_ID := 96348W3
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += netgear_dg834g-v4
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/netgear_dgnd3700-v1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx_netgear)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_MODEL := DGND3700
DEVICE_VARIANT := v1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96368MVWG
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
BLOCK_SIZE := 0x20000
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
NETGEAR_BOARD_ID := U12L144T01_NETGEAR_NEWLED
NETGEAR_REGION := 1
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += netgear_dgnd3700-v1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/netgear_dgnd3800b
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx_netgear)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_MODEL := DGND3800B
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
DEVICE_DTS := bcm6368-netgear-dgnd3700-v1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96368MVWG
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
BLOCK_SIZE := 0x20000
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
NETGEAR_BOARD_ID := U12L144T11_NETGEAR_NEWLED
NETGEAR_REGION := 1
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += netgear_dgnd3800b
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/netgear_evg2000
brcm63xx: add initial support for Netgear EVG2000 This patch adds support for the Netgear EVG2000 VoIP Gateway to the bcm63xx targets. This device was not sold to the general public, but rather is/was provided by telcos to customers in Sweden, Australia, Singapore and other parts of asia. Known issues: - Unable to detect 53115 switch. This appear to be a problem with probing for the PHY using MDIO and results in error 5. Doesn't seem to be a problem with the configuration, and could use someone with experience to have a look at it. - Uses the b43 driver as using the OpenWRT/LEDE broadcom-wl driver fails to load the firmware for the 4322, so 802.11n is not supported. More info on the device and the research can be found at: https://wiki.openwrt.org/toh/netgear/evg2000 https://wikidevi.com/wiki/Netgear_EVG2000 https://github.com/Xotic750/mirror-lede/tree/evg2000 https://forum.openwrt.org/viewtopic.php?id=63950 Signed-off-by: Graham Fairweather <xotic750@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-22 22:56:23 +00:00
$(Device/bcm63xx_netgear)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_MODEL := EVG2000
brcm63xx: add initial support for Netgear EVG2000 This patch adds support for the Netgear EVG2000 VoIP Gateway to the bcm63xx targets. This device was not sold to the general public, but rather is/was provided by telcos to customers in Sweden, Australia, Singapore and other parts of asia. Known issues: - Unable to detect 53115 switch. This appear to be a problem with probing for the PHY using MDIO and results in error 5. Doesn't seem to be a problem with the configuration, and could use someone with experience to have a look at it. - Uses the b43 driver as using the OpenWRT/LEDE broadcom-wl driver fails to load the firmware for the 4322, so 802.11n is not supported. More info on the device and the research can be found at: https://wiki.openwrt.org/toh/netgear/evg2000 https://wikidevi.com/wiki/Netgear_EVG2000 https://github.com/Xotic750/mirror-lede/tree/evg2000 https://forum.openwrt.org/viewtopic.php?id=63950 Signed-off-by: Graham Fairweather <xotic750@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-22 22:56:23 +00:00
CFE_BOARD_ID := 96369PVG
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
BLOCK_SIZE := 0x20000
brcm63xx: add initial support for Netgear EVG2000 This patch adds support for the Netgear EVG2000 VoIP Gateway to the bcm63xx targets. This device was not sold to the general public, but rather is/was provided by telcos to customers in Sweden, Australia, Singapore and other parts of asia. Known issues: - Unable to detect 53115 switch. This appear to be a problem with probing for the PHY using MDIO and results in error 5. Doesn't seem to be a problem with the configuration, and could use someone with experience to have a look at it. - Uses the b43 driver as using the OpenWRT/LEDE broadcom-wl driver fails to load the firmware for the 4322, so 802.11n is not supported. More info on the device and the research can be found at: https://wiki.openwrt.org/toh/netgear/evg2000 https://wikidevi.com/wiki/Netgear_EVG2000 https://github.com/Xotic750/mirror-lede/tree/evg2000 https://forum.openwrt.org/viewtopic.php?id=63950 Signed-off-by: Graham Fairweather <xotic750@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-22 22:56:23 +00:00
NETGEAR_BOARD_ID := U12H154T90_NETGEAR
NETGEAR_REGION := 1
brcm63xx: be more specific about SOC names This uses the specific SOC names for several devices where the Chip ID was used incorrectly before. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-01-05 12:14:43 +00:00
SOC := bcm6369
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: add initial support for Netgear EVG2000 This patch adds support for the Netgear EVG2000 VoIP Gateway to the bcm63xx targets. This device was not sold to the general public, but rather is/was provided by telcos to customers in Sweden, Australia, Singapore and other parts of asia. Known issues: - Unable to detect 53115 switch. This appear to be a problem with probing for the PHY using MDIO and results in error 5. Doesn't seem to be a problem with the configuration, and could use someone with experience to have a look at it. - Uses the b43 driver as using the OpenWRT/LEDE broadcom-wl driver fails to load the firmware for the 4322, so 802.11n is not supported. More info on the device and the research can be found at: https://wiki.openwrt.org/toh/netgear/evg2000 https://wikidevi.com/wiki/Netgear_EVG2000 https://github.com/Xotic750/mirror-lede/tree/evg2000 https://forum.openwrt.org/viewtopic.php?id=63950 Signed-off-by: Graham Fairweather <xotic750@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-22 22:56:23 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += netgear_evg2000
brcm63xx: add initial support for Netgear EVG2000 This patch adds support for the Netgear EVG2000 VoIP Gateway to the bcm63xx targets. This device was not sold to the general public, but rather is/was provided by telcos to customers in Sweden, Australia, Singapore and other parts of asia. Known issues: - Unable to detect 53115 switch. This appear to be a problem with probing for the PHY using MDIO and results in error 5. Doesn't seem to be a problem with the configuration, and could use someone with experience to have a look at it. - Uses the b43 driver as using the OpenWRT/LEDE broadcom-wl driver fails to load the firmware for the 4322, so 802.11n is not supported. More info on the device and the research can be found at: https://wiki.openwrt.org/toh/netgear/evg2000 https://wikidevi.com/wiki/Netgear_EVG2000 https://github.com/Xotic750/mirror-lede/tree/evg2000 https://forum.openwrt.org/viewtopic.php?id=63950 Signed-off-by: Graham Fairweather <xotic750@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-22 22:56:23 +00:00
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### NuCom ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/nucom_r5010un-v2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := NuCom
DEVICE_MODEL := R5010UN
DEVICE_VARIANT := v2
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGES += sysupgrade.bin
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96328ang
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 16
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += nucom_r5010un-v2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: Add Observa VH4032N support Add support for the Observa Telecom VH4032N router. This is another BCM6368 router, 128 MB RAM, 32MB flash and 3 USB host ports. The wifi chip is an onboard Broadcom BCM43222. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: use gpio-hog instead of abusing ephy-reset] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-03 14:51:05 +00:00
### Observa ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/observa_vh4032n
brcm63xx: Add Observa VH4032N support Add support for the Observa Telecom VH4032N router. This is another BCM6368 router, 128 MB RAM, 32MB flash and 3 USB host ports. The wifi chip is an onboard Broadcom BCM43222. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: use gpio-hog instead of abusing ephy-reset] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-03 14:51:05 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Observa
DEVICE_MODEL := VH4032N
brcm63xx: Add Observa VH4032N support Add support for the Observa Telecom VH4032N router. This is another BCM6368 router, 128 MB RAM, 32MB flash and 3 USB host ports. The wifi chip is an onboard Broadcom BCM43222. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: use gpio-hog instead of abusing ephy-reset] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-03 14:51:05 +00:00
IMAGES += sysupgrade.bin
CFE_BOARD_ID := 96368VVW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: Add Observa VH4032N support Add support for the Observa Telecom VH4032N router. This is another BCM6368 router, 128 MB RAM, 32MB flash and 3 USB host ports. The wifi chip is an onboard Broadcom BCM43222. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: use gpio-hog instead of abusing ephy-reset] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-03 14:51:05 +00:00
BLOCK_SIZE := 0x20000
FLASH_MB := 32
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: Add Observa VH4032N support Add support for the Observa Telecom VH4032N router. This is another BCM6368 router, 128 MB RAM, 32MB flash and 3 USB host ports. The wifi chip is an onboard Broadcom BCM43222. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: use gpio-hog instead of abusing ephy-reset] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-03 14:51:05 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += observa_vh4032n
brcm63xx: Add Observa VH4032N support Add support for the Observa Telecom VH4032N router. This is another BCM6368 router, 128 MB RAM, 32MB flash and 3 USB host ports. The wifi chip is an onboard Broadcom BCM43222. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: use gpio-hog instead of abusing ephy-reset] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-12-03 14:51:05 +00:00
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Pirelli ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/pirelli_a226g
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Pirelli
DEVICE_MODEL := A226G
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := DWV-S0
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --signature2 IMAGE --tag-version 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += pirelli_a226g
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/pirelli_a226m
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Pirelli
DEVICE_MODEL := A226M
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := DWV-S0
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --signature2 IMAGE --tag-version 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += pirelli_a226m
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/pirelli_a226m-fwb
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Pirelli
DEVICE_MODEL := A226M-FWB
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := DWV-S0
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --signature2 IMAGE --tag-version 8
BLOCK_SIZE := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += pirelli_a226m-fwb
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/pirelli_agpf-s0
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Pirelli
DEVICE_MODEL := Alice Gate VoIP 2 Plus Wi-Fi AGPF-S0
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := AGPF-S0
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --signature2 IMAGE --tag-version 8
BLOCK_SIZE := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += pirelli_agpf-s0
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Sagem ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sagem_fast-2404
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Sagemcom
DEVICE_MODEL := F@st 2404
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := F@ST2404
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sagem_fast-2404
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sagem_fast-2504n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Sagemcom
DEVICE_MODEL := F@st 2504N
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := F@ST2504n
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6362
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sagem_fast-2504n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sagem_fast-2604
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Sagemcom
DEVICE_MODEL := F@st 2604
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := F@ST2604
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sagem_fast-2604
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sagem_fast-2704n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Sagemcom
DEVICE_MODEL := F@st 2704N
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := F@ST2704N
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6318
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sagem_fast-2704n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sagem_fast-2704-v2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Sagemcom
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
DEVICE_MODEL := F@st 2704
DEVICE_VARIANT := V2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := F@ST2704V2
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sagem_fast-2704-v2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: Add Sercomm AD1018 support Add support for the Sercomm AD1018 router This a BCM6328 based board, 128 MB RAM, 128 MiB NAND flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port (not soldered). The board also has an FXS chip (Si32177) connected via SPI (SS2#), without support in LEDE. Since NAND flash chips aren't still supported in brcm63xx, the support is for now added to work only with SPI flash chips. Therefore hardware modding, soldering a new SPI flash chip, is required to make the board work with LEDE (tested and working OK). The flash at dts is intentionally left without partitioning to let the user choose a NOR chip of any size (8, 16 or 32 MB). Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: renamed ad1018 to ad1018-nor to signify the modification] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-31 20:22:37 +00:00
### Sercomm ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sercomm_ad1018-nor
brcm63xx: Add Sercomm AD1018 support Add support for the Sercomm AD1018 router This a BCM6328 based board, 128 MB RAM, 128 MiB NAND flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port (not soldered). The board also has an FXS chip (Si32177) connected via SPI (SS2#), without support in LEDE. Since NAND flash chips aren't still supported in brcm63xx, the support is for now added to work only with SPI flash chips. Therefore hardware modding, soldering a new SPI flash chip, is required to make the board work with LEDE (tested and working OK). The flash at dts is intentionally left without partitioning to let the user choose a NOR chip of any size (8, 16 or 32 MB). Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: renamed ad1018 to ad1018-nor to signify the modification] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-31 20:22:37 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Sercomm
DEVICE_MODEL := AD1018
DEVICE_VARIANT := SPI flash mod
brcm63xx: Add Sercomm AD1018 support Add support for the Sercomm AD1018 router This a BCM6328 based board, 128 MB RAM, 128 MiB NAND flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port (not soldered). The board also has an FXS chip (Si32177) connected via SPI (SS2#), without support in LEDE. Since NAND flash chips aren't still supported in brcm63xx, the support is for now added to work only with SPI flash chips. Therefore hardware modding, soldering a new SPI flash chip, is required to make the board work with LEDE (tested and working OK). The flash at dts is intentionally left without partitioning to let the user choose a NOR chip of any size (8, 16 or 32 MB). Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: renamed ad1018 to ad1018-nor to signify the modification] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-31 20:22:37 +00:00
CFE_BOARD_ID := 96328avngr
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6328
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: Add Sercomm AD1018 support Add support for the Sercomm AD1018 router This a BCM6328 based board, 128 MB RAM, 128 MiB NAND flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port (not soldered). The board also has an FXS chip (Si32177) connected via SPI (SS2#), without support in LEDE. Since NAND flash chips aren't still supported in brcm63xx, the support is for now added to work only with SPI flash chips. Therefore hardware modding, soldering a new SPI flash chip, is required to make the board work with LEDE (tested and working OK). The flash at dts is intentionally left without partitioning to let the user choose a NOR chip of any size (8, 16 or 32 MB). Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: renamed ad1018 to ad1018-nor to signify the modification] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-31 20:22:37 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sercomm_ad1018-nor
brcm63xx: Add Sercomm AD1018 support Add support for the Sercomm AD1018 router This a BCM6328 based board, 128 MB RAM, 128 MiB NAND flash, with an onboard BCM43217 wifi, 4 ethernet ports and 1 USB host port (not soldered). The board also has an FXS chip (Si32177) connected via SPI (SS2#), without support in LEDE. Since NAND flash chips aren't still supported in brcm63xx, the support is for now added to work only with SPI flash chips. Therefore hardware modding, soldering a new SPI flash chip, is required to make the board work with LEDE (tested and working OK). The flash at dts is intentionally left without partitioning to let the user choose a NOR chip of any size (8, 16 or 32 MB). Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com> [jonas.gorski: renamed ad1018 to ad1018-nor to signify the modification] Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2017-08-31 20:22:37 +00:00
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### SFR ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sfr_neufbox-4-sercomm-r0
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := SFR
brcm63xx: align DTS model with Makefile and compatible Since the model string in DTS is not required to derive board name anymore, we can now align it with the model name in Makefile and the compatible. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 22:12:53 +00:00
DEVICE_MODEL := Neufbox 4
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VARIANT := Sercomm
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96358VW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
build: replace uses of OpenWrt with $(VERSION_DIST) This makes the distribution name more configurable. Signed-off-by: Felix Fietkau <nbd@nbd.name>
2017-11-08 17:40:37 +00:00
CFE_EXTRAS += --rsa-signature "$(VERSION_DIST)-$(firstword $(subst -,$(space),$(REVISION)))"
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sfr_neufbox-4-sercomm-r0
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sfr_neufbox-4-foxconn-r1
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := SFR
brcm63xx: align DTS model with Makefile and compatible Since the model string in DTS is not required to derive board name anymore, we can now align it with the model name in Makefile and the compatible. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 22:12:53 +00:00
DEVICE_MODEL := Neufbox 4
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VARIANT := Foxconn
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96358VW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
build: replace uses of OpenWrt with $(VERSION_DIST) This makes the distribution name more configurable. Signed-off-by: Felix Fietkau <nbd@nbd.name>
2017-11-08 17:40:37 +00:00
CFE_EXTRAS += --rsa-signature "$(VERSION_DIST)-$(firstword $(subst -,$(space),$(REVISION)))"
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sfr_neufbox-4-foxconn-r1
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sfr_neufbox-6-sercomm-r0
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := SFR
brcm63xx: align DTS model with Makefile and compatible Since the model string in DTS is not required to derive board name anymore, we can now align it with the model name in Makefile and the compatible. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 22:12:53 +00:00
DEVICE_MODEL := Neufbox 6
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := NB6-SER-r0
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6362
build: replace uses of OpenWrt with $(VERSION_DIST) This makes the distribution name more configurable. Signed-off-by: Felix Fietkau <nbd@nbd.name>
2017-11-08 17:40:37 +00:00
CFE_EXTRAS += --rsa-signature "$(VERSION_DIST)-$(firstword $(subst -,$(space),$(REVISION)))"
brcm63xx: be more specific about SOC names This uses the specific SOC names for several devices where the Chip ID was used incorrectly before. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-01-05 12:14:43 +00:00
SOC := bcm6361
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sfr_neufbox-6-sercomm-r0
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/sky_sr102
brcm63xx: initial support for Sky SR102 router The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. SOC: BCM63168 (BMIPS4350 V8.0 @400MHz) Flash size: 16 MiB RAM size: 128 MiB Heavily based on patch for OpenWRT Chaos Chalmer. Original patch and more info can be found at: https://openwrt.org/toh/sky/sr102 Known issues: - Wireless and ADSL modem are not working. Signed-off-by: Andrius Štikonas <andrius@stikonas.eu>
2018-07-14 21:53:47 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := SKY
DEVICE_MODEL := SR102
brcm63xx: initial support for Sky SR102 router The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. SOC: BCM63168 (BMIPS4350 V8.0 @400MHz) Flash size: 16 MiB RAM size: 128 MiB Heavily based on patch for OpenWRT Chaos Chalmer. Original patch and more info can be found at: https://openwrt.org/toh/sky/sr102 Known issues: - Wireless and ADSL modem are not working. Signed-off-by: Andrius Štikonas <andrius@stikonas.eu>
2018-07-14 21:53:47 +00:00
CFE_BOARD_ID := BSKYB_63168
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 63268
brcm63xx: initial support for Sky SR102 router The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. SOC: BCM63168 (BMIPS4350 V8.0 @400MHz) Flash size: 16 MiB RAM size: 128 MiB Heavily based on patch for OpenWRT Chaos Chalmer. Original patch and more info can be found at: https://openwrt.org/toh/sky/sr102 Known issues: - Wireless and ADSL modem are not working. Signed-off-by: Andrius Štikonas <andrius@stikonas.eu>
2018-07-14 21:53:47 +00:00
CFE_EXTRAS += --rsa-signature "$(VERSION_DIST)-$(firstword $(subst -,$(space),$(REVISION)))"
brcm63xx: be more specific about SOC names This uses the specific SOC names for several devices where the Chip ID was used incorrectly before. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2020-01-05 12:14:43 +00:00
SOC := bcm63168
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(USB2_PACKAGES)
brcm63xx: initial support for Sky SR102 router The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. SOC: BCM63168 (BMIPS4350 V8.0 @400MHz) Flash size: 16 MiB RAM size: 128 MiB Heavily based on patch for OpenWRT Chaos Chalmer. Original patch and more info can be found at: https://openwrt.org/toh/sky/sr102 Known issues: - Wireless and ADSL modem are not working. Signed-off-by: Andrius Štikonas <andrius@stikonas.eu>
2018-07-14 21:53:47 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += sky_sr102
brcm63xx: initial support for Sky SR102 router The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. SOC: BCM63168 (BMIPS4350 V8.0 @400MHz) Flash size: 16 MiB RAM size: 128 MiB Heavily based on patch for OpenWRT Chaos Chalmer. Original patch and more info can be found at: https://openwrt.org/toh/sky/sr102 Known issues: - Wireless and ADSL modem are not working. Signed-off-by: Andrius Štikonas <andrius@stikonas.eu>
2018-07-14 21:53:47 +00:00
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### T-Com ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/t-com_speedport-w-303v
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := T-Com
DEVICE_MODEL := Speedport W 303V
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES := factory.bin sysupgrade.bin
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
IMAGE/factory.bin := cfe-spw303v-bin --pad 4 | spw303v-bin | xor-image
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGE/sysupgrade.bin := cfe-spw303v-bin | spw303v-bin
CFE_BOARD_ID := 96358-502V
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += t-com_speedport-w-303v
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/t-com_speedport-w-500v
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := T-Com
DEVICE_MODEL := Speedport W 500V
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += t-com_speedport-w-500v
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
bcm63xx: add support for Technicolor TG582n Telecom Italia branded Technicolor TG582n Telecom Italia branded a.k.a. Telecom Italia ADSL2+ Wi-Fi N (AGTWI) has the same PCB as the unbranded Technicolor TG582n with LEDs connected to different GPIO PINs in active low configuration and different LED names. It has a PCB similar to the OpenWrt's ADB P.DG A4001N1 one. Hardware: * Board ID: DANT-V * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - EtronTech EM68B16CWQD-25H * Serial flash: 16 Mbyte - Spansion FL 128SAIF00 * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43227 Wireless Network Adapter (rev 30) * LEDs: 2x Power, 1x ADSL, 2x Internet, 2x Wi-Fi, 2x Service, 4x ethernet * Buttons: 1x Reset, 1x WPS (named WiFi/LED) * UART: 1x TTL 115200n8, VCC GND TX RX, on J3 connector (short R62 and R63) Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the CFE boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file PCB: |GPIO: |TG582n: |AGTWI: LED2R |488(08) |red Power |red Power LED2G |484(04) |green Power |green Power LED10R |486(06) | |missing R85 end LED LED13G |485(05) |green Ethernet |green ADSL LED11R |494(14) | |red Internet LED14G |491(11) |green Broadband |green Internet LED5R |487(07) |red Internet |red Wi-Fi LED5G |481(01) |green Internet |green Wi-Fi LED12R |498(18) | |red Service LED12G |499(19) | |green Service LED6R |482(02) |red Wi-Fi |missing R108 end LED LED6G |483(03) |green Wi-Fi |missing R107 end LED LED7R |490(10) |red WPS |missing R91 end LED LED7G |489(09) |green WPS |missing R92 end LED LED4 |508(28) |ethernet port 4 |ethernet port 4 LED3 |507(27) |ethernet port 3 |ethernet port 3 LED9 |506(26) |ethernet port 2 |ethernet port 2 LED8 |505(25) |ethernet port 1 |ethernet port 1 SW3 |503(23) |key Reset |key Reset SW5 |504(24) |key WPS |key Wi-Fi/LED SW4 |495(15) |key Wi-Fi |missing R127 end key SW6 |493(13) | |missing R171 end key SW1 |492(12) | |missing R1 end key Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [DT fixes, base-files fixes and device variant] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-09-08 15:16:06 +00:00
### Technicolor ###
bcm63xx: add support for Technicolor TG582n Technicolor TG582n has a similar PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. Hardware: * Board ID: DANT-1 * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - Winbond W9751G6KB-25 * Serial flash: 16 Mbyte - MXIC MX25L6445EMI * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43227 Wireless Network Adapter (rev 30) * LEDs: 2x Power, 1x Ethernet, 1x Broadband, 2x Wi-Fi, 2x WPS, 4x ethernet * Buttons: 1x Reset, 1x WPS, 1x WiFi * UART: 1x TTL 115200n8, VCC GND TX RX, on J3 connector (short R62 and R63) Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the CFE boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file PCB: |GPIO: |TG582n: LED2R |488(08) |red Power LED2G |484(04) |green Power LED10R |486(06) | LED13G |485(05) |green Ethernet LED11R |494(14) | LED14G |491(11) |green Broadband LED5R |487(07) |red Internet LED5G |481(01) |green Internet LED12R |498(18) | LED12G |499(19) | LED6R |482(02) |red Wi-Fi LED6G |483(03) |green Wi-Fi LED7R |490(10) |red WPS LED7G |489(09) |green WPS LED4 |508(28) |ethernet port 4 LED3 |507(27) |ethernet port 3 LED9 |506(26) |ethernet port 2 LED8 |505(25) |ethernet port 1 SW3 |503(23) |key Reset SW5 |504(24) |key WPS SW4 |495(15) |key Wi-Fi SW6 |493(13) | SW1 |492(12) | Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [Fix base-files, refresh patch] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-09-10 19:14:11 +00:00
define Device/technicolor_tg582n
$(Device/bcm63xx)
DEVICE_VENDOR := Technicolor
DEVICE_MODEL := TG582n
IMAGES += sysupgrade.bin
CFE_BOARD_ID := DANT-1
CHIP_ID := 6328
FLASH_MB := 16
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
endef
TARGET_DEVICES += technicolor_tg582n
bcm63xx: add support for Technicolor TG582n Telecom Italia branded Technicolor TG582n Telecom Italia branded a.k.a. Telecom Italia ADSL2+ Wi-Fi N (AGTWI) has the same PCB as the unbranded Technicolor TG582n with LEDs connected to different GPIO PINs in active low configuration and different LED names. It has a PCB similar to the OpenWrt's ADB P.DG A4001N1 one. Hardware: * Board ID: DANT-V * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - EtronTech EM68B16CWQD-25H * Serial flash: 16 Mbyte - Spansion FL 128SAIF00 * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43227 Wireless Network Adapter (rev 30) * LEDs: 2x Power, 1x ADSL, 2x Internet, 2x Wi-Fi, 2x Service, 4x ethernet * Buttons: 1x Reset, 1x WPS (named WiFi/LED) * UART: 1x TTL 115200n8, VCC GND TX RX, on J3 connector (short R62 and R63) Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the CFE boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file PCB: |GPIO: |TG582n: |AGTWI: LED2R |488(08) |red Power |red Power LED2G |484(04) |green Power |green Power LED10R |486(06) | |missing R85 end LED LED13G |485(05) |green Ethernet |green ADSL LED11R |494(14) | |red Internet LED14G |491(11) |green Broadband |green Internet LED5R |487(07) |red Internet |red Wi-Fi LED5G |481(01) |green Internet |green Wi-Fi LED12R |498(18) | |red Service LED12G |499(19) | |green Service LED6R |482(02) |red Wi-Fi |missing R108 end LED LED6G |483(03) |green Wi-Fi |missing R107 end LED LED7R |490(10) |red WPS |missing R91 end LED LED7G |489(09) |green WPS |missing R92 end LED LED4 |508(28) |ethernet port 4 |ethernet port 4 LED3 |507(27) |ethernet port 3 |ethernet port 3 LED9 |506(26) |ethernet port 2 |ethernet port 2 LED8 |505(25) |ethernet port 1 |ethernet port 1 SW3 |503(23) |key Reset |key Reset SW5 |504(24) |key WPS |key Wi-Fi/LED SW4 |495(15) |key Wi-Fi |missing R127 end key SW6 |493(13) | |missing R171 end key SW1 |492(12) | |missing R1 end key Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [DT fixes, base-files fixes and device variant] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-09-08 15:16:06 +00:00
define Device/technicolor_tg582n-telecom-italia
$(Device/bcm63xx)
DEVICE_VENDOR := Technicolor
DEVICE_MODEL := TG582n
DEVICE_VARIANT := Telecom Italia
IMAGES += sysupgrade.bin
CFE_BOARD_ID := DANT-V
CHIP_ID := 6328
FLASH_MB := 16
DEVICE_PACKAGES := $(USB2_PACKAGES) $(B43_PACKAGES)
endef
TARGET_DEVICES += technicolor_tg582n-telecom-italia
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Tecom ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/tecom_gw6000
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Tecom
DEVICE_MODEL := GW6000
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(BRCMWL_PACKAGES) $(USB1_PACKAGES)
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += tecom_gw6000
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/tecom_gw6200
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Tecom
DEVICE_MODEL := GW6200
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --rsa-signature "$(shell printf '\x99')"
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(BRCMWL_PACKAGES) $(USB1_PACKAGES)
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += tecom_gw6200
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### Telsey ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/telsey_cpva502plus
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Telsey
DEVICE_MODEL := CPVA502+
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := CPVA502+
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: CPVA502+: fix image generation Fix typo, erase pointless option and allow to build the image. Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com>
2017-02-14 15:36:55 +00:00
CFE_EXTRAS += --signature "Telsey Tlc" --signature2 "99.99.999"
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += telsey_cpva502plus
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/telsey_cpva642
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Telsey
DEVICE_MODEL := CPVA642-type (CPA-ZNTE60T)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := CPVA642
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6358
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --signature "Telsey Tlc" --signature2 "99.99.999" --second-image-flag "0"
brcm63xx: add sysupgrade images Some devices require padded images in order to prevent CFE from flashing them to the wrong offset. For small flashes (4/8) this is no big deal, but for larger flashes (16/32) this implies 8 and 16 MB images, which is way too large and some devices aren't capable of flashing them through sysupgrade. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 11:53:45 +00:00
FLASH_MB := 8
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(RT63_PACKAGES) $(USB2_PACKAGES)
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += telsey_cpva642
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/telsey_magic
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := Alice
DEVICE_MODEL := W-Gate
DEVICE_ALT0_VENDOR := Telsey
DEVICE_ALT0_MODEL := MAGIC
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES :=
CFE_BOARD_ID := MAGIC
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(RT63_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += telsey_magic
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### TP-Link ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/tp-link_td-w8900gb
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := TP-Link
DEVICE_MODEL := TD-W8900GB
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW-11
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --rsa-signature "$(shell printf 'PRID\x89\x10\x00\x02')"
IMAGE_OFFSET := 0x20000
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += tp-link_td-w8900gb
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### USRobotics ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/usrobotics_usr9108
bcm63xx: stop using legacy lzma for all devices BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-06-03 07:00:09 +00:00
$(Device/bcm63xx-legacy)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := USRobotics
brcm63xx: align DTS model with Makefile and compatible Since the model string in DTS is not required to derive board name anymore, we can now align it with the model name in Makefile and the compatible. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 22:12:53 +00:00
DEVICE_MODEL := USR9108
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
CFE_BOARD_ID := 96348GW-A
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6348
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES) $(USB1_PACKAGES)
brcm63xx: do not build images for 16 MiB RAM devices by default OpenWrt will run out of RAM while booting with the default package set, so let's not provide images that will likely fail. They can still be built manually through source or IB if needed. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2019-08-16 10:24:13 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += usrobotics_usr9108
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
### ZyXEL ###
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
define Device/zyxel_p870hw-51a-v2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
$(Device/bcm63xx)
brcm63xx: split up DEVICE_TITLE DEVICE_TITLE is split up into DEVICE_VENDOR, DEVICE_MODEL and DEVICE_VARIANT Uses DEVICE_ALT* variables for alternative vendor/retailer names. Signed-off-by: Moritz Warning <moritzwarning@web.de>
2019-09-11 19:15:01 +00:00
DEVICE_VENDOR := ZyXEL
DEVICE_MODEL := P870HW-51a
DEVICE_VARIANT := v2
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
IMAGES := factory.bin
IMAGE/factory.bin := cfe-bin | zyxel-bin
CFE_BOARD_ID := 96368VVW
bcm63xx: image: rename CFE_CHIP_ID to CHIP_ID Rename CFE_CHIP_ID to a generic name that doesn't involve CFE. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2020-05-20 07:21:34 +00:00
CHIP_ID := 6368
brcm63xx: simplify block size and image offset options Instead of having CFE_EXTRAS for every device that need specific block sizes and image offset, let's define a couple of vars which can be customized for each device. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-06-21 12:17:02 +00:00
CFE_EXTRAS += --rsa-signature "ZyXEL" --signature "ZyXEL_0001"
brcm63xx: remove unneeded line break for DEVICE_PACKAGES In brcm63xx image Makefile DEVICE_PACKAGE definitions are split into multiple lines with no apparent need. Merge them into one line to increase readability and maintainability. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-30 19:37:35 +00:00
DEVICE_PACKAGES := $(B43_PACKAGES)
bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAM Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2020-02-28 11:00:29 +00:00
DEFAULT := n
brcm63xx: move profiles definitions to image/Makefile This switches brcm63xx to the new profile definition system in image/Makefile Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-05-24 19:09:19 +00:00
endef
brcm63xx: use more systematic names for image and DTS files This changes brcm63xx target to achieve consistency between image names, device nodes names, compatible, DTS name and device name as much as possible. As with other targets, having consistent names is supposed to make life easier for developers and reduces the number of "variables" in the system. In particular, applying the DTS scheme will make it easier to find the correct file and architecture. DTS files are named based on the increasingly common soc-vendor-model scheme, using hyphens for separation as this seems to be the kernel way. Since the compatible is not used at the moment, I took the chance to also align them with this patch. For the SOC, the already existing CFE_CHIP_ID can be exploiting for all but two devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
2019-12-29 00:55:54 +00:00
TARGET_DEVICES += zyxel_p870hw-51a-v2
Reference in New Issue Copy Permalink