On Thu, Aug 3, 2017 at 6:31 AM, Tom Rini <[email protected]> wrote: > On Wed, Aug 02, 2017 at 10:00:06PM -0500, Derald D. Woods wrote: > > > This patch brings the OMAP3 EVM to a bootable state, on master, as of > > v2017.09-rc1. > > > > Signed-off-by: Derald D. Woods <[email protected]> > > Reviewed-by: Tom Rini <[email protected]> > > Thanks. Since you have one of these boards, would you like to take over > maintainership of it?
Yes. I do have this board, with the OMAP3530 processor module, and will be able to test releases. On a side note, I recently posted the following: http://u-boot.10912.n7.nabble.com/PATCH-arm-omap-Fix-get-device-type-for-OMAP34XX-td300937.html#a300993 I verified the small patch with omap3evm, beagleboard(revc4), and overo. CPU information can be directly read, as it was previously. Is there some consistent road-map for SRAM usage for OMAP34XX specifically? Derald > That means booting it at least once every 2 > months, ideally (at least on the final -rc before release, which is > pretty consistently scheduled) to catch bugs like this. Thanks again! > -- > Tom > _______________________________________________ U-Boot mailing list [email protected] https://lists.denx.de/listinfo/u-boot
