01:45 <Tartarus> SlimeyX: Sounds like vendor tree "fun"

02:12 <SlimeyX> heh indeed

02:12 <SlimeyX> at least i git it to build this time

02:12 <SlimeyX> got

02:16 <SlimeyX> solved a BIG piece of the puzzle at least

02:17 <SlimeyX> had to create the user and path that appears to be hard coded into the source >:(

02:22 <SlimeyX> lots of make -d to figure that out

02:28 <tpw_rules> classic

03:33 <SlimeyOTG> http://fuckingcisco.com/ used to be one for adtran too

04:23 <icee> Hey-- i have an application that's a bit paranoid about boot media corruption... I'd really like to get a very small boot image that checks whether one of a few images has a proper shasum or whatever, and boots the first proper one. This isn't for security: no signatures, etc, needed

04:24 <icee> Basically, it's a secondary payload on a satellite and random bit errors accumulating in our flash media isn't that unlikely. Is there any easy way to cobble uboot to do this? I see a lot of functionality that is kind of close to this

04:25 <icee> (I'd be wanting to look at an entire root filesystem, odds are, not just an image to load)

04:25 <icee> (i'm of course considering things like initrd to do the same)

04:31 <Forty-Bot> U-Boot won't boot an image with a bad hash

04:32 <Forty-Bot> so the easiest way is to just try to boot from several locations in sequence

04:34 <Forty-Bot> the traditional way is a script like `set imagename=linux.0.img; run bootlinux; set imagename=linux.1.img; runbootlinux` etc

04:35 <Forty-Bot> but there is probably a bootstd way as well if you like

04:35 <icee> Is there any way to get it to scan the rootfs too? Or do i need to do this at the uboot level, and then once again with an initramfs that finds a valid readonly root filesystem

04:36 <Forty-Bot> what do you mean by scan

04:36 <icee> hash, compare to signature

04:36 <Forty-Bot> idk

04:36 <Forty-Bot> maybe you can use a raid 0 with dm-verity?

04:37 <Forty-Bot> or, actually I think there is some other dm layer that just does ecc

04:37 <icee> ah, dm-verity + raid1 seems cool

04:38 <icee> this whole thing is expected to have crap life in LEO. I just want to improve the odds of it lasting a few months

04:38 <Forty-Bot> yeah, raid 1

04:38 <Forty-Bot> or whatever the redundancy one is

04:39 <icee> all the critical stuff is running off MRAM with ECC

04:39 <icee> but then we're flying a pi zero 2 w to run the camera

04:40 <icee> thanks for the ideas, this is helpful

04:40 <Forty-Bot> yeah, try dm-verity with fec

14:47 <Tartarus> sjg1: Please stop posting massive patchsets for your fork to the mailing list.

18:24 <xypron> Tartarus: https://patchwork.ozlabs.org/project/uboot/list/?series=435653 looks fine for me.

18:44 <Tartarus> xypron: Do you want to put it in a PR should should I just take it?

18:45 <xypron> Tartarus: You can just take it. I still have to go through all the patches for an origin/next PR.

18:45 <Tartarus> OK, thanks