From: Helmut Raiger <helmut.raiger@hale.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] Chain loading an u-boot from an u-boot
Date: Mon, 31 Mar 2014 13:29:17 +0200 [thread overview]
Message-ID: <5339518D.2090603@hale.at> (raw)
In-Reply-To: <52FC8A5B.7090506@hale.at>
On 02/13/2014 10:03 AM, Helmut Raiger wrote:
>
>
> But you just inspired me! There are probably interrupts running
> for some time when the second u-boot starts and the relocation
> might destroy part of the interrupt entry points ....
>
> Thx for asking the right questions.
> I'll have to check this.
>
> Helmut
I'm finally able to start the second u-boot (other things in-between as
always).
If I do a cleanup_before_linux(), i.e. turn off interrupts and caches before
the actual 'go' and it works just fine.
For testing I patched the go command, but obviously this can't be
contributed as such.
Anyone having a suggestion on how to do this?
1) add option to 'go' command, which is hard as it has variable arguments
2) add another go command
3) use an environment variable to set the option for 'go'
Theoretically I could use a u-boot image to encapsulate the second u-boot
and use 'bootm', but I think I'll stumble over the same kind of questions.
Helmut
--
Scanned by MailScanner.
next prev parent reply other threads:[~2014-03-31 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 11:11 [U-Boot] Chain loading an u-boot from an u-boot Helmut Raiger
2014-02-10 12:14 ` Andreas Bießmann
2014-02-10 12:57 ` Helmut Raiger
2014-02-12 21:59 ` Scott Wood
2014-02-13 9:45 ` Helmut Raiger
2014-02-11 9:38 ` Stefano Babic
2014-02-12 9:56 ` Helmut Raiger
2014-02-12 10:41 ` Stefano Babic
2014-02-12 10:45 ` Andreas Bießmann
2014-02-13 9:03 ` Helmut Raiger
2014-03-31 11:29 ` Helmut Raiger [this message]
2014-04-03 23:13 ` Simon Glass
2014-04-04 9:25 ` Stefano Babic
2014-04-09 14:07 ` Helmut Raiger
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=5339518D.2090603@hale.at \
--to=helmut.raiger@hale.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox