<rfs613>
shadow: for your spacemit/k3 patch from last week, most of this seems to be around a build_binary_file.py script, that i guess comes from the vendor (doesn't seem to be in mainline). I am not familiar with either this board nor this vendor script. Perhaps consider if binman could be used to assemble the binary images?
rainbyte has quit [Read error: Connection reset by peer]
<rfs613>
shadow: also regarding changing SPL_SIZE_LIMIT, this is usually a hardware constraint, does the value you are changing match with the hardware documentation?
<rfs613>
(eg. don't increase it just to avoid getting a compile error due to SPL size)
frieder has joined #u-boot
rainbyte has joined #u-boot
frieder has quit [Remote host closed the connection]
<marex>
rfs613: split by subsystem
<marex>
rfs613: send chunks by each subsystem
<marex>
rfs613: in the board/DT patches, add cover letter and list the deps with lore links there
apritzel_ has joined #u-boot
apritzel__ has quit [Ping timeout: 245 seconds]
<rfs613>
marex: okay, will do. Do I call them 'v2' (as there are some changes since the first post) or start fresh with just [PATCH] again?
<marex>
rfs613: if you did changes -> v2 with changelog / else do a v2 with changelog which states "split from series blah blah ..." or some such
<marex>
rfs613: btw. I'm dreadfully tired, sorry
<rfs613>
marex: don't worry, I'll find a way to mess it up :-) Get some rest!
dsimic has quit [Ping timeout: 264 seconds]
<marex>
rfs613: you'll do fine
dsimic has joined #u-boot
<Tartarus>
Catching up on emails, and part of the problem with an AI policy is that they're all still bad at not changing magic numbers. You have to assume it's always wrong, and at that point I fail to see the value
apritzel_ has quit [Ping timeout: 272 seconds]
walter has quit [Quit: Konversation terminated!]
walter has joined #u-boot
walter has quit [Changing host]
walter has joined #u-boot
memset_ has joined #u-boot
memset has quit [Remote host closed the connection]
rainbyte has quit [Read error: Connection reset by peer]
rainbyte has joined #u-boot
mmu_man has quit [Ping timeout: 256 seconds]
___nick___ has quit [Ping timeout: 264 seconds]
___nick___ has joined #u-boot
mmu_man has joined #u-boot
<shadow>
Tartarus: are my attempts to subscribe to the new listserv making it through?
<shadow>
e@freeshell.de
<shadow>
rfs613: increasing SPL_SIZE_LIMIT allows the build to continue but is not useful for the reason that fastboot also gates on the size, so factory pre-flashed vendor u-boot replies the limit and fastboot aborts
goliath has joined #u-boot
<shadow>
rfs613: allegedly we will see a patch series sent to mainline u-boot this month so I am looking to clean up the vendor u-boot just enough that it builds without going full ham sandwich rewrite on it ;)
<f_>
Tartarus: what magic numbers, what do you mean by that?
<rfs613>
shadow: interesting. I wouldn't have expected fastboot to use the same limit. Historically at lest, SPL tends to be quite small, 64 to 256 kB or so, whereas fastboot typically deals with large rootfs images that could be gigabytes in size.
<Tartarus>
shadow: are you having a problem subscribing?
<Tartarus>
f_: I mean I've seen it change a git hash in a commit message, for example. You can "tell" it to copy paste values from some source, but will it, and not change them? Not sure.
<Tartarus>
it's the same problem as "how many Ls are in google?" and getting back 3.
memset_ has quit [Remote host closed the connection]
<f_>
oh you're talking about how (not) good AIs are
memset has joined #u-boot
<Tartarus>
Yes
<f_>
I honestly don't care, I don't use them for ethical reasons and also because... well.. I like working on that stuff, don't feel particularly great if I just let some tool do the stuff I like doing instead of doing it myself
<Tartarus>
Yes, also very valid reasons.
<Tartarus>
I just find this helpful in explaining to people that do want to use it, why I don't think it's a good idea for the project.
<f_>
I am mostly asking because I got an Assisted-by patch in my inbox and I was wondering if there was some proper docs I could point to that say "no AI please"
<shadow>
Tartarus: yes I initially received multiple confirmation link emails with stale confirmation code/link, and on retrying to subscribe no confirmation email is sent
<Tartarus>
f_: ah, ok
<Tartarus>
shadow: No, you're not subscribed. I'm not sure why.
<Tartarus>
Do you want me to try and do it manually?
walter has quit [Quit: Konversation terminated!]
<shadow>
manually is fine yes thank you
walter has joined #u-boot
<Tartarus>
Hopefully you have an email in your inbox if not now, in a moment or two.
vagrantc has joined #u-boot
fgarcia_ has joined #u-boot
fgarcia has quit [Ping timeout: 265 seconds]
prabhakalad has quit [Ping timeout: 274 seconds]
prabhakalad has joined #u-boot
fgarcia_ is now known as fgarcia
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
mmu_man has quit [Ping timeout: 263 seconds]
mmu_man has joined #u-boot
___nick___ has quit [Ping timeout: 264 seconds]
mmu_man has quit [Ping timeout: 241 seconds]
mmu_man has joined #u-boot
walter has quit [Quit: Konversation terminated!]
walter has joined #u-boot
goliath has quit [Quit: SIGSEGV]
slobodan has quit [Ping timeout: 245 seconds]
memset has quit [Remote host closed the connection]