openwrt/upstream - upstream openwrt

	Commit message (Collapse)	Author	Age	Files	Lines
*	bcm4908: enable Netgear R8000P bootloader image	Rafał Miłecki	2021-04-08	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This enables building BCM4908 "raw" image that can be flashed using bootloader web UI. It requires serial console access & stopping booting by the "Press any key to stop auto run". It's easy to build vendor like CHK image but it can't be safely flashed using vendor UI at this point. Netgear implements method called "NAND incremental flashing" that doesn't seem to flash bootfs partition as provided. Above method seems to update vmlinux.lz without updating 94908.dtb. It prevents OpenWrt kernel from booting due to incomplete DTB file. Full Netgear R8000P support can be enabled after finding a way to make vendor firmware flash OpenWrt firmware including the 94908.dtb update. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit d92a9c97bf3700e90af1d3c9157502af660365c0)
*	bcm4908: enable target & Asus GT-AC5300 image	Rafał Miłecki	2021-04-08	1	-0/+2
\| \| \| \| \| \| \| \| \| \|	OpenWrt was succesfully tested on the GT-AC5300 model. It's possible to: 1. Install OpenWrt using vendor UI 2. Perform UBI aware sysupgrade 3. Install vendor firmware using OpenWrt sysupgrade Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 5e78cb9b85a045f436abf6a03aa5c774d30e1090)
*	bcm4908: fix Netgear R8000P image	Rafał Miłecki	2021-04-08	1	-2/+5
\| \| \| \| \| \| \|	Use vendor format to allow flashing using Negear UI. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit f2c8c62d98f2137d8af896e56d5e29759cf48715)
*	bcm4908: pad firmware image bootfs JFFS2 partition to 8 MiB	Rafał Miłecki	2021-04-08	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	This way MTD "bootfs" partition will be always 8+ MiB. This should be enough for any custom / future firmware to fit its bootfs (e.g. big kernel) without having to repertition whole flash. That way we can preserve UBI and its erase counters during sysupgrade. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit ca9b1f15c424d68af0f372c37c8eee81b36ee7e1)
*	bcm4908: rename bootfs dummy file to the 1-openwrt	Rafał Miłecki	2021-04-08	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \|	The purpose of that dummy file is to make CFE work properly with OpenWrt bootfs. CFE for some reason ignores JFFS2 files with ino 0. Rename it to 1-openwrt so: 1. It's consistent with bcm63xx 2. It's OpenWrt specific so sysupgrade can distinguish it from vendor images Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 880c8b44223c9cbce3dd14da78c33676c6f1a8a6)
*	bcm4908: prepare to support TP-Link Archer C2300 V1	Rafał Miłecki	2021-03-17	3	-0/+11
\| \| \| \| \| \| \| \| \| \| \|	It's a BCM4906 based device (2 CPU cores). It has 512 MiB of RAM, 4 LAN ports, 1 WAN port, 2 USB ports, NAND flash. WiFi unknown at this point. Flashing is possible using CFE only, proper image will be worked on later. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 8d24da14702b8da820bf2e3952d5691f77136018)
*	bcm4908: sort and wrap build recipes	Adrian Schmutzler	2021-01-27	1	-12/+16
\| \| \| \| \| \| \| \| \| \|	This sorts the Build recipes alphabetically, wraps some long lines and moves the DEVICE_VARS to the top like common on several other targets. Cc: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
*	bcm4908: build valid Asus GT-AC5300 firmware image	Rafał Miłecki	2021-01-22	1	-1/+11
\| \| \| \| \| \|	Insert Asus specific tail that is required for image identification. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
*	bcm4908: append UBI with rootfs to device images	Rafał Miłecki	2021-01-21	1	-3/+4
\| \| \| \| \| \|	Also enable UBI kernel support. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
*	bcm4908: build flashable & bootable firmware images	Rafał Miłecki	2021-01-21	5	-0/+23
\| \| \| \| \| \| \| \| \| \| \| \| \|	BCM4908 bootloader requires firmware with JFFS2 image containing: 1. cferam.000 2. 94908.dtb 3. vmlinux.lz 4. device custom files cferam.000 can be obtained from the bcm63xx-cfe repository. device custom files are stored in images dir. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
*	bcm4908: prepend kernel images with a custom header	Rafał Miłecki	2021-01-15	1	-2/+7
\| \| \| \| \| \|	It's required for CFE to accept kernel. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
*	bcm4908: initial work on the Broadcom BCM4908 target	Rafał Miłecki	2021-01-12	1	-0/+39
	BCM4906, BCM4908 and BCM49408 are SoCs with 64 bit ARMv8 B53 CPUs. Upstream Linux is slowly getting support for that SoCs family so it makes sense to add target for it. This prepares initial support for: 1. Asus GT-AC5300 BCM4908 based device (4 CPUs) with 1024 MiB RAM, NAND, 8 LAN ports. 2. Netgear R8000P BCM4906 based device (2 CPUs) with 512 MiB RAM, NAND, 4 LAN ports. Flashing info will come later as we learn how to generate proper images. It isn't usable yet (it only produces a bootable kernel) so "source-only" is used. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>