L4T BSP Versioning Scheme

Just out of curiosity, what is the versioning scheme followed on BSP releases?
Is it something like “Major.Minor.Revision”?


I can’t give you an “official” answer, but from what I’ve seen over many years, you are correct about the scheme. I’ll also add that public releases are always an even numbered major, e.g., “R28.x.x” and “R32.x.x” are public, but “R29” and “R31” would never be public. There wasn’t an “R30.x.x”, but I think it is because of test releases progressing fast enough that it worked out better to just go from “R28.x” to “R32.x”.

Thank you.

hello skumars05rt,

please check, nv_tegra_release release tag for details.
for example, it’s major R32 release, revision is 4.3; we usually use l4t keywords for its version, i.e. l4t-r32.4.3

$  cat /etc/nv_tegra_release
# R32 (release), REVISION: 4.3

there’s JetPack SDK which includes the Linux Driver Package (L4T), you may also check JetPack Archive for details.

1 Like