All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tushar Behera <trblinux@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>, "Kevin Hilman" <khilman@linaro.org>
Cc: Laura Abbott <lauraa@codeaurora.org>,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	Russell King <linux@arm.linux.org.uk>,
	kernel-build-reports@lists.linaro.org,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: mainline boot: 64 boots: 62 pass, 2 fail (v3.16-rc1-2-gebe0618)
Date: Fri, 27 Jun 2014 08:58:31 +0530	[thread overview]
Message-ID: <53ACE4DF.3040603@gmail.com> (raw)
In-Reply-To: <53AC5293.90209@suse.de>

On 06/26/2014 10:34 PM, Andreas Färber wrote:
> Hi Kevin and Tushar,
> 
> Am 26.06.2014 16:59, schrieb Kevin Hilman:
>>> IMO, the bug is in u-boot and we should fix that.
>>
>> I agree that the u-boot bug needs to be fixed, and FWIW, I updated my
>> u-boot and haven't seen the boot failure yet after several boots with
>> next-20140625.
> 
> Could you clarify your test setup: Are you using the original InSignal
> SPL [1] with just your own u-boot.bin? Or do you have access to some
> newer Samsung-signed SPL?
> 

The u-boot changes for Arndale-Octa was done as part of an activity
within Linaro. Insignal had signed the SPL binary for us. You can
extract the signed SPL binary from following hwpack[6] (tar xfz and then
within u_boot folder[7]).

The source code for this u-boot can be found here.[8]

Just in case, commands to flash u-boot binaries are listed here.[9]

>> That being said, since it's not always feasible/practical to update
>> u-boot, and when it comes down to it, this is still a kernel
>> regression, we should also fix the kernel to sanity check the values
>> coming from u-boot, like it was doing before.
> 
> Sounds good.
> 
> Apart from this memory issue here, I noticed that CPUs don't appear to
> be in HYP mode for virtualization, which had required a signed SPL
> update for the ODROID-XU [2]. And to me it looks as if there's no
> Arndale Octa support in upstream U-Boot [3], no real maintenance on the
> InSignal fork [4] and a policy of not cooperating with others [5].
> 

Adding Arndale-Octa support to upstream U-Boot was on a TODO list, but
that didn't materialize because of some other reasons.

> Thanks,
> Andreas
> 
> [1] http://forum.insignal.co.kr/viewtopic.php?f=6&t=3199
> [2] http://forum.odroid.com/viewtopic.php?f=64&t=2778&start=40#p32581
> [3]
> http://git.denx.de/?p=u-boot.git;a=blob;f=boards.cfg;h=947f2bc5ba2794c94b3b2cea04664f005e025f9f;hb=HEAD#l286
> [4] http://git.insignal.co.kr/insignal/arndale_octa-jb_mr1.1/u-boot/
> [5] http://forum.insignal.co.kr/viewtopic.php?f=40&t=3613
> 
[6]
http://snapshots.linaro.org/kernel-hwpack/linux-linaro-tracking-ll-arndale-octa/442/hwpack_linaro-arndale-octa_20140626-442_armhf_supported.tar.gz
[7] <path_to_extracted_folder>/u_boot/usr/lib/u-boot/arndale_octa
[8]
git.linaro.org/landing-teams/working/samsung/u-boot.git/shortlog/refs/heads/tracking-arndale_octa
[9] http://pastebin.com/pfGF2giq

Thanks,
-- 
Tushar Behera

WARNING: multiple messages have this Message-ID (diff)
From: trblinux@gmail.com (Tushar Behera)
To: linux-arm-kernel@lists.infradead.org
Subject: mainline boot: 64 boots: 62 pass, 2 fail (v3.16-rc1-2-gebe0618)
Date: Fri, 27 Jun 2014 08:58:31 +0530	[thread overview]
Message-ID: <53ACE4DF.3040603@gmail.com> (raw)
In-Reply-To: <53AC5293.90209@suse.de>

On 06/26/2014 10:34 PM, Andreas F?rber wrote:
> Hi Kevin and Tushar,
> 
> Am 26.06.2014 16:59, schrieb Kevin Hilman:
>>> IMO, the bug is in u-boot and we should fix that.
>>
>> I agree that the u-boot bug needs to be fixed, and FWIW, I updated my
>> u-boot and haven't seen the boot failure yet after several boots with
>> next-20140625.
> 
> Could you clarify your test setup: Are you using the original InSignal
> SPL [1] with just your own u-boot.bin? Or do you have access to some
> newer Samsung-signed SPL?
> 

The u-boot changes for Arndale-Octa was done as part of an activity
within Linaro. Insignal had signed the SPL binary for us. You can
extract the signed SPL binary from following hwpack[6] (tar xfz and then
within u_boot folder[7]).

The source code for this u-boot can be found here.[8]

Just in case, commands to flash u-boot binaries are listed here.[9]

>> That being said, since it's not always feasible/practical to update
>> u-boot, and when it comes down to it, this is still a kernel
>> regression, we should also fix the kernel to sanity check the values
>> coming from u-boot, like it was doing before.
> 
> Sounds good.
> 
> Apart from this memory issue here, I noticed that CPUs don't appear to
> be in HYP mode for virtualization, which had required a signed SPL
> update for the ODROID-XU [2]. And to me it looks as if there's no
> Arndale Octa support in upstream U-Boot [3], no real maintenance on the
> InSignal fork [4] and a policy of not cooperating with others [5].
> 

Adding Arndale-Octa support to upstream U-Boot was on a TODO list, but
that didn't materialize because of some other reasons.

> Thanks,
> Andreas
> 
> [1] http://forum.insignal.co.kr/viewtopic.php?f=6&t=3199
> [2] http://forum.odroid.com/viewtopic.php?f=64&t=2778&start=40#p32581
> [3]
> http://git.denx.de/?p=u-boot.git;a=blob;f=boards.cfg;h=947f2bc5ba2794c94b3b2cea04664f005e025f9f;hb=HEAD#l286
> [4] http://git.insignal.co.kr/insignal/arndale_octa-jb_mr1.1/u-boot/
> [5] http://forum.insignal.co.kr/viewtopic.php?f=40&t=3613
> 
[6]
http://snapshots.linaro.org/kernel-hwpack/linux-linaro-tracking-ll-arndale-octa/442/hwpack_linaro-arndale-octa_20140626-442_armhf_supported.tar.gz
[7] <path_to_extracted_folder>/u_boot/usr/lib/u-boot/arndale_octa
[8]
git.linaro.org/landing-teams/working/samsung/u-boot.git/shortlog/refs/heads/tracking-arndale_octa
[9] http://pastebin.com/pfGF2giq

Thanks,
-- 
Tushar Behera

  reply	other threads:[~2014-06-27  3:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <539fdd37.e7bc420a.76b9.ffffb583@mx.google.com>
     [not found] ` <CAGa+x85nqPbH-sye28ni=gUEdgjGdUDqHhv1+0pV5aO8y1+wHQ@mail.gmail.com>
     [not found]   ` <53A106F1.10201@gmail.com>
     [not found]     ` <CAGa+x8527FEPk6fg5kv-fbOzK3MzcFooFGE9Me12b9C_Pv=UzA@mail.gmail.com>
     [not found]       ` <53A2AE11.2050208@gmail.com>
     [not found]         ` <53A2BE94.2010308@gmail.com>
2014-06-23  3:56           ` mainline boot: 64 boots: 62 pass, 2 fail (v3.16-rc1-2-gebe0618) Tushar Behera
2014-06-23  3:56             ` Tushar Behera
2014-06-23 18:32             ` Kevin Hilman
2014-06-23 18:32               ` Kevin Hilman
2014-06-24 17:47               ` Laura Abbott
2014-06-24 17:47                 ` Laura Abbott
2014-06-24 22:29                 ` Laura Abbott
2014-06-24 22:29                   ` Laura Abbott
2014-06-25 12:13                   ` Tushar Behera
2014-06-25 12:13                     ` Tushar Behera
2014-06-25 21:57                     ` Laura Abbott
2014-06-25 21:57                       ` Laura Abbott
2014-06-26  6:44                       ` Tushar Behera
2014-06-26  6:44                         ` Tushar Behera
2014-06-26 14:59                         ` Kevin Hilman
2014-06-26 14:59                           ` Kevin Hilman
2014-06-26 15:17                           ` Russell King - ARM Linux
2014-06-26 15:17                             ` Russell King - ARM Linux
2014-06-26 19:42                             ` Laura Abbott
2014-06-26 19:42                               ` Laura Abbott
2014-06-27  3:06                               ` Tushar Behera
2014-06-27  3:06                                 ` Tushar Behera
2014-06-27  9:09                                 ` Laura Abbott
2014-06-27  9:09                                   ` Laura Abbott
2014-06-27  9:40                                   ` Russell King - ARM Linux
2014-06-27  9:40                                     ` Russell King - ARM Linux
2014-06-26 17:04                           ` Andreas Färber
2014-06-26 17:04                             ` Andreas Färber
2014-06-27  3:28                             ` Tushar Behera [this message]
2014-06-27  3:28                               ` Tushar Behera
2014-06-25  2:07               ` Andreas Färber
2014-06-25  2:07                 ` Andreas Färber

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=53ACE4DF.3040603@gmail.com \
    --to=trblinux@gmail.com \
    --cc=afaerber@suse.de \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=khilman@linaro.org \
    --cc=lauraa@codeaurora.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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.