From: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: socfpga: make socfpga_socrates_defconfig boot from QSPI
Date: Fri, 10 Aug 2018 14:56:42 +0200 [thread overview]
Message-ID: <7b1e9dac-62e5-5223-e578-90b3ba5140bd@gmail.com> (raw)
In-Reply-To: <8c12ed86-8156-f730-4491-e164c9632ebc@gmail.com>
On 09.08.2018 23:57, Marek Vasut wrote:
> On 08/09/2018 09:17 PM, Simon Goldschmidt wrote:
>> [..]
>> BTW, the DIP switches even allow the SoCrates to boot from fpga, which
>> is what I'm currently working on. In this case, it seems like we need
>> a separate config at least, but the dts can still be the same.
> Presumably because the SPL needs different link address ?
The linker address of course needs to be changed. Preventing the cpu
accessing the FPGA OnChip RAM was a bit more tricky to debug, but it
seems I have it working now.
I guess we need a Kconfig option to enable the bridge reset changes and
select the correct link address. I'll prepare a patch for that. Should I
base it on top of my gen5 fixes series?
Additionally, to add the binary into an fpga, we need a hex file, maybe
these can be automatically generated by mach-socfpga's Makefile when
creating the SPL...
Simon
next prev parent reply other threads:[~2018-08-10 12:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 13:05 [U-Boot] [PATCH] arm: socfpga: make socfpga_socrates_defconfig boot from QSPI Simon Goldschmidt
2018-08-06 13:10 ` Marek Vasut
2018-08-06 13:45 ` Simon Goldschmidt
2018-08-09 19:17 ` Simon Goldschmidt
2018-08-09 21:57 ` Marek Vasut
2018-08-10 12:56 ` Simon Goldschmidt [this message]
2018-08-10 13:15 ` Marek Vasut
2018-08-10 20:11 ` Simon Goldschmidt
2018-08-10 20:21 ` Marek Vasut
2018-08-11 19:26 ` Simon Goldschmidt
2018-08-11 22:05 ` Marek Vasut
2018-08-12 20:04 ` Simon Goldschmidt
2018-08-13 10:21 ` Marek Vasut
2018-09-17 20:39 ` Simon Goldschmidt
2018-10-07 6:43 ` Simon Goldschmidt
2018-10-07 13:24 ` Marek Vasut
2018-10-08 18:45 ` Simon Goldschmidt
2018-10-08 20:27 ` Marek Vasut
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=7b1e9dac-62e5-5223-e578-90b3ba5140bd@gmail.com \
--to=simon.k.r.goldschmidt@gmail.com \
--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.