<rob_w>
i wonder ... if i use openssl with devcrypto it takes far longer then without ? might this be due to weak randomness ??
eballetbo has joined #linux-ti
minash has quit [Remote host closed the connection]
minash has joined #linux-ti
HcE has quit [Quit: Lost terminal]
florian has quit [Quit: Ex-Chat]
<rob_w>
i wonder ... if i use openssl with devcrypto it takes far longer then without ? might this be due to weak randomness ??
rob_w has quit [Remote host closed the connection]
florian has joined #linux-ti
goliath has quit [Quit: SIGSEGV]
florian has quit [Ping timeout: 245 seconds]
florian has joined #linux-ti
florian has quit [Ping timeout: 260 seconds]
<pivi>
bryanb: I am back with this 6.6 vs 6.12 in scarthgap. can I expect people using a v6.6 based kernel to still be able to use meta-ti scarthgap branch? we do have our own stuff in a separate layer, but we do still build on top of meta-ti, and we might not have the same roadmap as you moving from v6.6 to v6.12
<pivi>
I do foresee a need to keep meta-ti/scarthgap being able to work with either v6.6 or v6.12, if anything not compatible would arise at some point
florian has joined #linux-ti
Kubu_work has quit [Quit: Leaving.]
goliath has joined #linux-ti
ikarso has quit [Quit: Connection closed for inactivity]
<pivi>
NishanthMenon: hello! I just noticed an issue in your downstream U-Boot
<pivi>
you have this commit in, commit 82e26e0d6883 ("spl: Use CONFIG_SPL... instead of CONFIG_..._SPL_...")
<pivi>
and a few more. In practice it's working, so likely not needed stuff that could just be removed. Or maybe there is something worst going on. Not sure where to report this, so I decided here was the easiest way for me