On Thu, 2018-06-21 at 09:58 -0700, Olof Johansson wrote: > On Thu, Jun 21, 2018 at 9:50 AM, Andre Przywara <andre.przywara@arm.c > om> wrote: > > Hi, > > /cut > > So you probably want a way to identify a U-Boot version by looking > > at > > the storage it resides on. This seems more like a U-Boot problem, > > last > > time I checked I couldn't find any generic way of doing that. The > > best > > thing I could come up with was to scan the image for the U-Boot > > banner > > string. That is pretty reliable on the SPL, because this image is > > much > > smaller and the string to match is more specific: I did a memmem() > > for > > "U-Boot SPL 20", which had only one hit in my case. But still this > > is a > > bit dodgy. > > So the binding can include a property that tells you where the > firmware was booted from, so you can go read that device and see what > version is stored there. Why can't we just trust U-Boot in telling us its own version? -- To unsubscribe from this list: send the line "unsubscribe devicetree-spec" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
