public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: trini@ti•com (Tom Rini)
To: linux-arm-kernel@lists•infradead.org
Subject: OMAP baseline test results for v3.10-rc6
Date: Wed, 26 Jun 2013 07:27:28 -0400	[thread overview]
Message-ID: <51CAD020.5090704@ti.com> (raw)
In-Reply-To: <20130626091522.GT21614@n2100.arm.linux.org.uk>

On 06/26/2013 05:15 AM, Russell King - ARM Linux wrote:
> On Tue, Jun 25, 2013 at 04:22:29PM -0400, Tom Rini wrote:
>> On 06/25/2013 03:57 PM, Kevin Hilman wrote:
>>> Just to confirm, my problems with mainline were with appended DTB also.
>>> Separate DTB and zImage work fine (at least using u-boot v2013.04.)
>>>
>>> That being said, appended DTB should still work, so there's a bug hiding
>>> someplace that needs to be found fixed.
>>
>> Since we've narrowed down what the problem is, someone can bisect it
>> now, yeah.
>>
>>> Can you guys update your tests to test appended DTB also?
>>
>> What is the official position on appending DTBs?
> 
> If a platform goes from being able to boot without a DTB to requiring
> a DTB, we must continue to support booting on that platform in some
> manner otherwise it is a regression.
> 
> And no, I don't term upgrading uboot as an acceptable regression fix.
> So if appended DTB doesn't work, that needs fixing before the non-DTB
> support for a platform is removed, otherwise we _will_ have a regression.

am335x never had a board file in mainline, so it's always required a DTB.

Now, I assume you're still saying that whatever software, except for the
kernel of course, shipped on the SD card, has to be supported for
forever by the kernel, right?

-- 
Tom

  reply	other threads:[~2013-06-26 11:27 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-17  5:23 OMAP baseline test results for v3.10-rc6 Paul Walmsley
2013-06-25 16:02 ` Felipe Balbi
2013-06-25 18:20   ` Paul Walmsley
2013-06-25 19:34     ` Tom Rini
2013-06-25 19:57       ` Kevin Hilman
2013-06-25 20:22         ` Tom Rini
2013-06-26  9:15           ` Russell King - ARM Linux
2013-06-26 11:27             ` Tom Rini [this message]
2013-06-26  4:53         ` Hiremath, Vaibhav
2013-06-26 13:22           ` Rajendra Nayak
2013-06-26 13:26             ` Tom Rini
2013-06-26 17:28               ` Paul Walmsley
2013-06-26 17:45                 ` Tom Rini
2013-06-26 17:58                   ` Paul Walmsley
2013-06-26 20:02                     ` Tom Rini
2013-06-26 23:57                       ` Kevin Hilman
2013-06-26 17:26             ` Paul Walmsley
2013-06-27  4:17               ` Lokesh Vutla
2013-06-28 18:45                 ` Paul Walmsley
2013-07-01  2:15                   ` Paul Walmsley
2013-07-02  4:29                     ` Hiremath, Vaibhav
2013-07-02 14:15                       ` Nishanth Menon
2013-07-03 19:51                         ` Paul Walmsley
2013-07-04 18:12                           ` Paul Walmsley
2013-07-05  5:48                             ` Rajendra Nayak
2013-07-05 14:14                               ` Tom Rini
2013-07-05 15:44                               ` Paul Walmsley
2013-06-26 20:56           ` Kevin Hilman
2013-06-26 17:19       ` Paul Walmsley
2013-06-26 20:16         ` Tom Rini
2013-07-29  8:29           ` Paul Walmsley
2013-07-29 12:29             ` Tom Rini
2013-07-30 20:23               ` Paul Walmsley
2013-07-30 20:28                 ` Nishanth Menon
2013-06-25 20:39     ` Felipe Balbi
2013-06-26  4:57     ` Hiremath, Vaibhav
2013-06-26 16:51       ` Paul Walmsley
2013-06-26 17:41         ` Paul Walmsley
2013-06-26  9:21     ` Lokesh Vutla
2013-06-26 17:36       ` Paul Walmsley

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=51CAD020.5090704@ti.com \
    --to=trini@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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