From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
barebox@lists.infradead.org
Subject: Re: [PATCH v3 0/4] mvebu: Add network support for Armada 370/XP
Date: Wed, 12 Nov 2014 12:22:22 +0100 [thread overview]
Message-ID: <546342EE.20500@gmail.com> (raw)
In-Reply-To: <20141112105637.GN27002@pengutronix.de>
On 11/12/2014 11:56 AM, Uwe Kleine-König wrote:
> Hello again,
>
> here come the recent insights.
[...]
>
> It seems to be not possible to easily dump the register space in both
> U-Boot and barebox for comparison. md 0xf1074000+0x4000 just hangs
> somewhere in the middle.
>
> A difference between U-Boot and barebox is the location where the
> internal registers are mapped. Maybe something that depends on U-Boot's
> memory layout leaks into barebox because I do 2nd stage booting?
>
> Out of ideas at the moment. :-(
Uwe,
Nice comparison, but did you double check caches are disabled? There is
no support for Dcache on mvebu SoCs in barebox atm.
Sebastian
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-11-12 11:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 14:56 Ezequiel Garcia
2014-11-09 14:56 ` [PATCH v3 1/4] ARM: mvebu: Enable PUP register Ezequiel Garcia
2014-11-09 14:56 ` [PATCH v3 2/4] net: phy: Support Marvell 88EE1545 PHY Ezequiel Garcia
2014-11-09 14:56 ` [PATCH v3 3/4] net: phy: Support Marvell 88EE1543 PHY Ezequiel Garcia
2014-11-10 6:57 ` Sascha Hauer
2014-11-09 14:56 ` [PATCH v3 4/4] net: Add driver for Armada 370/XP 10/100/1000 Mbps network controller Ezequiel Garcia
2014-11-10 8:06 ` [PATCH v3 0/4] mvebu: Add network support for Armada 370/XP Uwe Kleine-König
2014-11-10 18:10 ` Ezequiel Garcia
2014-11-10 18:43 ` Uwe Kleine-König
2014-11-10 19:36 ` Sebastian Hesselbarth
2014-11-11 9:06 ` Uwe Kleine-König
2014-11-11 14:25 ` Ezequiel Garcia
2014-11-11 14:31 ` Thomas Petazzoni
2014-11-11 14:34 ` Ezequiel Garcia
2014-11-12 7:03 ` Sascha Hauer
2014-11-11 20:35 ` Uwe Kleine-König
2014-11-12 10:56 ` Uwe Kleine-König
2014-11-12 11:22 ` Sebastian Hesselbarth [this message]
2014-11-13 9:09 ` Uwe Kleine-König
2014-11-13 9:53 ` Sebastian Hesselbarth
2014-11-13 10:46 ` Uwe Kleine-König
2014-11-13 11:31 ` Sebastian Hesselbarth
2014-11-13 18:44 ` Uwe Kleine-König
2014-11-14 8:21 ` Sebastian Hesselbarth
2014-11-14 20:48 ` Uwe Kleine-König
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=546342EE.20500@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=u.kleine-koenig@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox