<hexdump0815>
just to add some of my thoughts to this discussion: i think we have two groups of devices here armv7l and aarch64
<hexdump0815>
aarch64 is not a problem as depthcharge is good enough to support things like initrd etc.
<hexdump0815>
on armv7l there is a wild mix of boot loaders exynos is somehow ancient u-boot based while later ones are based on older coreboot i think
<hexdump0815>
one important point about armv7l devices is: there is only a limited number of them and there will be no new ones
<hexdump0815>
as a result there is just some solution required which covers all existing armv7l devices somehow - it does not have to be perfect as the userbase is very small anyway
<hexdump0815>
this is why i neded up using u-boot for armv7l as it exists for all armv7l in some form (maybe even an older version only, but it can at least be reliably compiled from source)
<hexdump0815>
ended up using i mean
<hexdump0815>
i think being able to use initrd for things like luks is something essential for any kind of mobile device
<hexdump0815>
for aarch64 i'm simply sticking to depthcharge as this is what each chromebook is coming with and its good enough for what is needed
<hexdump0815>
one good thing about u-boot (chainloaded via legacy bootloader) is that you cannot brick the device by using it - if it does not work, just replace it with a working u-boot or a kpart kernel
<hexdump0815>
same is trut for depthcharge on aarch64 as nothing needs to be changed on the chromebook to use it
<hexdump0815>
i even prefer to use rw efi payload on newer intel chromebooks over writing efi to flash as the second option can really brick the device
<hexdump0815>
and flashing the device from outside with a programmer is no real fun and nothing for everyone (i did it a few times and i prefer to not having to do it again)
<jenneron[m]>
btw it seems that usb on spring now works reliably for me
<jenneron[m]>
i've ordered a few things for debugging with usb
<hexdump0815>
jenneron[m]: that is good news - did you change anything in the code or on the device?
<jenneron[m]>
did a new installation, not sure what fixed it
<jenneron[m]>
it might be corrupted fs, might be that I don't use u-boot anymore