On Sat, Aug 25, 2018 at 7:22 PM, Tom Rini trini@konsulko.com wrote:
On Sat, Aug 25, 2018 at 06:58:19PM +0300, Grazvydas Ignotas wrote:
On Mon, Aug 20, 2018 at 8:43 PM, Tom Rini trini@konsulko.com wrote:
On Mon, Aug 20, 2018 at 07:45:16AM -0500, Adam Ford wrote:
On Mon, Aug 20, 2018 at 6:21 AM Tom Rini trini@konsulko.com wrote:
On Tue, Aug 07, 2018 at 07:28:11AM -0500, Adam Ford wrote:
Wasn't there a requirement that we need to move all boards to support CONFIG_DM at one point?
Yes, things should get moved to DM. So, adding the omap3_pandora listed maintainer to the email.
I'm sorry I haven't been following u-boot development for some years, what exactly needs to be done here? I've tried enabling CONFIG_DM_SERIAL, but then the board only prints some garbage and resets. Without changes current u-boot built from git boots fine.
Note that the device is old and only pre- device tree kernels are shipped and officially supported. However the mainline kernel still has incomplete board support (including device tree) for those wanting to use it.
So over in U-Boot, we're moving towards the point where having some device tree that describes the board will be a lot easier than not in terms of continuing to support the board. So, there's a few ways to look at things:
- If you take a look at 0d43fded20e3 you can see how omap3_evm was updated to use DM_SERIAL and a bunch of other modern things.
- You can also just say that it's time to retire omap3_pandora from mainline U-Boot and that v2018.09 (or v2018.11, but I don't want to wait too long) is the last release with support for the platform.
- See if there's anyone else you know that would like to pick up and maintain the board and make the kind of changes that were made to omap3_evm.
Thanks for the info. I've sent a patch, I hope it is sufficient.
GraÅžvydas