narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
vagrantc has joined #linux-amlogic
montjoie has quit [Ping timeout: 268 seconds]
montjoie has joined #linux-amlogic
BlueMatt has quit [Ping timeout: 255 seconds]
BlueMatt has joined #linux-amlogic
camus has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
elastic_dog has quit [Ping timeout: 260 seconds]
elastic_dog has joined #linux-amlogic
camus1 has joined #linux-amlogic
camus has quit [Ping timeout: 252 seconds]
camus1 is now known as camus
Ballerburg9005 has quit [Ping timeout: 268 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
camus has quit [Ping timeout: 260 seconds]
camus has joined #linux-amlogic
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-amlogic
tdebrouw has joined #linux-amlogic
dbouyeure has joined #linux-amlogic
JohnnyonF has joined #linux-amlogic
JohnnyonFlame has quit [Ping timeout: 260 seconds]
JohnnyonF has quit [Ping timeout: 268 seconds]
JohnnyonFlame has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
<tomeu> narmstrong: the power sequence seems to be pretty solid on the vim3 basic I have on my desk, but 50% of the time the boards in our LAVA lab hang when etnaviv probes
<tomeu> do you know what I could have got wrong?
<xdarklight> tomeu: at which stage does it hang? random guess: maybe the bootloader is different between the two boards - there's some magic blob for DDR initialization in it
<narmstrong> tomeu: no idea, but yea what's the difference between the boards ? can you check the early boot log and the board type/version ?
<narmstrong> and at some point you should get rid of the vendor u-boot :-/
<narmstrong> tomeu: do you use the same kernel ?
<tomeu> this was with the same kernel build, yeah
<tomeu> let me check the logs before the kernel starts booting
<tomeu> here are the logs before kernel boot:
<tomeu> local (reliable): https://paste.debian.net/1262360/
<tomeu> I don't see any obvious differences in hw, so I guess the bootloader is suspicious
Ballerburg9005 has joined #linux-amlogic
<narmstrong> tomeu: yeah neither BL2, BL31 or U-boot are the same, here's a diff https://paste.debian.net/plain/1262361
<narmstrong> probably the boot image of the CI VIM3 should be updated
Ballerburg9005 has quit [Ping timeout: 252 seconds]
<tomeu> narmstrong: something I don't understand is that the board on my desk is showing 2GB available after boot, but the bootloader logs mention 4GB (and I should have purchased a VIM3 Pro)
<tomeu> this is the kernel log: https://paste.debian.net/1262362/
<narmstrong> tomeu: it may happen with vendor u-boot not updating the dt correctly
GNUtoo has quit [Ping timeout: 255 seconds]
GNUtoo has joined #linux-amlogic
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
<lvrp16> Speaking of u-boot and LAVA. Did u guys see the u-boot wget patches? Does open interesting applications but also a huge attack surface especially if people don't have a process to check signatures.
<lvrp16> Give users just enough rope to hang themselves.
<narmstrong> If it's only enabled for CI u-boots, I don't think it's worse than tftp or smb...
<tomeu> narmstrong: is there a safe way to update the u-boot in SPI? there used to be https://docs.khadas.com/vim3/BootFromSpiFlash.html but that seems to have gone away
Ballerburg9005 has joined #linux-amlogic
<narmstrong> indeed they removed all pages on spi flash boot
<narmstrong> the safest would be the flash the current bootloader on emmc, then try to replace the one in SPI
<tomeu> narmstrong: because if something goes wrong with the one in SPI, the board will fall back to emmc?
<narmstrong> If the binary is invalid yes
<narmstrong> If it’s broken, no
<tomeu> narmstrong: and the same images that can be booted from SD can be used to boot from SPI or eMMC? (sorry to ask, but I'm not finding any docs for mainline u-boot on internal storage)
<narmstrong> The same boot binary will work from sd emmc or spi
<narmstrong> But you’ll have to extract the boot binary from the sd or emmc image to flash it on spi
camus has quit [Remote host closed the connection]
jernej has joined #linux-amlogic
Ballerburg9005 has quit [Ping timeout: 255 seconds]
jelly has quit [Remote host closed the connection]
GNUtoo has quit [Remote host closed the connection]
GNUtoo has joined #linux-amlogic
jelly has joined #linux-amlogic
GNUtoo has quit [Ping timeout: 255 seconds]
GNUtoo has joined #linux-amlogic
jernej has quit [Quit: Konversation terminated!]
jernej has joined #linux-amlogic
Tartarus has quit [Quit: Bridge terminating on SIGTERM]
BlueMatt[m] has quit [Quit: Bridge terminating on SIGTERM]
psydroid has quit [Quit: Bridge terminating on SIGTERM]
Tartarus has joined #linux-amlogic
BlueMatt[m] has joined #linux-amlogic
psydroid has joined #linux-amlogic
vagrantc has joined #linux-amlogic
naoki has quit [Quit: naoki]
naoki has joined #linux-amlogic
naoki has quit [Client Quit]
naoki has joined #linux-amlogic
naoki has quit [Quit: naoki]
JohnnyonFlame has quit [Read error: Connection reset by peer]
JohnnyonFlame has joined #linux-amlogic
GNUtoo has quit [Ping timeout: 255 seconds]
GNUtoo has joined #linux-amlogic
tdebrouw has quit [Quit: Leaving.]
Ballerburg9005 has joined #linux-amlogic
JohnnyonF has joined #linux-amlogic
JohnnyonFlame has quit [Ping timeout: 260 seconds]
ldevulder has quit [Read error: Connection reset by peer]
ldevulder has joined #linux-amlogic
vagrantc has quit [Quit: leaving]
naoki has joined #linux-amlogic
jernej has quit [Ping timeout: 248 seconds]
anessen97 has quit [Quit: The Lounge - https://thelounge.chat]
Guest9 has joined #linux-amlogic
Guest9 has quit [Write error: Broken pipe]
anessen97 has joined #linux-amlogic