* Derald D. Woods <woods.technical@xxxxxxxxx> [171212 16:34]: > On Tue, Dec 12, 2017 at 07:39:30AM +0100, Ladislav Michl wrote: > > On Mon, Dec 11, 2017 at 10:12:13PM -0600, Derald D. Woods wrote: > > > The partition information was omitted during the conversion to OMAP3430 > > > specific data. > > > > That could be intentional... > > I am fixing an addition that I created. > > > > > > The data added by this commit is consistent with current U-Boot default > > > definitions. > > > > What about passing U-Boot partitions information to kernel instead? > > > > I am testing using an appended device-tree. This has been the most > reliable method for the OMAP34XX boards that I have. If you have an > example config, with working command line MTDPARTS, for beagleboard(Rev. > C4), Overo TOBI, or similiar OMAP34XX, I will gladly use it. Also note > that other OMAP34XX boards currently provide a default partition > layout. Is that bad practice for all of those as well? I am open to > exploring the method that actually works. I think we came to the conclusion at some point that it's best to rely on u-boot passed partitions because with later u-boot versions the size was increased for the bootloader partition. Ideally of course we would read the partition information from the MTD device somewhere.. Regards, Tony -- 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
