15:54 <mmind00> rperier: IIRC (and git log seems to confirm it) you had a veyron-speedy ... do you remember if it has/had issues with tuning for the (internal) emmc? I just like to cross-check the patch from vagrantc :-)

16:36 <mmind00> vagrantc: :-)

16:38 <vagrantc> for veyron-speedy

17:22 <rperier> mmind00: for now I mainly tested it with an sdcard , however I can do advanced test cases if you want :)

17:25 <mmind00> rperier: I guess it should be enough to see if the emmc manages to tune (kernel messages), is mountable and can maybe survive a hdparm test run

17:25 <mmind00> vagrantc: or did you do anything special to make the tuning emmc break?

17:26 <vagrantc> mmind00: it was only an issue when using eMMC for rootfs ... worked fine when booting with SD as rootfs

17:26 <vagrantc> or, at least, mostly

17:27 <vagrantc> it booted maybe 1 out of 10 times with eMMC for rootfs, with the patch i haven't seen it fail once ...

17:27 <vagrantc> sorry i didn't provide a very good test case or more detail ...

18:45 <vagrantc> hrm... if i can't get an initrd to work ... maybe i can try kexec...

20:29 <mmind00> vagrantc: I'm plagued with bad memory, but IIRC the FIT image format itself can handle initramfs things, but depthcharge does not care about that

20:30 <vagrantc> mmind00: newish versions of depthcharge appear to make *some* attempt at using the initramfs from the FIT image ...

20:31 <vagrantc> but when the kernel boots, it apparently hasn't been passed the right address, or it is passed the right address, but depthcharge didn't load anything there...

20:32 <vagrantc> spits out some message like: initramfs: junk in archive

20:47 <mmind00> vagrantc: of course you don't really know how newish the depthcharge in your speedy is

20:50 <vagrantc> mmind00: i built libreboot and installed it, and i *think* the version it included "supports" intird

20:50 <vagrantc> mmind00: but honestly, the libreboot build toolchain is a bit much to follow

20:51 <vagrantc> mmind00: when i used whatever shipped on the speedy it refused to boot FIT images with an initrd

20:52 <vagrantc> other option is to try and adapt the veyron-jerry u-boot... but that's getting in a little deeper than i'd like

20:53 <mmind00> vagrantc: hehe ... I try to stay away from firmware as much as I can (except when there is a clear path to recover) and am mostly happy once it (net-)boots my kernels :-)

20:56 <vagrantc> hmmm... rethinking this ... maybe it would recognize a smaller initramfs ... on another board i got the same "junk in archive" message when booting a large initramfs