ikarso has quit [Quit: Connection closed for inactivity]
xroumegue has quit [Ping timeout: 244 seconds]
jclsn has quit [Ping timeout: 252 seconds]
jclsn has joined #u-boot
xroumegue has joined #u-boot
frieder has quit [Ping timeout: 252 seconds]
leah has joined #u-boot
fkw has quit [Remote host closed the connection]
fkw has joined #u-boot
vagrantc has joined #u-boot
fkw has quit [Remote host closed the connection]
dsimic has quit [Ping timeout: 265 seconds]
dsimic has joined #u-boot
Peng_Fan has joined #u-boot
vagrantc has quit [Quit: leaving]
alperak has joined #u-boot
gsz has joined #u-boot
monstr has joined #u-boot
monstr has quit [Ping timeout: 248 seconds]
haritz has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
ikarso has joined #u-boot
K900 has quit [Remote host closed the connection]
K900 has joined #u-boot
Peng_Fan has quit [Quit: Connection closed for inactivity]
gsz has quit [Ping timeout: 264 seconds]
ldevulder has joined #u-boot
gsz has joined #u-boot
julia has quit [Read error: Connection reset by peer]
sszy has joined #u-boot
julia has joined #u-boot
walter has joined #u-boot
walter has joined #u-boot
gsz has quit [Ping timeout: 248 seconds]
gsz has joined #u-boot
Stat_headcrabbed has joined #u-boot
gsz has quit [Ping timeout: 245 seconds]
persmule has quit [Quit: Leaving]
persmule has joined #u-boot
<qschulz>
marex: the issue I'm seeing is how to document what a specific reset does. Like, edl is a very Qualcomm specific thing. The partial reset for CA/CR/CM cores also sounds very architecture or even SoC-specific.
<qschulz>
on Rockchip, it's even unclear what a reset does, as you can configure the level of the CPU reset programmatically and it's very vague what each level actually does
<qschulz>
so it's difficult to come up with documentation for the expected behavior of the command
rainbyte has quit [Read error: Connection reset by peer]
rainbyte has joined #u-boot
gsz has joined #u-boot
SnoopyOnZNCNow has quit [Ping timeout: 244 seconds]
milkylainen has quit [Remote host closed the connection]
gsz has quit [Quit: gsz]
zsoltiv_ has quit [Quit: Left]
zsoltiv_ has joined #u-boot
slobodan__ has joined #u-boot
gsz has joined #u-boot
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
artiepoole has quit [Quit: ZNC 1.9.0+deb2build3 - https://znc.in]
artiepoole has joined #u-boot
Stat_headcrabbed has joined #u-boot
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
artiepoole has quit [Quit: ZNC 1.9.0+deb2build3 - https://znc.in]
artiepoole has joined #u-boot
<marex>
qschulz: altera socfpga also had warm and cold reset ... and yes, it is likely very soc specific
<marex>
qschulz: but there it is clear what each of them does
<marex>
qschulz: the command might need some hooks/linkedlist to plug in the various resets ?
<qschulz>
marex: the hook is what's being implemented for edl on Qualcomm
<qschulz>
(the thing I tried to revert yesterday_
gsz has quit [Ping timeout: 272 seconds]
rgallaispou has joined #u-boot
memset has quit [Remote host closed the connection]
rgallaispou has quit [Client Quit]
memset has joined #u-boot
Stat_headcrabbed has joined #u-boot
<marex>
qschulz: hmmmm
monstr has joined #u-boot
monstr has quit [Ping timeout: 248 seconds]
memset has quit [Remote host closed the connection]
haritz has joined #u-boot
haritz has quit [Changing host]
haritz has joined #u-boot
memset has joined #u-boot
<sjg1>
Tartarus: I notice that some crawlers go through every gitlab commit and every file in the tree (using URLs) which loads up the server for a few days, so you could add a rule for that, if it is happening
<f_>
sjg1: there's already anubis to prevent that no?
<sjg1>
f_: I'm not actually using that. I find it annoying not to be able to access lore programmatically, for example, because of those things
<f_>
I find it very annoying to not be able to access anything without waiting ages
<f_>
but it is what it is
SnoopyOnZNCNow has joined #u-boot
gsz has joined #u-boot
memset has quit [Remote host closed the connection]
memset has quit [Remote host closed the connection]
memset has joined #u-boot
<Tartarus>
catching up on emails, qschulz, if you don't have time to squash and grab kcxt's ack, I'll just do that in a bit, today. Thanks again for being persistent on this
<qschulz>
Tartarus: I haven't checked anything since yesterday so I'm as confident in the patch as yesterday
<qschulz>
but I can squash + acked-by kcxt and send that as a v2 if you want
<Tartarus>
qschulz: Please, with just listing all the reverted commits. I think that addresses Marek's point about having a better commit message
<Tartarus>
1 commit, explaining the problem, listing and reverting N commits
<qschulz>
np np
jeroen_ has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
m has quit [Quit: WeeChat 4.7.2]
ja_02 has quit [Ping timeout: 245 seconds]
ravikant_ has quit [Ping timeout: 256 seconds]
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
ikarso has joined #u-boot
<qschulz>
Tartarus: done, sorry for the delay
<Tartarus>
No worries, thanks again
eballetbo has quit [Quit: Connection closed for inactivity]
vagrantc has joined #u-boot
sszy has quit [Remote host closed the connection]
julia has quit [Ping timeout: 272 seconds]
julia has joined #u-boot
Stat_headcrabbed has joined #u-boot
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
<marex>
f_: maybe you can ask AI for a summary of that page instead of waiting for it to load ... surely the AI already brutalized the page and asimilated it :/
<f_>
I don't know why but everytime I ask my AI about something it says "?"
<f_>
I have a feeling I might be holding it wrong :D
<jeroen_>
f_: you like need a ed plugin and rewrite it in rust...
julia has quit [Ping timeout: 252 seconds]
julia has joined #u-boot
<f_>
but I thought ed itself was an AI agent!!
mischief has quit [Quit: goodbye cruel world]
<Ermine>
"?" is peak AI actually
mischief has joined #u-boot
<jeroen_>
f_: obviously it is, just start with a ! first ;)
<jeroen_>
(well and some glue script following it)
<f_>
now it's screaming at me :O
<jeroen_>
f_: just append 2>&1 >/dev/null, that will tame it
<f_>
:D
<Tartarus>
So, I guess the solution to "too many files open" is you need to drop something like "LimitNOFILE=1048576" in the systemd unit override for gitlab-runner?
<Tartarus>
(in the services section)
slobodan__ has quit [Quit: Leaving]
slobodan has joined #u-boot
gsz has quit [Ping timeout: 268 seconds]
ldevulder has quit [Ping timeout: 245 seconds]
prabhakalad has quit [Quit: Konversation terminated!]
leah has quit [Ping timeout: 265 seconds]
leah has joined #u-boot
mischief has quit [Read error: Connection reset by peer]
<sjg1>
Tartarus: I put this in the config.toml (for each runner): [runners.docker.ulimit]
<sjg1>
"nofile" = "1048576"
dormito has quit [Quit: WeeChat 4.5.2]
jeroen_ has quit [Remote host closed the connection]
dormito has joined #u-boot
tec42 has quit [Quit: bye!]
weirdtreething has quit [Ping timeout: 248 seconds]