From: "Andreas Färber" <afaerber@suse.de>
To: "S.J.R. van Schaik" <stephan@synkhronix.com>
Cc: Dylan Reid <dgreid@chromium.org>,
linux-tegra@vger.kernel.org,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>
Subject: nv u-boot for spring (was: building nv-uboot for nyan-big.)
Date: Mon, 03 Nov 2014 14:05:12 +0100 [thread overview]
Message-ID: <54577D88.2070002@suse.de> (raw)
In-Reply-To: <54575BFE.2010108@synkhronix.com>
Dear Stephan,
Am 03.11.2014 um 11:42 schrieb S.J.R. van Schaik:
> [...] I have done some research to figure out how to build
> a working nv u-boot binary, and working instructions can be found on the
> linux-exynos wiki [1]. However, when I tried to apply them to the snow
> and spring boards, by selecting a different branch and a different
> u-boot configuration, those attempts were of no success. [...]
[...]
> The u-boot.bin binary seems to build fine. However, the problem is similar
> to the snow and spring boards, where I can't seem to build the DTB-files.
You didn't ask me. ;) My Spring branch with patches is located here:
https://github.com/afaerber/u-boot/commits/spring
For my convenience I changed the sources to default to the right device
tree, and I manually inlined exynos-periph-id.dtsi.
If you need further info on my build steps, I can look them up in my
scripts (on another machine) - I mainly derived them from the official
instructions for Snow on the Chromium Wiki. I'm pretty sure I did not
mess with the EC firmware at all.
But whatever workarounds exist, the Chromium folks should really be
working on upstreaming U-Boot support for all those Chromebooks, that
usually sanitizes the build process as a side-effect, resulting in less
user questions. :) For Snow I believe that to be done.
Regards,
Andreas
> 1. http://linux-exynos.org/wiki/ARM_Chromebook/Building_u-boot#Building_U-Boot_for_Peach_Pi.2FPit
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2014-11-03 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 10:42 building nv-uboot for nyan-big S.J.R. van Schaik
2014-11-03 13:05 ` Andreas Färber [this message]
[not found] ` <54577D88.2070002-l3A5Bk7waGM@public.gmane.org>
2014-11-04 18:39 ` nv u-boot for spring (was: building nv-uboot for nyan-big.) Andrew Bresticker
[not found] ` <CAODwPW_ZbCMEwdtuu9gMD_HLQWynC6ZQjno6xVxFMOBuxRzd+A@mail.gmail.com>
2014-11-04 22:28 ` Julius Werner
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=54577D88.2070002@suse.de \
--to=afaerber@suse.de \
--cc=dgreid@chromium.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stephan@synkhronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).