From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 9/9] ARM: tegra: Default configuration updates for v4.3-rc1
Date: Wed, 19 Aug 2015 12:33:06 +0200 [thread overview]
Message-ID: <20150819103305.GF26627@ulmo> (raw)
In-Reply-To: <1439977724.4135.90.camel@collabora.co.uk>
On Wed, Aug 19, 2015 at 11:48:44AM +0200, Sjoerd Simons wrote:
> On Wed, 2015-08-19 at 11:14 +0200, Thierry Reding wrote:
> > On Tue, Aug 18, 2015 at 03:30:41PM -0700, Tyler Baker wrote:
> > > Hi Theirry,
> > >
> > >
> > > This isn't where the story ends unfortunately. The collabora lab
> > > also
> > > has a jetson-tk1, booted in the same manner, which boots next
> > > -20150818
> > > fine[4]. The only differences I can spot in the two boot logs is
> > > that
> > > the collabora board is using an older version of u-boot, where as
> > > my
> > > board is using a newer version. U-Boot 2015.01-00231-gab77f24-dirty
> > > (Good) vs U-Boot 2015.07-00130-gb217c89 (Bad).
>
> Our 2015.01-00231-gab77f24-dirty is 2015.01-00231-gab77f24 + changes
> which got merged as 053b86e6d8e50359412e626c33bae3f7bafd74dd in
> upstream u-boot.
>
> Fwiw:
> $ git show 2015.01-00231-gab77f24
> commit ab77f24119e80257de4ab017b877f92f96980562
> Merge: d928664 fa58b10
> Author: Tom Rini <trini@ti.com>
> Date: Thu Jan 15 14:05:31 2015 -0500
>
> Merge branch 'master' of git://git.denx.de/u-boot-ti
>
> Which is definately a commit you should hae in your upstream u-boot
> tree.
Yeah, I suck. I was running:
$ git show gab77f24
I didn't know git could parse the full output from git describe.
> > I don't have either of those commits in any of the U-Boot trees I
> > have.
> > Perhaps whatever tree this comes from has local patches that cause
> > the
> > breakage? The version that I use a recent upstream U-Boot with some
> > local patches, none of which should impact Jetson TK1 in any way.
> > Just
> > to make sure I tried running latest origin/master, which identifies
> > thusly:
> >
> > U-Boot 2015.10-rc2-00040-g0f9258228e2b
> >
> > And that boots next-20150818 fine.
>
> Probably worth for tyler to test that u-boot commit on his jetson to
> see if that solves the issue he's having...
I've tried reconstructing the version that Tyler is running by checking
out 2015.01-00231-gab77f24 and applying 053b86e6d8e5 ("pci: tegra: Fix
port information parsing") on top, but that also leaves me with a
bootable system, so no way of reproducing. I agree that upgrading to a
more recent U-Boot version sounds like the best way forward because it
has already proven to work on at least two setups.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150819/63181835/attachment.sig>
next prev parent reply other threads:[~2015-08-19 10:33 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 14:48 [GIT PULL 0/9] ARM: tegra: Changes for v4.3-rc1 Thierry Reding
2015-08-14 14:48 ` [GIT PULL 1/9] clk: " Thierry Reding
2015-08-25 23:43 ` Stephen Boyd
2015-08-14 14:48 ` [GIT PULL 2/9] pinctrl: " Thierry Reding
2015-08-14 14:48 ` [GIT PULL 3/9] ARM: tegra: Cleanup patches " Thierry Reding
2015-08-21 1:42 ` Olof Johansson
2015-08-14 14:48 ` [GIT PULL 4/9] ARM: tegra: Core SoC changes " Thierry Reding
2015-08-21 1:45 ` Olof Johansson
2015-08-14 14:48 ` [GIT PULL 5/9] ARM: tegra: CPU frequency scaling " Thierry Reding
2015-08-21 1:47 ` Olof Johansson
2015-08-14 14:48 ` [GIT PULL 6/9] iommu/tegra-smmu: Changes " Thierry Reding
2015-08-17 12:40 ` Joerg Roedel
2015-08-14 14:48 ` [GIT PULL 7/9] ARM: tegra: Memory controller updates " Thierry Reding
2015-08-21 1:57 ` Olof Johansson
2015-08-14 14:48 ` [GIT PULL 8/9] ARM: tegra: Devicetree changes " Thierry Reding
2015-08-21 1:58 ` Olof Johansson
2015-08-21 16:09 ` Olof Johansson
2015-08-21 16:27 ` Jon Hunter
2015-08-21 16:33 ` Olof Johansson
2015-08-21 16:52 ` [GIT PULL 8/9] ARM: tegra: Devicetree changes for v4.3-rc1 (updated) Thierry Reding
2015-08-21 17:16 ` Olof Johansson
2015-08-14 14:48 ` [GIT PULL 9/9] ARM: tegra: Default configuration updates for v4.3-rc1 Thierry Reding
2015-08-18 22:30 ` Tyler Baker
2015-08-19 9:14 ` Thierry Reding
2015-08-19 9:48 ` Sjoerd Simons
2015-08-19 10:33 ` Thierry Reding [this message]
2015-08-19 16:48 ` Tyler Baker
2015-09-03 23:08 ` Tyler Baker
2015-09-10 21:29 ` Kevin Hilman
2015-09-11 10:39 ` Jon Hunter
2015-09-11 11:04 ` Jon Hunter
2015-09-11 12:38 ` Thierry Reding
2015-09-11 13:10 ` Jon Hunter
2015-09-11 13:25 ` Thierry Reding
2015-09-11 13:43 ` Jon Hunter
2015-09-11 15:51 ` Jon Hunter
2015-09-11 15:59 ` Thierry Reding
2015-09-11 16:33 ` Thierry Reding
2015-09-11 17:08 ` Kevin Hilman
2015-09-17 10:26 ` Thierry Reding
2015-09-11 13:15 ` Jon Hunter
2015-09-11 13:21 ` Thierry Reding
2015-09-11 13:39 ` Jon Hunter
2015-09-11 13:57 ` Thierry Reding
2015-09-11 14:08 ` Jon Hunter
2015-08-19 20:36 ` Olof Johansson
2015-08-19 11:15 ` Mikko Perttunen
2015-08-19 16:50 ` Tyler Baker
2015-08-21 2:00 ` Olof Johansson
2015-08-21 2:39 ` Tyler Baker
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=20150819103305.GF26627@ulmo \
--to=thierry.reding@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).