Update bcm2712.adoc #4082
Closed
Update bcm2712.adoc #4082
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Push to production
Push to production
Push to productions
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to Production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Push to production
Release latest to production
Release latest changes to production
Roll out latest changes to production
Roll out latest changes to production
Deploy latest improvements to production
Roll out latest changes to production
Roll out latest changes, including Pico C SDK 2.1.1 API docs, to production
Deploy to production
roll out latest changes to production
Deploy to production
Deploy to production
Deploy to production
Deploy to production
Deploy to production
tdewey-rpi
reviewed
Apr 28, 2025
tdewey-rpi
reviewed
Apr 28, 2025
lurch
reviewed
Apr 28, 2025
lurch
reviewed
Apr 28, 2025
lurch
reviewed
Apr 28, 2025
lurch
reviewed
Apr 28, 2025
|
|
||
| WARNING: The list above was correct as of April 2025 but may have been superceded. You should use `lscpu` on your Raspberry Pi to get up to date information. This is especially important when using a third-party operating system, as these may not include all the latest mitigations in their Linux kernel builds. The Arm processors used by Raspberry Pi Ltd do not use microcode, so all mitigations are at the kernel level. | ||
|
|
||
| The vulnerability information reported by `lscpu` is based on the currently executing kernel's detection scheme. It may not accurately reflect the true vulnerability status of the hardware, especially if the OS lacks recent kernel updates. Further vulnerability information on the CPU vendor advisories can be obtained from https://developer.arm.com/Arm%20Security%20Center/Speculative%20Processor%20Vulnerability referencing Vendor ID and Model Name reported by `lscpu`. |
There was a problem hiding this comment.
"referencing Vendor ID" -> "referencing the Vendor ID" ?
"Model Name" -> "Model name" (because lscpu reports Model name: Cortex-A76)
Add a section on vulnerabilities and mitigations
e04d5e3 to
b119c32
Compare
|
Because of merge problems, I've created a new PR for this, so this one can be closed. But I don't seem to have the permissions to do that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a section on vulnerabilities and mitigations