<marex>
Tartarus: have we ever considered including u-boot.bin or similar build artifacts in CI output , for easy testing ?
sszy has quit [Ping timeout: 256 seconds]
monstr has quit [Ping timeout: 252 seconds]
<Tartarus>
There's both size constraints and then that so many targets now require other blobs that many wouldn't work
monstr has joined #u-boot
sszy has joined #u-boot
Clamor has quit [Read error: Connection reset by peer]
jluthra has quit [Ping timeout: 246 seconds]
jbowen has quit [Ping timeout: 268 seconds]
mithro has quit [Ping timeout: 268 seconds]
broonie has quit [Ping timeout: 246 seconds]
Tartarus has quit [Ping timeout: 268 seconds]
patersonc has quit [Ping timeout: 246 seconds]
sjg1 has quit [Ping timeout: 256 seconds]
khilman has quit [Ping timeout: 256 seconds]
mkorpershoek has quit [Ping timeout: 260 seconds]
Tartarus has joined #u-boot
rcn-ee has quit [Ping timeout: 246 seconds]
Forty-Bot has quit [Ping timeout: 268 seconds]
jluthra has joined #u-boot
jbowen has joined #u-boot
khilman has joined #u-boot
nohit has quit [Ping timeout: 246 seconds]
crb_ has joined #u-boot
crb has quit [Ping timeout: 260 seconds]
mithro has joined #u-boot
robher has quit [Ping timeout: 256 seconds]
lvrp16 has quit [Ping timeout: 256 seconds]
patersonc has joined #u-boot
rcn-ee has joined #u-boot
broonie has joined #u-boot
vigneshr has quit [Ping timeout: 260 seconds]
robher has joined #u-boot
Tartarus has quit [Ping timeout: 264 seconds]
nohit has joined #u-boot
jbowen has quit [Ping timeout: 264 seconds]
logicalerzor has quit [Ping timeout: 264 seconds]
lvrp16 has joined #u-boot
logicalerzor has joined #u-boot
Forty-Bot has joined #u-boot
Tartarus has joined #u-boot
jluthra has quit [Ping timeout: 264 seconds]
jbowen has joined #u-boot
jluthra has joined #u-boot
lvrp16 has quit [Ping timeout: 246 seconds]
jluthra has quit [Ping timeout: 246 seconds]
rcn-ee has quit [Ping timeout: 268 seconds]
joeskb7 has quit [Remote host closed the connection]
joeskb7 has joined #u-boot
Clamor has joined #u-boot
jbowen has quit [Ping timeout: 246 seconds]
Tartarus has quit [Ping timeout: 256 seconds]
lvrp16 has joined #u-boot
<xypron>
calebccff: This does not look like an EFI bug but like an ext4 bug. ext4fs_exists() should not call ext4fs_open() but ext4fs_find_file1() which can find directories and files. To be truthful the problem starts with the methods in struct fstype_info not being documented.
rcn-ee has joined #u-boot
jluthra has joined #u-boot
jbowen has joined #u-boot
Tartarus has joined #u-boot
sjg1 has joined #u-boot
stefanro has quit [Ping timeout: 255 seconds]
mkorpershoek has joined #u-boot
vigneshr has joined #u-boot
Clamor has quit [Ping timeout: 264 seconds]
stefanro has joined #u-boot
<calebccff>
xypron: yes, i wasn't super clear there, I do agree that this is an ext4 bug
matthias_bgg has quit [Read error: Connection reset by peer]
Gravis has quit [Ping timeout: 264 seconds]
Clamor has joined #u-boot
GNUtoo has quit [Ping timeout: 255 seconds]
GNUtoo has joined #u-boot
matthias_bgg has joined #u-boot
<Forty-Bot>
Tartarus: what about just for the stage 2 builds? those we know work because we run them in qemu
<Tartarus>
That's not always useful in and of itself tho
<calebccff>
is there anything that can be done about "clk_get_rate()" having a return type of ulong but then returning -ENOSYS if ops->get_rate isn't implemented?
<calebccff>
i've seen a few drivers only check for 0 and assume any other value is a valid clock rate, which can lead to some... weird behaviour
rcn-ee has quit [Ping timeout: 246 seconds]
rcn-ee has joined #u-boot
<Forty-Bot>
calebccff: convert them to IS_ERR_VALUE