From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Chain-loading u-boot stopped working between 2016.01-rc1 and 2016.01-rc4
Date: Wed, 20 Jan 2016 12:02:58 +0100 [thread overview]
Message-ID: <20160120110258.GA12906@amd> (raw)
In-Reply-To: <569F588B.10105@denx.de>
Hi!
> On 20.01.2016 10:31, Pavel Machek wrote:
> >I'm loading u-boot using tftp from u-boot 2013.01. Marek will claim
> >that this configuration is unsupported, but it enables fairly quick
> >development and was very useful for me in past.
>
> Yes, I use this chainloading also quite frequently on some platforms.
> It should generally work on platforms with SPL support. Where the
> preloader / SPL / BootROM has initialized the base HW and the SDRAM.
> So that the U-Boot proper can get loaded into SDRAM. So it should
> also work on SoCFPGA. I have to admit, that I haven't tested it
> lately on SoCFPGA though.
>
> >Unfortunately, it stopped working between 2016.01-rc1 and -rc4. Before
> >I start bisecting it, I wanted to ask if someone has idea what might
> >be responsible?
>
> As mentioned above, I've not tested on this platform lately, sorry.
> But I assume that you also test the latest release version, yes?
> And current master as well. Also failing there?
I have not got to current master. I retested 2016.01 now, and used
config not based on my previous one, but based on defconfig, and it
seems to work.
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2016-01-20 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 9:31 [U-Boot] Chain-loading u-boot stopped working between 2016.01-rc1 and 2016.01-rc4 Pavel Machek
2016-01-20 9:51 ` Stefan Roese
2016-01-20 11:02 ` Pavel Machek [this message]
2016-01-20 10:19 ` Pavel Machek
2016-01-20 14:06 ` Wolfgang Denk
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=20160120110258.GA12906@amd \
--to=pavel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox