Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2024.07, v2024.10-rc2 are OUT / Merge Window is CLOSED, next branch is OPEN / Release v2024.10 is scheduled for 07 October 2024 / Channel archives at https://libera.irclog.whitequark.org/u-boot
ikarso has quit [Quit: Connection closed for inactivity]
Jones42_ has joined #u-boot
Jones42 has quit [Ping timeout: 272 seconds]
jclsn has quit [Ping timeout: 248 seconds]
jclsn has joined #u-boot
Jones42__ has joined #u-boot
Jones42_ has quit [Ping timeout: 246 seconds]
mmu_man has quit [Ping timeout: 244 seconds]
ikarso has joined #u-boot
rvalue has quit [Ping timeout: 260 seconds]
gsz has joined #u-boot
rvalue has joined #u-boot
profcowculus has joined #u-boot
monstr has joined #u-boot
gsz has quit [Ping timeout: 248 seconds]
enok has joined #u-boot
warpme has joined #u-boot
glaroque has joined #u-boot
naoki has quit [Ping timeout: 276 seconds]
enok has quit [Ping timeout: 272 seconds]
naoki has joined #u-boot
goliath has joined #u-boot
sng has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
sng has joined #u-boot
ikarso has quit [Quit: Connection closed for inactivity]
Jones42__ is now known as Jones42
ladis has joined #u-boot
ldevulder has joined #u-boot
ikarso has joined #u-boot
mckoan|away is now known as mckoan
Kwiboo- has quit [Quit: .]
Kwiboo has joined #u-boot
mmu_man has joined #u-boot
devarsh has joined #u-boot
rvalue- has joined #u-boot
rvalue has quit [Ping timeout: 255 seconds]
rvalue- is now known as rvalue
<Jones42> So I've sent this patch two days ago regarding the mkimage ecdsa thing. Now I've discovered another independent bug in the ecdsa dtb handling. should I simply send another patch or should I put them in a patch series?
persmule has quit [Remote host closed the connection]
urja has quit [Read error: Connection reset by peer]
urja has joined #u-boot
<pivi> Jones42: if the fix is relevant in every case and can be applied on its own just send a new indipendent patch
<Jones42> pivi: thanks, will do!
devarsh has quit [Quit: Connection closed for inactivity]
naoki has quit [Quit: naoki]
Cityjohn has joined #u-boot
mmu_man has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
mmu_man has quit [Ping timeout: 272 seconds]
mmu_man has joined #u-boot
Cityjohn has quit [Remote host closed the connection]
Cityjohn has joined #u-boot
slobodan has joined #u-boot
slobodan has quit [Changing host]
slobodan has joined #u-boot
<Forty-Bot> imo the important thing is whether they touch adjacent lines of code (and will conflict if applied in the wrong order)
<Forty-Bot> if there's no conflict, separate patches is easier
persmule has joined #u-boot
monstr has quit [Remote host closed the connection]
dsimic has quit [Ping timeout: 248 seconds]
<pivi> Forty-Bot: I meant the same with "can be applied on its own", but you were more explicit :-)
dsimic has joined #u-boot
goliath has quit [Quit: SIGSEGV]
Stat_headcrabed has joined #u-boot
Manouchehri has quit [Ping timeout: 276 seconds]
macromorgan has quit [Quit: No Ping reply in 180 seconds.]
macromorgan has joined #u-boot
Manouchehri has joined #u-boot
Cityjohn has quit [Ping timeout: 246 seconds]
mripard has quit [Quit: mripard]
Stat_headcrabed has quit [Quit: Stat_headcrabed]
ikarso has quit [Quit: Connection closed for inactivity]
enok has joined #u-boot
<Jones42> is there a trick to tell devtool to continue the patch numbering? when I "devtool finish", the new patches always start at 0001 and i have to manually rename it
<Jones42> ah. it wants the patch-list in SRC_URI += instead :append.
<Jones42> Also, it removes the filenames from my SRC_URI-list if the patch files contain a proper commit message...
Stat_headcrabed has joined #u-boot
goliath has joined #u-boot
mckoan is now known as mckoan|away
ldevulder has quit [Quit: Leaving]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Jones42> ah, wrong channel, sorry
mmu_man has quit [Ping timeout: 260 seconds]
mmu_man has joined #u-boot
slobodan has quit [Read error: Connection reset by peer]
slobodan has joined #u-boot
slobodan has quit [Remote host closed the connection]
warpme has joined #u-boot
enok has quit [Ping timeout: 265 seconds]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vagrantc has joined #u-boot
warpme has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
prabhakalad has quit [Ping timeout: 252 seconds]
prabhakalad has joined #u-boot
ladis has quit [Quit: Leaving]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
enok has joined #u-boot
<Tartarus> Bah, does any distro use kernel= on Pi family?
ikarso has joined #u-boot
<Tartarus> Ah nevermind, now I get it, arm_64bit=1 needed, or not..
mmu_man has quit [Ping timeout: 245 seconds]
redbrain has quit [Read error: Connection reset by peer]
redbrain has joined #u-boot
mmu_man has joined #u-boot
joeskb7 has quit [Quit: Lost terminal]
enok has quit [Ping timeout: 248 seconds]
enok has joined #u-boot
<Tartarus> And with my labgrid stuff posted now too, ugh, this reminds me that 32bit pi might be where the EFI selftest pytest is most unreliable on real hardware :|
naoki has joined #u-boot
enok has quit [Ping timeout: 276 seconds]
Stat_headcrabed has quit [Quit: Stat_headcrabed]
ikarso has quit [Quit: Connection closed for inactivity]
prabhakalad has quit [Ping timeout: 272 seconds]
prabhakalad has joined #u-boot
prabhakalad has quit [Ping timeout: 246 seconds]
prabhakalad has joined #u-boot
ellyq has quit [Remote host closed the connection]
ellyq has joined #u-boot
ellyq has joined #u-boot
enok has joined #u-boot
enok has quit [Ping timeout: 246 seconds]
enok has joined #u-boot
enok has quit [Ping timeout: 252 seconds]
ikarso has joined #u-boot
joeskb7 has joined #u-boot