aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm27xx/patches-5.4/950-0018-Register-the-clocks-early-during-the-boot-process-so.patch
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2022-07-20 13:47:05 +0200
committerRafał Miłecki <rafal@milecki.pl>2022-09-02 12:24:16 +0200
commitcc9c72529cdae95d03afdc6a52b9a24f6dedca90 (patch)
tree701d498bba165f8a391e40ab416130bdd3d7ea47 /target/linux/bcm27xx/patches-5.4/950-0018-Register-the-clocks-early-during-the-boot-process-so.patch
parent28ab4f395541ad4b969879042f58fd19d13a596a (diff)
downloadupstream-cc9c72529cdae95d03afdc6a52b9a24f6dedca90.tar.gz
upstream-cc9c72529cdae95d03afdc6a52b9a24f6dedca90.tar.bz2
upstream-cc9c72529cdae95d03afdc6a52b9a24f6dedca90.zip
bcm4908: build bootfs image per-SoC
In theory we could have just 1 bootfs image for all devices as each device has its own entry in the "configurations" node. It doesn't work well with default configuration though. If something goes wrong U-Boot SPL can be interrupted (by pressing A) to enter its minimalistic menu. It allows ignoring boardid. In such case bootfs default configuration is used. For above reason each SoC family (BCM4908, BCM4912) should have its own bootfs built. It allows each of them to have working default configuration. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 6ae2f7ff4737ec8dbec026fc6c02f7d1850b521c)
Diffstat (limited to 'target/linux/bcm27xx/patches-5.4/950-0018-Register-the-clocks-early-during-the-boot-process-so.patch')
0 files changed, 0 insertions, 0 deletions