All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Vaussard <florian.vaussard@epfl.ch>
To: Kevin Hilman <khilman@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>, Tero Kristo <t-kristo@ti.com>,
	kernel-build-reports@lists.linaro.org,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	Mike Turquette <mturquette@linaro.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	Olof Johansson <olof@lixom.net>, Ash Charles <ash@gumstix.com>
Subject: Re: next boot: 34 pass, 5 fail (next-20140122)
Date: Thu, 06 Feb 2014 09:47:55 +0100	[thread overview]
Message-ID: <52F34C3B.4030503@epfl.ch> (raw)
In-Reply-To: <CAGa+x86d4BbefALJhY2c=kMFmpJ+SLGu2ibfwuZxStCzXm65Uw@mail.gmail.com>

Hi Kevin,

On 02/05/2014 04:23 PM, Kevin Hilman wrote:
> On Fri, Jan 24, 2014 at 10:13 AM, Florian Vaussard
> <florian.vaussard@epfl.ch> wrote:
>> Hi,
>>
>> On 01/24/2014 07:11 PM, Tony Lindgren wrote:
>>> * Florian Vaussard <florian.vaussard@epfl.ch> [140123 01:17]:
>>>>
>>>> I just tested next-20140123 with an OMAP3630 ES1.2 Overo/Tobi. Changing
>>>> the include to omap36xx.dtsi do not fix the issue. I still get the
>>>> external abort on non-linefetch (full log here [1]).
>>>
>>> I think the issue here is that you need to have "ti,omap36xx" in
>>> the compatible string in addition to including omap36xx.dtsi.
>>> Otherwise "ti,omap3" will initialize things for 34xx.
>>>
>>> For the initial minimal fix, I suggest we do something like the
>>> following. This should fix things for 36xx based tobi, then
>>> 34xx based tobi support can be added later on. Untested as I
>>> don't have one.
>>>
>>
>> You are probably right. I will test Monday.
> 
> Any progress on this?
> 
> We still have the 36xx Tobi boards failing basic boot tests -next, but
> now also in mainline.
> 

Thanks for the reminder. Tony's patch fixes the problem for 36xx Overo,
but makes 35xx Overo to fail. I did a patch to split the Tobi between a
common include file, and model-specific DTS. Will send it in a couple of
minutes.

Regards,

Florian

      reply	other threads:[~2014-02-06  8:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52e06652.c103450a.79d7.6517@mx.google.com>
2014-01-23  1:35 ` next boot: 34 pass, 5 fail (next-20140122) Kevin Hilman
2014-01-23  6:23   ` Tero Kristo
2014-01-23  8:14     ` Florian Vaussard
2014-01-23  9:00       ` Tero Kristo
2014-01-23  9:15         ` Florian Vaussard
2014-01-23  9:41           ` Florian Vaussard
2014-01-23 12:27             ` Tero Kristo
2014-01-23 16:35               ` Florian Vaussard
2014-01-23 17:33                 ` Nishanth Menon
2014-01-24 20:37                   ` Florian Vaussard
2014-01-23 17:35                 ` Tony Lindgren
2014-01-24 18:00                   ` Tony Lindgren
2014-01-24 20:51                   ` Florian Vaussard
2014-01-24 18:11           ` Tony Lindgren
2014-01-24 18:13             ` Florian Vaussard
2014-02-05 15:23               ` Kevin Hilman
2014-02-06  8:47                 ` Florian Vaussard [this message]

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=52F34C3B.4030503@epfl.ch \
    --to=florian.vaussard@epfl.ch \
    --cc=ash@gumstix.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=khilman@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=olof@lixom.net \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.