aboutsummaryrefslogtreecommitdiff
path: root/target/linux/bcm63xx/Makefile
Commit message (Collapse)AuthorAge
* bcm63xx: drop targetÁlvaro Fernández Rojas2024-03-04
| | | | | | | | | | | | BCM63xx maintainance is a PITA since there's no full Device Tree support and therefore every board needs it's own definition in board_bcm963xx.c There's no DSA support for this board and there have been very few contributions in the last years. Moreover, BCM63xx SoCs >= BCM6358 are already supported in bmips target, so any efforts to keep this target alive aren't worth the time. Let's focus the community efforts on improving bmips instead. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: mark as source-onlyÁlvaro Fernández Rojas2023-06-15
| | | | | | | | | | | | Maintaining bcm63xx is a nightmare due to the amount of devices and patches required, since every board requires an individual patch due to the lack of full device tree compatibility. Moreover, there are a lot of devices supported on this target which won't work due to not having enough resources (16M-32M of RAM and/or 4M of flash). Therefore, any development efforts should be focused on bmips and support for those devices with enough resources should be added on bmips target. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: switch to Kernel 5.15 by defaultPaul Spooren2023-03-04
| | | | | | Getting ready for the next release. Signed-off-by: Paul Spooren <mail@aparcar.org>
* bcm63xx: add linux v5.15 supportÁlvaro Fernández Rojas2022-05-20
| | | | | | | | Build system: x86_64 Build-tested: generic, smp Run-tested: generic/AR-5387un, smp/VR-3032u Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: switch to Kernel 5.10Paul Spooren2022-02-27
| | | | | | | | Bump the last missing target to Kernel 5.10. While this requires a work around to boot it will allow more people to test the new Kernel before the upcomming release. Signed-off-by: Paul Spooren <mail@aparcar.org>
* bcm63xx: add kernel 5.10 supportÁlvaro Fernández Rojas2021-02-17
| | | | | | Runtime-tested on Comtrend AR-5387un. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* target: use SPDX license identifiers on MakefilesAdrian Schmutzler2021-02-10
| | | | | | Use SPDX license tags to allow machines to check licenses. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: switch to 5.4 kernelÁlvaro Fernández Rojas2020-04-18
| | | | | | | Seems stable after 6 days of testing on some of my devices. Let's switch to 5.4 in order to get more feedback. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: use kernel 5.4 as testing kernelAdrian Schmutzler2020-04-12
| | | | | | | | | This uses 5.4 as testing kernel. Since 4.19 has not seen broad testing yet, just keep 4.14 as stable kernel until 5.4 is ready. Tested on Comtrend AR-5387un (Thanks to @Noltari). Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: remove maintainer variable from targetsPetr Štetiar2020-03-16
| | | | | | | | | | | | | There is no such role as target maintainer anymore, one should always send corresponding changes for the review and anyone from the commiters is allowed to merge them or eventually use the hand break and NACK them. Lets make it clear, that it is solely a community doing the maintenance tasks. Signed-off-by: Petr Štetiar <ynezz@true.cz> Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Piotr Dymacz <pepe2k@gmail.com>
* brcm63xx: rename target to bcm63xxAdrian Schmutzler2020-02-14
This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>