From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] make mach-omap2 boot with device tree only for v3.14
Date: Tue, 17 Dec 2013 07:26:54 -0800 [thread overview]
Message-ID: <20131217152653.GM12324@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1312170707140.14039@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [131216 23:16]:
> On Fri, 13 Dec 2013, Tony Lindgren wrote:
>
> > OK posted a patch for the SBC-T3730 with minimal support also for
> > SBC-3530 and SBC-3517 that should boot far enough to start adding
> > more devices. Paul, care to try it on the CM-T3517, the patch is:
> >
> > [PATCH] ARM: dts: Add support for sbc-3xxx with cm-t3730
>
> Didn't get anything out of the serial port:
>
> http://www.pwsan.com/omap/testlogs/test_tonys_conversion_v3.14/20131215235827/boot/cmt3517/cmt3517_log.txt
OK thanks for testing. Looks like the CompuLab guys will need to
take a look at it. I'll update my patch for SBC-T3730 only with the
comments from Igor.
> As a partial sanity check, AM3517 EVM was included as part of the run
> (with a separate uImage+dtb of course) and that seems to boot OK:
>
> http://www.pwsan.com/omap/testlogs/test_tonys_conversion_v3.14/20131215235827/boot/3517evm/3517evm_log.txt
Hmm OK, weird that the 3517 EVM boots but not the CM-T3517.
> In case it's useful, here's a CM-T3517 boot log from v3.13-rc4:
>
> http://www.pwsan.com/omap/testlogs/test_v3.13-rc4/20131215195251/boot/cmt3517/cmt3517_log.txt
OK thanks.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] make mach-omap2 boot with device tree only for v3.14
Date: Tue, 17 Dec 2013 07:26:54 -0800 [thread overview]
Message-ID: <20131217152653.GM12324@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1312170707140.14039@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [131216 23:16]:
> On Fri, 13 Dec 2013, Tony Lindgren wrote:
>
> > OK posted a patch for the SBC-T3730 with minimal support also for
> > SBC-3530 and SBC-3517 that should boot far enough to start adding
> > more devices. Paul, care to try it on the CM-T3517, the patch is:
> >
> > [PATCH] ARM: dts: Add support for sbc-3xxx with cm-t3730
>
> Didn't get anything out of the serial port:
>
> http://www.pwsan.com/omap/testlogs/test_tonys_conversion_v3.14/20131215235827/boot/cmt3517/cmt3517_log.txt
OK thanks for testing. Looks like the CompuLab guys will need to
take a look at it. I'll update my patch for SBC-T3730 only with the
comments from Igor.
> As a partial sanity check, AM3517 EVM was included as part of the run
> (with a separate uImage+dtb of course) and that seems to boot OK:
>
> http://www.pwsan.com/omap/testlogs/test_tonys_conversion_v3.14/20131215235827/boot/3517evm/3517evm_log.txt
Hmm OK, weird that the 3517 EVM boots but not the CM-T3517.
> In case it's useful, here's a CM-T3517 boot log from v3.13-rc4:
>
> http://www.pwsan.com/omap/testlogs/test_v3.13-rc4/20131215195251/boot/cmt3517/cmt3517_log.txt
OK thanks.
Tony
next prev parent reply other threads:[~2013-12-17 15:27 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 2:42 [GIT PULL] make mach-omap2 boot with device tree only for v3.14 Tony Lindgren
2013-12-10 14:35 ` Russell King - ARM Linux
2013-12-10 14:35 ` Russell King - ARM Linux
2013-12-10 16:01 ` Tony Lindgren
2013-12-10 16:01 ` Tony Lindgren
2013-12-10 16:07 ` Russell King - ARM Linux
2013-12-10 16:07 ` Russell King - ARM Linux
2013-12-10 16:59 ` Tony Lindgren
2013-12-10 16:59 ` Tony Lindgren
2013-12-10 20:36 ` Tony Lindgren
2013-12-10 20:36 ` Tony Lindgren
2013-12-10 18:36 ` Arnd Bergmann
2013-12-10 18:36 ` Arnd Bergmann
2013-12-10 18:43 ` Tony Lindgren
2013-12-10 18:43 ` Tony Lindgren
2013-12-10 18:45 ` Paul Walmsley
2013-12-10 18:45 ` Paul Walmsley
2013-12-10 18:59 ` Tony Lindgren
2013-12-10 18:59 ` Tony Lindgren
2013-12-10 19:08 ` Tony Lindgren
2013-12-10 19:08 ` Tony Lindgren
2013-12-10 19:27 ` Tony Lindgren
2013-12-10 19:27 ` Tony Lindgren
2013-12-10 19:39 ` Arnd Bergmann
2013-12-10 19:39 ` Arnd Bergmann
2013-12-10 19:44 ` Paul Walmsley
2013-12-10 19:44 ` Paul Walmsley
2013-12-10 19:50 ` Tony Lindgren
2013-12-10 19:50 ` Tony Lindgren
2013-12-10 23:07 ` Tony Lindgren
2013-12-10 23:07 ` Tony Lindgren
2013-12-13 19:26 ` Tony Lindgren
2013-12-13 19:26 ` Tony Lindgren
2013-12-17 7:14 ` Paul Walmsley
2013-12-17 7:14 ` Paul Walmsley
2013-12-17 15:26 ` Tony Lindgren [this message]
2013-12-17 15:26 ` Tony Lindgren
2013-12-10 23:56 ` Paul Walmsley
2013-12-10 23:56 ` Paul Walmsley
-- strict thread matches above, loose matches on Subject: below --
2013-12-10 2:42 Tony Lindgren
2013-12-10 2:42 Tony Lindgren
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=20131217152653.GM12324@atomide.com \
--to=tony@atomide.com \
--cc=arm@kernel.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.