[ANN] U-Boot v2020.01 released
Hey all,
It's once again release day. While we've had a few things pop up near the end of the cycle I think we've got things handled well enough. In fact, I'm going to be open to doing, if needed, a v2020.01.y, with a fairly strict set of rules, if we have problems arise that can be safely addressed. I'd like to thank all of our contributors for their efforts.
The next thing I'd like to point out is that as part of this release we've re-synced with upstream for libfdt and it's now more strict in somme cases. What this means for the end user is that, especially on platforms where the DT that we use is passed in from upstream, you may need a more up-to-date ATF binary. I believe this is documented in the i.MX8-based board READMEs and for Renesas platforms the patch is currently at: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/3025 and I would like to thank Marek Vasut for digging into the details on this at almost the literal last minute.
Another important part of this release is that we've migrated fully from Python 2.7 to Python 3 (with 3.5 being the minimum version required). Thanks again to everyone that put in some time and energy to digging into our problems here and helping to fix it.
In terms of a changelog, git log --merges v2020.01-rc5..v2020.01 or git log --merges v2019.10..v2020.01
The merge window is once again open and I plan to tag -rc1 on January 27th, bi-weekly -rcs thereafter and final release on April 6th, 2020.
On 06.01.2020 22:58, Tom Rini wrote:
The next thing I'd like to point out is that as part of this release we've re-synced with upstream for libfdt
Hello Tom,
Regarding the DTC parser (/scripts/dtc/version_gen.h)
#define DTC_VERSION "DTC 1.4.6-gaadd0b65"
Is this compatible with the new libfdt that we have , and, are there any plans to update this to a newer version? (aadd0b65 is about 2 years old -2018/02)
I tried to try out with a new DTC version but most devicetrees have new warnings popping out blocking travis/CI etc.
Thanks ! Eugen
On Tue, Jan 07, 2020 at 07:28:35AM +0000, Eugen.Hristev@microchip.com wrote:
On 06.01.2020 22:58, Tom Rini wrote:
The next thing I'd like to point out is that as part of this release we've re-synced with upstream for libfdt
Hello Tom,
Regarding the DTC parser (/scripts/dtc/version_gen.h)
#define DTC_VERSION "DTC 1.4.6-gaadd0b65"
Is this compatible with the new libfdt that we have , and, are there any plans to update this to a newer version? (aadd0b65 is about 2 years old -2018/02)
I tried to try out with a new DTC version but most devicetrees have new warnings popping out blocking travis/CI etc.
I believe that needing to fix all of the device trees was what put my last effort to re-sync with upstream dtc on hold. That I think in turn was blocked by wanting to re-sync dts files with upstream Linux and that in turn for TI am335x at least got stuck on changes to the cpsw driver and associated bindings. That last problem I think is either unblocked now, or can be once I go through my queue of TI related patches to apply.
On a related note, I also want to start a slow re-sync of the Kbuild files as they've gone a while without a re-sync and I think just doing a big jump looked hard, but a release or two at a time didn't seem too bad.
On 06.01.2020 22:58, Tom Rini wrote:
The next thing I'd like to point out is that as part of this release we've re-synced with upstream for libfdt
Hello Tom,
Regarding the DTC parser (/scripts/dtc/version_gen.h)
#define DTC_VERSION "DTC 1.4.6-gaadd0b65"
Is this compatible with the new libfdt that we have , and, are there any plans to update this to a newer version? (aadd0b65 is about 2 years old -2018/02)
I tried to try out with a new DTC version but most devicetrees have new warnings popping out blocking travis/CI etc.
Thanks ! Eugen
On Mon, Jan 06, 2020 at 03:58:43PM -0500, Tom Rini wrote:
Hey all,
It's once again release day. While we've had a few things pop up near the end of the cycle I think we've got things handled well enough. In fact, I'm going to be open to doing, if needed, a v2020.01.y, with a fairly strict set of rules, if we have problems arise that can be safely addressed. I'd like to thank all of our contributors for their efforts.
The next thing I'd like to point out is that as part of this release we've re-synced with upstream for libfdt and it's now more strict in somme cases. What this means for the end user is that, especially on platforms where the DT that we use is passed in from upstream, you may need a more up-to-date ATF binary. I believe this is documented in the i.MX8-based board READMEs and for Renesas platforms the patch is currently at: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/3025 and I would like to thank Marek Vasut for digging into the details on this at almost the literal last minute.
Another important part of this release is that we've migrated fully from Python 2.7 to Python 3 (with 3.5 being the minimum version required). Thanks again to everyone that put in some time and energy to digging into our problems here and helping to fix it.
In terms of a changelog, git log --merges v2020.01-rc5..v2020.01 or git log --merges v2019.10..v2020.01
The merge window is once again open and I plan to tag -rc1 on January 27th, bi-weekly -rcs thereafter and final release on April 6th, 2020.
I've now merged -next in to master and re-set next to current master. I'm closing the next branch for now and will re-open it likely in March or very late February (depending on how things are going). Thanks all!
participants (2)
-
Eugen.Hristev＠microchip.com -
Tom Rini