We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CirnOS currently can only run on the Pi Zero family and the original Raspberry Pi, which only makes up a fraction of the total Raspberry Pi users.
It should be possible to modify the vectors.s, macros.h, loader and build.sh files to create builds of CirnOS that can run on the other models.
To build for the different models, separate scripts should be available such as build-rpi.sh,build-rpi2.sh, and build-zero.sh etc ...
build-rpi.sh
build-rpi2.sh
build-zero.sh
The text was updated successfully, but these errors were encountered:
I will work on this issue.
Sorry, something went wrong.
What is the difference between start.elf and start2.elf on rbpi3b+? What about the bootcode.bin?
start.elf
start2.elf
bootcode.bin
Don't they both load kernel.img and invoke _start aka ENTRY(_start) in the linker.ld (if present, else its default)?
kernel.img
_start
ENTRY(_start)
linker.ld
No branches or pull requests
CirnOS currently can only run on the Pi Zero family and the original Raspberry Pi, which only makes up a fraction of the total Raspberry Pi users.
It should be possible to modify the vectors.s, macros.h, loader and build.sh files to create builds of CirnOS that can run on the other models.
To build for the different models, separate scripts should be available such as
build-rpi.sh
,build-rpi2.sh
, andbuild-zero.sh
etc ...The text was updated successfully, but these errors were encountered: