linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sre@kernel.org (Sebastian Reichel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Drop legacy support for omap3517
Date: Thu, 15 Jan 2015 15:25:36 +0100	[thread overview]
Message-ID: <20150115142536.GC512@earth.universe> (raw)
In-Reply-To: <20150113204219.GJ2419@atomide.com>

On Tue, Jan 13, 2015 at 12:42:20PM -0800, Tony Lindgren wrote:
> * Arnd Bergmann <arnd@arndb.de> [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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150115/86546acf/attachment.sig>

  parent reply	other threads:[~2015-01-15 14:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13 17:57 [PATCH 0/4] Drop legacy support for omap3517 Tony Lindgren
2015-01-13 17:57 ` [PATCH 1/4] ARM: OMAP3: Remove legacy support for am3517-evm Tony Lindgren
2015-01-13 17:57 ` [PATCH 2/4] ARM: OMAP3: Remove legacy support for am3517crane Tony Lindgren
2015-01-13 17:57 ` [PATCH 3/4] ARM: OMAP3: Remove cm-t3517 legacy support Tony Lindgren
2015-01-13 17:57 ` [PATCH 4/4] ARM: OMAP3: Remove legacy support for am35xx-emac Tony Lindgren
2015-01-13 20:24 ` [PATCH 0/4] Drop legacy support for omap3517 Arnd Bergmann
2015-01-13 20:42   ` Tony Lindgren
2015-01-13 20:50     ` Pali Rohár
2015-01-18 21:02       ` Pavel Machek
2015-01-18 22:29         ` Sebastian Reichel
2015-01-15 14:25     ` Sebastian Reichel [this message]
2015-01-24 12:00       ` Pali Rohár
2015-01-24 22:08         ` Arnd Bergmann
2015-01-24 22:14           ` Pali Rohár
2015-01-26 10:16             ` Arnd Bergmann
2015-01-25 21:23           ` Pavel Machek
2015-01-25 15:18         ` Sebastian Reichel
2015-01-25 21:22         ` Pavel Machek
2015-01-25 21:49           ` Sebastian Reichel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150115142536.GC512@earth.universe \
    --to=sre@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).