3

The release notes for example to date 2019-07-10 shows

* Linux kernel 4.19.57
* Raspberry Pi firmware cb3a32adf39f45a49be454e30c7464920ad7c605

After an update I can verify the current kernel version with uname -r. At How can I determine the current firmware version number? I have found how to get the current firmware version:

rpi ~$ sudo /opt/vc/bin/vcgencmd version
Jul  9 2019 14:37:58
Copyright (c) 2012 Broadcom
version d2b1b7fb01475cb3914b2086299e32d724e832f1 (clean) (release) (start)

But as you can see it does not match the release note.

How can I verify the Raspberry Pi firmware version from the release notes?

Ingo
  • 42,107
  • 20
  • 85
  • 197

1 Answers1

2

I think I have an answer to this - actually one of the maintainers of the GitHub repo for Raspberry Pi firmware has answered your question. The Q&A is #1407 under the GitHub Issues tab.

The answer is not as detailed as I would have liked, but to my reading, it seems there is one repo to house the compiled/binary firmware for Raspberry Pi, and another repo to house the source code. The compiled/binary Raspberry Pi firmware is housed on the GitHub repo linked above. The repo containing the source code for the Raspberry Pi firmware is "unpublished/closed-source". The Wiki page for the Raspberry Pi (compiled) firmware repo tells the same story.

And so the answer seems to be this:

  • The 160-bit hash reported by vcgencmd is the hash of the firmware's source code - source code that is housed in an unpublished/closed-source repo.

  • The 160-bit hash in the release notes is the hash of the compiled/binary firmware repo hosted on GitHub.

  • Consequently, the release/commit date is all you have to rely upon. The dates are at least close - I assume there may be a time lag between committing the source files, and committing the binaries since they occur on different repos.

Finally, there's a related Q&A here... this question has been around for a while.

Seamus
  • 21,900
  • 3
  • 33
  • 70