On Thu, Aug 03, 2017 at 07:37:34AM -0500, Derald Woods wrote:
On Thu, Aug 3, 2017 at 6:31 AM, Tom Rini trini@konsulko.com 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 woods.technical@gmail.com
Reviewed-by: Tom Rini trini@konsulko.com
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-OMA...
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?
Ah yes, I had that on my to reply to list, sorry. What I was wondering was, why does current mainline fail? I had tested that series on the beagleboard xM but indeed not on plain beagleboard.