From: khilman@linaro•org (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: OMAP baseline test results for v3.10-rc6
Date: Wed, 26 Jun 2013 13:56:10 -0700 [thread overview]
Message-ID: <87ppv8r3px.fsf@linaro.org> (raw)
In-Reply-To: <79CD15C6BA57404B839C016229A409A83ECC952D@DBDE04.ent.ti.com> (Vaibhav Hiremath's message of "Wed, 26 Jun 2013 04:53:14 +0000")
"Hiremath, Vaibhav" <hvaibhav@ti•com> writes:
>> -----Original Message-----
>> From: linux-arm-kernel [mailto:linux-arm-kernel-
>> bounces at lists.infradead.org] On Behalf Of Kevin Hilman
>> Sent: Wednesday, June 26, 2013 1:28 AM
>> To: Rini, Tom
>> Cc: Paul Walmsley; linux-omap at vger.kernel.org; linux-arm-
>> kernel at lists.infradead.org; Balbi, Felipe; Hiremath, Vaibhav
>> Subject: Re: OMAP baseline test results for v3.10-rc6
>>
>> Tom Rini <trini@ti•com> writes:
>>
>> > On 06/25/2013 02:20 PM, Paul Walmsley wrote:
>> >> + Vaibhav and Kevin
>> >>
>> >> Hi,
>> >>
>> >> On Tue, 25 Jun 2013, Felipe Balbi wrote:
>> >>
>> >>> On Mon, Jun 17, 2013 at 05:23:17AM +0000, Paul Walmsley wrote:
>> >>>> Boot to userspace:
>> >>>> FAIL ( 3/12): 37xxevm, am335xbone, am335xbonelt
>> >>>
>> >>> Paul, we have at least 2 different folks who can't reproduce your
>> bone
>> >>> and bone black boot to userspace failures. I wonder how you're
>> trying to
>> >>> boot them.
>> >>>
>> >>> Care to share your test scripts ?
>> >>
>> >> Sure... the methodology is completely open and has been posted in
>> the
>> >> online logs since the first test cycle. (For some reason, almost no
>> one
>> >> clicks through the test directory trees that I post online. Is this
>> a
>> >> documentation issue? What can we do to make it easier for people to
>> >> explore this?)
>> >
>> > Well, another link never hurts the search results :)
>> >
>> > [snip]
>> >> Am certainly open to the idea that there's something wrong with the
>> way
>> >> that I'm booting either of these. But AFAIK no one's been able to
>> >> identify exactly what it could be. I haven't had the time recently
>> to
>> >> spend hours going through the various permutations, given all the
>> other
>> >> breakage :-( BeagleBone-white has the additional complication that
>> it is
>> >> not easy to automate, due to the way that power is delivered to the
>> board,
>> >> so there is an extra dimension of difficulty there.
>> >
>> > Ah-ha, I reproduced your failure. If I make up a concat uImage +
>> DTB,
>> > rather than pass them separately, it fails to boot. If you switch to
>> > mainline U-Boot (v2012.10 or later) you get support for separate
>> image +
>> > dtb (v2013.04 gives you bootz and zImage support). v2013.04 will
>> also
>> > work out of the box for BeagleBone-Black.
>>
>> 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.
>>
>> Can you guys update your tests to test appended DTB also?
>>
>
> What is missing here is,
>
> CONFIG_ARM_APPENDED_DTB = y
> CONFIG_ARM_ATAG_DTB_COMPAT = y
Yes, yes... I use these options since I use appended DT with mainline
for *many* boards. Only the beaglebone stopped working.
I just tested v3.10-rc7 and it's back to working again for me with
appended DT. I did not spend anymore time to figure out exactly which
versions worked or didn't work.
Kevin
next prev parent reply other threads:[~2013-06-26 20:56 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
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 [this message]
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=87ppv8r3px.fsf@linaro.org \
--to=khilman@linaro$(echo .)org \
--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