>> I recall looking at a newer uboot-tools (2015-01 I think), but it did >> not generate a booting system, so I got back to the tried 2011 version. >> We might want to do some testing before putting in a newer version. > > The latest uboot, as shipped with recent Fedoras doesn't even _build_ > on armv5tel (invalid assembly instructions). The reason why I built > the ones I mentioned was because I needed a more recent version to > uimage up a kernel for my Chromebook. I don't know whether the uboot > firmware payload itself works, but at least it builds (I only needed > mkimage). > maybe that is what I've seen. I just looked at the latest, it didn't work and went back.
> I'm currently looking at porting zfs-dracut to zfs-fuse, and then > I'll try to build a blob containing the device tree, kernel and the > initrd to try to get zfs-fuse-rootfs working. The outcome of this will > hopefully be reasonably portable to other things using similar uboot > (e.g. do your machines use uboot? I seem to recall you said that > running them with initrd was somewhat... experimental). yes that's for the raspi stuff. odroid needs the mkimage also. Jacco _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
