Timeline for How does the pi know which kernel to load?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2022 at 19:52 | comment | added | Marc Compere | these threads have been very constructive and right on point, IMO. Understanding how these devices work is difficult and general discussion on options and limitations is super helpful. | |
| Jan 30, 2017 at 16:54 | comment | added | SiKing | I think we are both saying the same thing. I was just trying to clarify my answer. Maybe I failed. Sorry. | |
| Jan 30, 2017 at 6:42 | comment | added | Milliways | @SiKing You are also NOT answering the actual question "How does the system know which to load" NOT what other methods can be used to load kernels. | |
| Jan 30, 2017 at 6:40 | comment | added | Milliways |
@SiKing I don't understand why you are deliberately misinterpreting my answer. I said the kernel option "is NOT used by normal images" NOT that it couldn't be done. This is easily verified by looking at config.txt in any standard image.
|
|
| Jan 30, 2017 at 5:49 | comment | added | SiKing | FYI: I tried a small experiment to verify my answer. See my update. | |
| Jan 24, 2017 at 3:45 | history | edited | Milliways | CC BY-SA 3.0 |
Added link Raspberry Pi boot modes
|
| Jan 24, 2017 at 0:09 | comment | added | SiKing | From your link, I read that completely differently. "Second stage bootloader (bootcode.bin) - This is used to retrieve the GPU firmware from the SD card, program the firmware, then start the GPU." Reading further: "User code - This can be one of any number of binaries. By default, it is the Linux kernel (usually named kernel.img), but it can also be another bootloader (e.g. U-Boot), or a bare-bones application." | |
| Jan 23, 2017 at 23:57 | history | answered | Milliways | CC BY-SA 3.0 |