From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] dm: rpi: Move script load address to 0x8000
Date: Mon, 24 Nov 2014 21:22:51 -0700 [thread overview]
Message-ID: <5474041B.7040809@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ3jBCvLdVS0oz+7kCdy6MfT0PiA5xooSGv2wNqYqTxtpA@mail.gmail.com>
On 11/24/2014 09:10 PM, Simon Glass wrote:
> Hi Stephen,
>
> On 24 November 2014 at 21:06, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 11/24/2014 06:08 PM, Simon Glass wrote:
>>> The current load address of 0 seems to cause problems when driver model
>>> is used. There doesn't seem to be any reason why the script needs to load
>>> to 0, so move it.
>>
>> I'm not particularly tied to the specific $scriptaddr value, but I think
>> we should find out why writing to address 0 causes failures, rather than
>> just papering over the issue.
>
> I had the same thought, but I have no documentation and have spent
> quite a bit of time on it. Do you have any suggestions? Where are the
> CPU vectors kept on this platform?
I think I found the issue; see my latest message in thread "Re:
Raspberry Pi with driver model".
(I should mention I originally started looking at that code since I
dumped the memory at address 0 immediately after boot, and noticed the
UART address was there for some unexpected reason)
next prev parent reply other threads:[~2014-11-25 4:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 1:08 [U-Boot] [PATCH v2 0/2] dm: rpi: Move Raspberry Pi to use driver model Simon Glass
2014-11-25 1:08 ` [U-Boot] [PATCH v2 1/2] dm: rpi: Move serial to " Simon Glass
2014-11-25 4:07 ` Stephen Warren
2014-11-25 1:08 ` [U-Boot] [PATCH v2 2/2] dm: rpi: Move script load address to 0x8000 Simon Glass
2014-11-25 4:06 ` Stephen Warren
2014-11-25 4:10 ` Simon Glass
2014-11-25 4:22 ` Stephen Warren [this message]
2014-11-25 4:28 ` Simon Glass
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=5474041B.7040809@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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.