On 05/12/2014 04:57 PM, Robert Nelson wrote: >>> Either case if fine with me. As who knows when the dtc "overlay" will >>> every truly make it mainline, as the capemgr was the only real kernel >>> user of the i2c/at24 eeprom information. >> >> Sounds like we should keep it disabled though so u-boot can be used >> to toggle it while waiting for the capemgr. That's because the board >> has a header for pins, so it's not exactly limited to just the capes. >> >> Anybody working on enabling/disabling cape dtb configurations in u-boot? > > Well, > > Would Tom even approve of that in mainline u-boot? He didn't want my > "invert" the gpio to enable the usb hub on the older beagle xm A/B.. > > http://lists.denx.de/pipermail/u-boot/2014-January/172154.html > > http://lists.denx.de/pipermail/u-boot/2014-January/172274.html I would think that using the 'fdt' command in U-Boot to add all properties of every cape found on a running system would drive someone to madness quite quickly. Moving all of Pantelis' work for dynamic device trees from the kernel to N bootloaders (U-Boot, barebox, UEFI, etc) sounds like a step in the wrong direction. -- Tom -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
