Drop legacy support for omap3517
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
| Patch | Pavel Machek |
|---|---|
| Series | A-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] Drop legacy support for omap3517
Quoted 10 lines · Arnd Bergmann
Quoted 8 lines · On Tuesday 13 January 2015 09:57:41 Tony Lindgren wrote:
It seems we can now drop omap3517 legacy booting support to get a bit closer to making all of omap3 boot in device tree only mode.
All these boards have at least minimal support for booting with device tree, and pretty much anything supported with the legacy board files can be configured also for device tree based booting if not done already.
Quoted 4 lines
Ah, very nice.
Just out of curiosity, what are the remaining showstoppers for the 3430 and 3530 based boards?
Not much really. We're now printing a warning to get a people to upgrade their systems. So with some boards we need to wait a while.
Then here are the remaining items that I'm aware of:
- A regression at least on some n900 with appended DTB not booting properly any longer reported by Pali
- A regression where the legacy ATAGs don't seem to get properly translated by the uncompress code for atag_rev at least reported by Pali
- A few missing .dts files for devkit8000, omap3logic, omap3stalker, omap3pandora and omap3touchbook
Pali and Sebastian probably know best of any other remaining issues to drop n900 legacy booting.
If people have the boards listed above, please pitch in to do the .dts files or send the boards to me and I can do minimal .dts files for them.
Regards,
Tony