3 ms·
the rpi-open-firmware codebase is going the route of doing as little as possible on the VPU, and giving the arm control fairly early i found that a bit limitin
by cleverca22 4y ago
the rpi-open-firmware codebase is going the route of doing as little as possible on the VPU, and giving the arm control fairly early
i found that a bit limiting, with the lack of threads/drivers/modularity
thats why i ported little-kernel, to get the same level of features threadx likely offered, and then be able to expand the feature-set far more
with the lk-overlay codebase, you can drive the 2d and 3d cores from the VPU
you can output ntsc or vga video
you can turn on the arm core and boot linux
and you can map /dev/fb0 on the video output
and there are various cpu-independent features in LK like tga image decoding