From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: OMAP baseline test results for v3.13-rc1 (toolchain Debian 4.7.2-5)
Date: Mon, 25 Nov 2013 08:30:31 -0800 [thread overview]
Message-ID: <20131125163031.GQ10023@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311251514330.1364@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [131125 07:16]:
> On Mon, 25 Nov 2013, Paul Walmsley wrote:
>
> > Boot to userspace:
> > FAIL ( 1/11): 37xxevm
>
> An auto-bisect traced this to:
>
> commit 95807689eab8441737572d1a9daaa1025429a908
> Author: Tony Lindgren <tony@atomide.com>
> Date: Mon Oct 14 11:31:43 2013 -0700
>
> ARM: OMAP2+: Remove legacy booting support for omap3 EVM
>
> We now have pretty decent support with the device tree
> based booting. Patches to add more features are welcome.
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
>
> So looks like this is due to the switchover to DT-based booting for 37xx
> EVM. Will plug that in here and re-test.
Yes. Also there's the patch missing to enable wake-up interrupts, but
that has a dependency to populating IRQ resources dynamically to avoid
nasty warnings. Both should get fixed during the -rc cycle though.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP baseline test results for v3.13-rc1 (toolchain Debian 4.7.2-5)
Date: Mon, 25 Nov 2013 08:30:31 -0800 [thread overview]
Message-ID: <20131125163031.GQ10023@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311251514330.1364@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [131125 07:16]:
> On Mon, 25 Nov 2013, Paul Walmsley wrote:
>
> > Boot to userspace:
> > FAIL ( 1/11): 37xxevm
>
> An auto-bisect traced this to:
>
> commit 95807689eab8441737572d1a9daaa1025429a908
> Author: Tony Lindgren <tony@atomide.com>
> Date: Mon Oct 14 11:31:43 2013 -0700
>
> ARM: OMAP2+: Remove legacy booting support for omap3 EVM
>
> We now have pretty decent support with the device tree
> based booting. Patches to add more features are welcome.
>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
>
> So looks like this is due to the switchover to DT-based booting for 37xx
> EVM. Will plug that in here and re-test.
Yes. Also there's the patch missing to enable wake-up interrupts, but
that has a dependency to populating IRQ resources dynamically to avoid
nasty warnings. Both should get fixed during the -rc cycle though.
Regards,
Tony
next prev parent reply other threads:[~2013-11-25 16:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 7:41 OMAP baseline test results for v3.13-rc1 (toolchain Debian 4.7.2-5) Paul Walmsley
2013-11-25 7:41 ` Paul Walmsley
2013-11-25 15:15 ` Paul Walmsley
2013-11-25 15:15 ` Paul Walmsley
2013-11-25 16:30 ` Tony Lindgren [this message]
2013-11-25 16:30 ` Tony Lindgren
2013-12-09 9:54 ` Paul Walmsley
2013-12-09 9:54 ` Paul Walmsley
2013-12-09 17:16 ` Tony Lindgren
2013-12-09 17:16 ` Tony Lindgren
2013-12-09 19:14 ` Tony Lindgren
2013-12-09 19:14 ` Tony Lindgren
2013-12-09 19:32 ` Tony Lindgren
2013-12-09 19:32 ` Tony Lindgren
2013-12-09 21:34 ` Sergei Shtylyov
2013-12-09 21:34 ` Sergei Shtylyov
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=20131125163031.GQ10023@atomide.com \
--to=tony@atomide.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.