Skip to content

rpi-update and rpi-firmware #225

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

Closed
Mausy5043 opened this issue May 9, 2015 · 2 comments
Closed

rpi-update and rpi-firmware #225

Mausy5043 opened this issue May 9, 2015 · 2 comments

Comments

@Mausy5043
Copy link
Contributor

I've occasionally seen references to rpi-update (https://github.com/Hexxeh) here on this repo.

Since neither Hexxeh's rpi-update nor rpi-firmware are installed by default I was wondering if you would see some added advantage to regularly running rpi-update?

Or do you consider these tools to be used when things are broken?

@diederikdehaas
Copy link
Member

You shouldn't use rpi-update unless you're told to (by a rpf member) or when you think it's fun to run the latest and (mostly) untested kernel and firmware.
Thankfully ShiftPlusOne (on the forum/irc) is now actively discouraging ppl to use rpi-update.

When things are broken (and kernel related) like raspberrypi/linux#914 then it makes sense to also test whether the issue is present in rpf's very latest kernel, but by far most ppl should stay clear of rpi-update.

I've never heard of rpi-firmware though (rpi-update updates both kernel and firmware).
There are nightly build firmware package which are properly packaged (as opposed to rpi-update) and thus manageable through APT

@Mausy5043
Copy link
Contributor Author

Thanks. 👍

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

No branches or pull requests

2 participants