Skip to contentSkip to conversation

U-Boot v2020.01-rc4 released

U-Boot Tom Rini 5 participants 12 messages Dec 3, 2019 1 message not in the archive

lore
Share & tools
lore

Tom Rini

author
#0 lore raw

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191202/e1321951/attachment.sig>

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Resending because of mailing list server issues.

Quoted 38 lines · Eugen Hristev
Quoted 9 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4.  Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go.  In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series.  Then we're down to just fixing up misconversions where things got turned off.

Quoted 7 lines

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th.  Thanks all!

Hi Tom,

Isn't Jan 6th a bit tight considering the new year vacations ? Not like I would expect last minute bugs, but, just to make sure.

Eugen

Quoted 10 lines
Signature · 8 lines
-- 
Tom


_______________________________________________
U-Boot-Custodians mailing list
U-Boot-Custodians at lists.denx.de
https://lists.denx.de/listinfo/u-boot-custodians
author
#3 lore raw
In reply to a message not in the archive
Quoted 18 lines · Eugen.Hristev at microchip.com
Quoted 14 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

Quoted 7 lines
Quoted 2 lines

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

Hi Tom,

Isn't Jan 6th a bit tight considering the new year vacations ? Not like I would expect last minute bugs, but, just to make sure.

I expect things to get very quiet after this week, so I think things will be safe. I'm grabbing some assorted fixes now, and then the MTD cleanups, and then that's about it.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191203/4dda45d8/attachment.sig>
#4 lore raw
In reply to Tom Rini

Hi Tom,

Quoted 10 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Quoted 7 lines

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

I have a -net PR just about ready, but there are a few boards failing for size. When can I expect the size reduction to drop?

Thanks,
-Joe

author
#5 lore raw
Quoted 18 lines · Joe Hershberger

Hi Tom,

Quoted 15 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

Quoted 5 lines
Quoted 2 lines

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

I have a -net PR just about ready, but there are a few boards failing for size. When can I expect the size reduction to drop?

How much are they failing? You can rebase on top of WIP/2019-12-03-master-imports and see if that's enough. But also if it's for packed member things, I'm not sure if that's the right approach vs disabling the warning like the Linux kernel does (and we do today, for clang).

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191203/59ec76a5/attachment.sig>
#6 lore raw

Hey Tom,

Quoted 20 lines · Tom Rini
Quoted 18 lines · Joe Hershberger

Hi Tom,

Quoted 15 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

Quoted 8 lines
Quoted 5 lines
Quoted 2 lines

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

I have a -net PR just about ready, but there are a few boards failing for size. When can I expect the size reduction to drop?

How much are they failing? You can rebase on top of WIP/2019-12-03-master-imports and see if that's enough. But also if

arm: + tbs2910
+u-boot.imx exceeds file size limit:

1356+  limit:  0x5fc00 bytes
1357+  actual: 0x60c00 bytes
1358+  excess: 0x1000 bytes

arm: + am335x_boneblack_vboot
922+arm-linux-gnueabi-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram'
923+arm-linux-gnueabi-ld.bfd: region `.sram' overflowed by 392 bytes 924+make[2]: *** [spl/u-boot-spl] Error 1
925+make[1]: *** [spl/u-boot-spl] Error 2
926+make: *** [sub-make] Error 2
927 arm: + am335x_evm
928+arm-linux-gnueabi-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram'
929+arm-linux-gnueabi-ld.bfd: region `.sram' overflowed by 664 bytes 930+make[2]: *** [spl/u-boot-spl] Error 1
931+make[1]: *** [spl/u-boot-spl] Error 2
932+make: *** [sub-make] Error 2

Quoted 6 lines

it's for packed member things, I'm not sure if that's the right approach vs disabling the warning like the Linux kernel does (and we do today, for clang).

--
Tom

author
#7 lore raw
Quoted 29 lines · Joe Hershberger

Hey Tom,

Quoted 26 lines · Tom Rini
Quoted 23 lines · Joe Hershberger

Hi Tom,

Quoted 10 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Quoted 7 lines

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

I have a -net PR just about ready, but there are a few boards failing for size. When can I expect the size reduction to drop?

Quoted 8 lines
Quoted 2 lines

How much are they failing? You can rebase on top of WIP/2019-12-03-master-imports and see if that's enough. But also if

arm: + tbs2910
+u-boot.imx exceeds file size limit:

1356+  limit:  0x5fc00 bytes
1357+  actual: 0x60c00 bytes
1358+  excess: 0x1000 bytes

Might be fine now, we're clearing out a few bytes.

Quoted 6 lines

arm: + am335x_boneblack_vboot
922+arm-linux-gnueabi-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram'
923+arm-linux-gnueabi-ld.bfd: region `.sram' overflowed by 392 bytes 924+make[2]: *** [spl/u-boot-spl] Error 1
925+make[1]: *** [spl/u-boot-spl] Error 2

Quoted 8 lines

926+make: *** [sub-make] Error 2
927 arm: + am335x_evm
928+arm-linux-gnueabi-ld.bfd: u-boot-spl section .u_boot_list' will not fit in region .sram'
929+arm-linux-gnueabi-ld.bfd: region `.sram' overflowed by 664 bytes 930+make[2]: *** [spl/u-boot-spl] Error 1
931+make[1]: *** [spl/u-boot-spl] Error 2
932+make: *** [sub-make] Error 2

SPL is unchanged in all cases. What's causing this growth anyhow? Thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191203/265be8f1/attachment.sig>
#8 lore raw
In reply to Tom Rini

Hi Tom,

Quoted 10 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Quoted 7 lines

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

Speaking of next year, what is the plan for the release. Is there any chance we might move back to a release every two months? The three-month process is very slow...

Regards,
Simon

#9 lore raw
Quoted 18 lines · Simon Glass

Hi Tom,

Quoted 15 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

Quoted 6 lines
Quoted 2 lines

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

Speaking of next year, what is the plan for the release. Is there any chance we might move back to a release every two months? The three-month process is very slow...

I am very happy with this 3-month release cycle, it's less stressful and I think the quality of the releases is higher too.

author
#10 lore raw
Quoted 22 lines · Marek Vasut
Quoted 21 lines · Simon Glass

Hi Tom,

Quoted 17 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

Quoted 6 lines
Quoted 3 lines

Speaking of next year, what is the plan for the release. Is there any chance we might move back to a release every two months? The three-month process is very slow...

I am very happy with this 3-month release cycle, it's less stressful and I think the quality of the releases is higher too.

I thought I said this a release or so ago, sorry. I believe we'll be sticking with the 3-month cycle and I hope to find time to more actively use a -next branch myself to help with some of the delay, or at least slower feedback cycle.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191203/23f6c1bd/attachment.sig>
#11 lore raw

Hi Tom,

Quoted 28 lines · Tom Rini
Quoted 26 lines · Marek Vasut
Quoted 24 lines · Simon Glass

Hi Tom,

Quoted 10 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Quoted 7 lines

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

Speaking of next year, what is the plan for the release. Is there any chance we might move back to a release every two months? The three-month process is very slow...

Quoted 7 lines
Quoted 2 lines

I am very happy with this 3-month release cycle, it's less stressful and I think the quality of the releases is higher too.

I thought I said this a release or so ago, sorry. I believe we'll be sticking with the 3-month cycle and I hope to find time to more actively use a -next branch myself to help with some of the delay, or at least slower feedback cycle.

That would certainly help, but it hasn't proved possible so far. Let's see how it goes with the next release.

Do you think if we can improve the testing (e.g. with more mini-labs attached to gitlab) we might resolve these stability problems?

Regards,
Simon

author
#12 lore raw
Quoted 34 lines · Simon Glass

Hi Tom,

Quoted 31 lines · Tom Rini
Quoted 28 lines · Marek Vasut
Quoted 18 lines · Simon Glass

Hi Tom,

Quoted 15 lines · Tom Rini

Hey all,

It's release day and here is v2020.01-rc4. Yes, I'm still working on fixing all of the issues that pop up as I get the MTD clean-up series ready to go. In fact, what I need to do at this point is grab the handful of size reduction patches that this has shown are worthwhile, then I can do the MTD series. Then we're down to just fixing up misconversions where things got turned off.

Once again, for a changelog,
git log --merges v2020.01-rc3..v2020.01-rc4
and as always, I ask for more details in the PRs people send me so I can put them in the merge commit.

Quoted 6 lines
Quoted 2 lines

I'm planning on doing -rc5 on December 23rd with the release scheduled on January 6th. Thanks all!

Speaking of next year, what is the plan for the release. Is there any chance we might move back to a release every two months? The three-month process is very slow...

I am very happy with this 3-month release cycle, it's less stressful and I think the quality of the releases is higher too.

Quoted 7 lines
Quoted 4 lines

I thought I said this a release or so ago, sorry. I believe we'll be sticking with the 3-month cycle and I hope to find time to more actively use a -next branch myself to help with some of the delay, or at least slower feedback cycle.

That would certainly help, but it hasn't proved possible so far. Let's see how it goes with the next release.

Well, it's also about custodian stress and time levels. The longer cycle seems to be better for that.

Quoted 2 lines

Do you think if we can improve the testing (e.g. with more mini-labs attached to gitlab) we might resolve these stability problems?

Ah right, I needed to reply to that thread, sorry. I get the feeling that the answer overall is that folks that have spent time with LAVA need to chime in, or barring that, I need to play with LAVA as that's how a lot of the "how do you reserve boards" and so forth problems are handled, and would also make an easier case for vendors to get more U-Boot testing done (as that gets you to kernelci too, or if you already have kernelci going, you can add U-Boot with just a few more steps).

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191203/95f9f4ff/attachment.sig>