From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] relocation on freescale mx35 doesn't work after update to 2015.01
Date: Wed, 11 Feb 2015 15:10:10 +0100 [thread overview]
Message-ID: <20150211151010.59284143@crub> (raw)
In-Reply-To: <CAOMZO5DwyZ=-tXNCUAvHdvKggbed0QJDtW9maw-w3hEi5+L1GA@mail.gmail.com>
Hi Fabio,
On Wed, 11 Feb 2015 11:55:04 -0200
Fabio Estevam <festevam@gmail.com> wrote:
...
> I don't have a mx35pdk handy to look into this, but it would be nice
> to get mx35 back to life in U-boot.
>
> Magnus,
>
> I suspect that mx31 is also broken. Could you please test mx31pdk with
> U-boot 2015.01?
I can confirm that mx31 is broken in 2015.04-rc1. I tried to boot it
on imx31_phycore, the board is bricked (hangs after "DRAM: 128 MiB"
output). Unfortunately I do not have time to debug/repair it now.
Best regards,
Anatolij
next prev parent reply other threads:[~2015-02-11 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 15:24 [U-Boot] relocation on freescale mx35 doesn't work after update to 2015.01 Priebe, Sebastian
2015-02-06 0:15 ` Albert ARIBAUD
2015-02-06 9:38 ` Priebe, Sebastian
2015-02-06 10:25 ` Albert ARIBAUD
2015-02-11 13:55 ` Fabio Estevam
2015-02-11 14:10 ` Anatolij Gustschin [this message]
2015-02-11 14:16 ` Stefano Babic
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=20150211151010.59284143@crub \
--to=agust@denx.de \
--cc=u-boot@lists.denx.de \
/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.