On Tue, Jan 13, 2015 at 12:42:20PM -0800, Tony Lindgren wrote: > * Arnd Bergmann <arnd@xxxxxxxx> [150113 12:27]: > > 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. > > > > 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. Apart from the bugs there is only one feature-wise regression when the system is booted via DT, which is the accelerometer. I will (re)send patches for that in the next days. -- Sebastian
Attachment:
signature.asc
Description: Digital signature
