diff options
| author | Rafał Miłecki <rafal@milecki.pl> | 2021-11-03 18:12:05 +0100 |
|---|---|---|
| committer | Rafał Miłecki <rafal@milecki.pl> | 2021-12-13 14:33:07 +0100 |
| commit | 027dd3c50bd5f9912b28203e56ae4a21fe266739 (patch) | |
| tree | d69b7955f767e2009747c8ba955ad97cd4cadd34 /README.md | |
| parent | 2c1f27bf4bb2b2a90a326c2ae75ac5bdc6b47074 (diff) | |
| download | upstream-027dd3c50bd5f9912b28203e56ae4a21fe266739.tar.gz upstream-027dd3c50bd5f9912b28203e56ae4a21fe266739.tar.bz2 upstream-027dd3c50bd5f9912b28203e56ae4a21fe266739.zip | |
bcm4908: start work on images for devices using U-Boot
New BCM4908 family based routers will use U-Boot bootloader. That will
require using a totally different firmware format. Kernel has to be put
in a FIT image.
OpenWrt has some helpers for generating .its files but they don't fit
BCM4908 requirements and there is no simple way of extending any of
them. The best solution seems to be storing an .its template.
BCM4908 bootfs may:
1. contain extra binaries (other than kernel & DTB)
2. include multiple DTB files
3. store device specific U-Boot configurations with custom properties
Such setups are too complex to generate using shell script. Raw .its
file on the other hand seems quire clean & reasonable.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
(cherry picked from commit a02c971dff934a11ddadf7ffd850dabcab5a3cdf)
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions