unlord has quit [Remote host closed the connection]
unlord has joined #riscv
unlord has quit [Ping timeout: 240 seconds]
eroux has quit [Ping timeout: 256 seconds]
motherfsck has quit [Ping timeout: 276 seconds]
motherfsck has joined #riscv
eroux has joined #riscv
bauruine has joined #riscv
unlord has joined #riscv
jack_lsw has quit [Read error: Connection reset by peer]
BootLayer has quit [Quit: Leaving]
jack_lsw has joined #riscv
unlord has quit [Ping timeout: 240 seconds]
jn has quit [Read error: Connection reset by peer]
jn has joined #riscv
jn has joined #riscv
unlord has joined #riscv
unlord has quit [Remote host closed the connection]
unlord has joined #riscv
khem has quit [Quit: You have been kicked for being idle]
unlord has quit [Ping timeout: 256 seconds]
BootLayer has joined #riscv
jack_lsw has quit [Quit: Back to the real world]
motherfsck has quit [Ping timeout: 240 seconds]
<Esmil>
smaeul: Ok, unfortunately using the dt from u-boot does not fix the mmc issue
<Esmil>
I suspect the reason I see them is that I'm running btrfs on the sd-card which checksums every data blob, so when it's reading something unexpected it complains
<Esmil>
mmind00: did you get a chance to try mmc on the d1?
<mmind00>
Esmil: last week I did just try a "dd" of 2MB size _from_ the SD card, not sure if that is similar to what is failing for you ... though I can go a bit more in-depth if needed :-)
<Esmil>
mmind00: when i'm booting from a btrfs rootfs on an sd-card it complains about reading data that is not matching the checksums
motherfsck has joined #riscv
<Esmil>
it seems to be transcient, because when i later run btrfs scrub to read and check the data it finds no errors
<Esmil>
also when I check/mount the filesystem from other machines it's fine. it happens on different sd-cards too
unlord has joined #riscv
haritz has joined #riscv
haritz has quit [Changing host]
haritz has joined #riscv
BootLayer has quit [Quit: Leaving]
unlord has quit [Remote host closed the connection]
bgamari has quit [Ping timeout: 240 seconds]
bgamari has joined #riscv
BootLayer has joined #riscv
aerkiaga has joined #riscv
unlord has joined #riscv
motherfsck has quit [Ping timeout: 246 seconds]
motherfsck has joined #riscv
jmd_ has quit [Ping timeout: 260 seconds]
motherfsck has quit [Ping timeout: 240 seconds]
motherfsck has joined #riscv
toluene0 has quit [Quit: Ping timeout (120 seconds)]
toluene has joined #riscv
BootLayer has quit [Quit: Leaving]
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #riscv
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #riscv
<smaeul>
Esmil: all of my D1 boards boot from ext4 on an SD card. I was seeing random FS errors with v3 of the CMO series, but not with v4. Possibly your issue is fixed by v5 of the series; I will have to rebase on that.
<Esmil>
smaeul: Ah yeah, I was thinking it might be something like that
<la_mettrie>
i'm trying to figure out what is the point where u-boot register data is used at the kernel code's side. u-boot code seems to #define many registers but i haven't found those strings appearing on definitions appearing on the kernel side yet
GenTooMan has quit [Ping timeout: 240 seconds]
pierce_ has joined #riscv
frkazoid333 has quit [Ping timeout: 264 seconds]
frkazoid333 has joined #riscv
pierce_ has quit [Remote host closed the connection]
frkazoid333 has quit [Ping timeout: 240 seconds]
GenTooMan has joined #riscv
BootLayer has joined #riscv
davidlt has quit [Remote host closed the connection]