On Tue, Nov 08, 2016 at 11:19:20AM +0100, Maxime Ripard wrote: [snip] > I think the biggest drawback at the moment is that we maintain a list of > DIPs and the actions needed directly into the C code, which will make it > quite hard to customise for end users and tedious to maintain in the long > term. I couldn't really get my head around a better solution, so feel free > to suggest alternative approaches.
A thought I had after reading over 8/9 in the series was, could we try something like: - In C, loop over everything in w1 and set environment variables based on each thing we find. - In a CONFIG_PREBOOT load a U-Boot shell script in that will look for the right env variables to be set for a given DIP and then do whatever is needed to load in the overlay. Does that make sense? -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
