-
Notifications
You must be signed in to change notification settings - Fork 2k
configtxt/boot: Update arm_64bit flag #3903
New issue
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
Changes from 3 commits
e6c8979
4270c31
4835557
6349bd0
e82addc
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -25,13 +25,34 @@ The Raspberry Pi 5 firmware defaults to loading `kernel_2712.img` because this i | |
|
|
||
| === `arm_64bit` | ||
|
|
||
| NOTE: This flag has been removed from Raspberry Pi 5, as Raspberry Pi 5 only supports a 64-bit kernel. | ||
|
|
||
| If set to 1, the kernel will be started in 64-bit mode. Setting to 0 selects 32-bit mode. | ||
|
|
||
| In 64-bit mode, the firmware will choose an appropriate kernel (e.g. `kernel8.img`), unless there is an explicit `kernel` option defined, in which case that is used instead. | ||
|
|
||
| Defaults to 1 on Pi 4s (Pi 4B, Pi 400, CM4 and CM4S), and 0 on all other platforms. However, if the name given in an explicit `kernel` option matches one of the known kernels then `arm_64bit` will be set accordingly. | ||
| Defaults to 1 on Raspberry Pi 4, 400 and Compute Module 4, 4S platforms. Defaults to 0 on all other platforms. However, if the name given in an explicit `kernel` option matches one of the known kernels then `arm_64bit` will be set accordingly. | ||
|
|
||
| 64-bit kernels come in the following forms: | ||
|
|
||
| * uncompressed image files | ||
| * gzip archives of an image | ||
|
Comment on lines
+37
to
+38
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I wonder if we should remove the plural from these two lines, given that you'll only ever be using one kernel at any given time? And IMHO "archive" usually implies that there's more than one file inside the archive, so perhaps this could be simplified too? (so "uncompressed image file" and "gzip-compressed image file" ?) |
||
|
|
||
| Both forms may use the `img` file extension; the bootloader recognizes archives using signature bytes at the start of the file. | ||
|
|
||
| The following Raspberry Pi models support this flag: | ||
|
|
||
| * 2B rev 1.2 | ||
| * 3 | ||
| * 3+ | ||
| * 4 | ||
| * 400 | ||
| * Zero 2 W | ||
| * Compute Module 3 | ||
| * Compute Module 3+ | ||
| * Compute Module 4 | ||
nathan-contino marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| NOTE: 64-bit kernels may be uncompressed image files or a gzip archive of an image (which can still be called kernel8.img; the bootloader will recognize the archive from the signature bytes at the beginning). The 64-bit kernel will only work on the Raspberry Pi 3, 3+, 4, 400, Zero 2 W and 2B rev 1.2, and Raspberry Pi Compute Modules 3, 3+ and 4. Raspberry Pi 5 only supports a 64-bit kernel, so this parameter has been removed for that device. | ||
| Later models, such as Raspberry Pi 5, _only_ support the 64-bit kernel. Such models do not support this flag. | ||
|
|
||
| === `ramfsfile` | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.