fbos/test/test_dt.c, branch mainA RISC-V operating system devoted to running fizz/buzz processes.
https://git.mssola.com/os/fbos/atom?h=main2024-11-26T20:43:54ZShow the detected machine model2024-11-26T20:43:54ZMiquel Sabaté Solàmikisabate@gmail.com2024-11-26T20:43:54Zurn:sha1:87d1a2597ceedd03a7d4005db1bf82b72b423a18
Originally I was planning to detect the machine model just in case we
needed to do workaround for special cases. But since apparently even
VisionFive2 brings its own CPU frequency base on DT, this is not even
needed. Hence, fetching the model is now a cool message being shown on
boot.
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
test: Add a DT test for a VisionFive2 board2024-11-26T20:42:50ZMiquel Sabaté Solàmikisabate@gmail.com2024-11-26T20:42:50Zurn:sha1:eec442be4d2dd0a1630a820ee43220e635450aa7
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
dt: Fetch the CPU frequency as well2024-11-26T12:59:54ZMiquel Sabaté Solàmikisabate@gmail.com2024-11-26T12:59:54Zurn:sha1:7870d56b155c2be73cdacfba94eeb893cd55628e
If the 'timebase-frequency' property is available under the 'cpus' node
from the DTB blob, it makes sense to try to fetch this value from there
instead of hardcoding it. For other use-cases, where this information is
not available through DT (e.g. ACPI on the VisionFive2 board), we will
have to hardcode it with a default value even if it's not the proper
one.
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>
Fetch the initrd address from the DTB blob2024-11-20T10:43:08ZMiquel Sabaté Solàmikisabate@gmail.com2024-11-20T10:43:08Zurn:sha1:fb9627cc985912a57de8b4bedc98991e290e4075
The kernel entry has a pointer to the DTB blob as a parameter. From this
pointer we can parse the the DTB blob to find the properties
"chosen->linux,initrd-start" and "chosen->linux,initrd-start". These
properties are guaranteed to have 64-bit addresses which point where the
initrd is in memory, which we need to fetch the binaries to be loaded.
Signed-off-by: Miquel Sabaté Solà <mikisabate@gmail.com>