| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | bcm63xx: lzma-loader: allow bigger ramdisks | Álvaro Fernández Rojas | 2020-06-03 | 1 | -3/+4 |
| | | | | | | | | | | | | | | | | | Some (older) CFEs are loaded at 0x80401000 and ramdisks are loaded at 0x80010000, which means that ramdisk size limit is 0x3F1000 (almost 4M). Therefore, current ramdisks (~4MB) are overwritting CFE in these devices, which results in a crash. This commit changes the address where ramdisks are loaded to 0x80a00000, which is the same address where kernel is loaded when booting from the flash. Therefore, lzma-loader will now be loaded at 0x80a00000, but it will still decompress the kernel at 0x80010000. Tested with huawei,hg556a-b, which has its CFE loaded at 0x80401000. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> | ||||
| * | bcm63xx: lzma-loader: rely on CHIP_ID for UART address | Álvaro Fernández Rojas | 2020-05-20 | 3 | -82/+8 |
| | | | | | | | | | lzma-loader uart output wasn't working on BCM3380/BCM6362 because these SoCs have the same processor ID. Let's use CHIP_ID for establishing the UART base address. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> | ||||
| * | bcm63xx: lzma-loader: remove unused definitions | Álvaro Fernández Rojas | 2020-05-20 | 1 | -12/+0 |
| | | | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> | ||||
| * | brcm63xx: rename target to bcm63xx | Adrian Schmutzler | 2020-02-14 | 17 | -0/+1889 |
| 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> | |||||
 |
index : openwrt/upstream | |
| upstream openwrt | James |
| aboutsummaryrefslogtreecommitdiffstats |