10:35 <crazy_imp> hi, what should i look at if the boot.scr is ignored? i can run `load mmc :1 0x01000000 boot.scr` followed by `source` and everything is fine. wrong `bootcmd` (it's set to `bootflow scan`)?

13:32 <sjg1> crazy_imp: You can enable CONFIG_BOOTSTD_FULL and get more information. There is an open issue about this too: https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/13

13:52 <crazy_imp> sjg1: so boot.scr should be executed by default anyway, no matter what $bootcmd says?

13:53 <sjg1> crazy_imp: No, it is executed by the 'script' bootmeth - see https://docs.u-boot.org/en/latest/develop/bootstd.html

13:53 <sjg1> crazy_imp: But if you use 'bootflow list -l' you will see what it finds

13:54 <crazy_imp> sjg1: my build currently only supports `scan` as argument for bootflow

13:58 <sjg1> crazy_imp: You can enable CONFIG_BOOTSTD_FULL

19:19 <marex> Tartarus: I'd push the release a bit later into January

19:19 <marex> Tartarus: hmmm, did I mention that before ?

19:24 <f_> in 5 days..hmm

19:25 <Tartarus> marex: You did, but little changed between rc5 (Dec 18) and now, and not all that much between rc4 and rc5 so yes, I just wish people in places where there's big holidays between dec and mid jan would schedule testing time in. If we push in to mid Jan now it's just the people that take lunar new year instead having crunch time not align well with testing u-boot before they go off

19:25 <Tartarus> There's no great answer here aside from just making sure I really do stick to the plan about keeping changes post -rc2 to the minimum of fixing things

19:47 <marex> Tartarus: you mean like ... there is big holiday, so, people are in holiday, doing holidayey things like relaxing ... and instead, you would wish they would schedule work in ? :)

19:47 <marex> Tartarus: please clarify :)

19:54 <Forty-Bot> u-boot is usually relaxing...

20:04 <Tartarus> I mean there's half of November and all of December for finding time for testing what will become v202X.01

20:04 <Tartarus> Pushing out 2 weeks in Jan (so Monday of 3rd week) instead of 1 week in Jan (Monday of 2nd week) doesn't seem like it's really going to make much difference

20:05 <marex> Tartarus: I think that makes all the difference, people are freshly relaxed and ready to test

20:21 <mps> Tartarus: good idea to postpone a little, 7 Jan is Christmas in some countries, Georgia (Caucasian), Armenia, Russia, Belarus, Ukraine, Serbia and iirc Ethiopia, maybe more

20:24 <Tartarus> Again, that's why there's been months of little to no change before hand

20:25 <Tartarus> And we push it out more and now it's getting in to problem for lunar new year countries instead time frame

20:27 <mps> hm

20:29 <Tartarus> Schedule is published 12 months in advance, all I ask for is people to plan around a well announced schedule

20:29 <Tartarus> afk a bit

20:36 <mps> no problem for me whenever it is released, just commented and maybe OT

21:00 <marex> mps: didnt UA shift xmas to 24th ?

21:01 <marex> Tartarus: I did complain about it for a few years already, so schedule of my complaints was published and you didn't plan around :)

21:14 <mps> marex: idk, could be, they changed a lot in last time, didn't followed much

22:14 <Tartarus> OK, so I think we can schedule this talk again for same time next year ;)

22:15 <mps> :)

23:17 <sakman> Tartarus: regarding to MPC837XERDB DM_I2C, I am traveling now and will take care of this when I am back around end of Jan/early Feb if it is not too late for you.

23:17 <Tartarus> OK, thanks