Skip to content

Conversation

@timg236
Copy link
Contributor

@timg236 timg236 commented Nov 25, 2024

No description provided.

@timg236
Copy link
Contributor Author

timg236 commented Nov 25, 2024

@peterharperuk @popcornmix

Copy link
Contributor

@nathan-contino nathan-contino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, will merge when we're ready to roll out CM5. The one mention of Pi 500 is fine as a small teaser of announcements yet to come :) ... and because it's very unlikely that anyone will remember to update this firmware doc when that comes out!

@timg236
Copy link
Contributor Author

timg236 commented Nov 25, 2024

lgtm, will merge when we're ready to roll out CM5. The one mention of Pi 500 is fine as a small teaser of announcements yet to come :) ... and because it's very unlikely that anyone will remember to update this firmware doc when that comes out!

We published the device-tree for Pi500 recently so there shouldn't be any big surprises. Happy for this to published whenever is convenient e.g. for CM5.

Copy link
Contributor

@nathan-contino nathan-contino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

incorporating a suggestion from a little birdie: flagship should use the full name. compute module prefix fine to drop; keyboard 'raspberry pi' prefix is OK to drop if we have already used a fully qualified flagship model name to reduce fatigue.

@timg236
Copy link
Contributor Author

timg236 commented Nov 26, 2024

Thanks, this looks more compact now and should be unambiguous to readers

@nathan-contino nathan-contino merged commit 0573f44 into raspberrypi:develop Nov 26, 2024
1 check passed
@timg236 timg236 deleted the firmware-updates branch February 25, 2025 17:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants