From: Chin Liang See <clsee@altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Separate EBV Socrates board from Altera Cyclone 5 board
Date: Wed, 13 Nov 2013 11:57:39 -0600 [thread overview]
Message-ID: <1384365459.6899.13.camel@clsee-VirtualBox.altera.com> (raw)
In-Reply-To: <5283A107.6040704@monstr.eu>
Hi,
> >>>>
> >>>
> >>> Currently, the SOCFPGA SPL is customized through a set of handoff files
> >>> which located at board folders. These handoff files are generated by
> >>> tools based on board and user design in FPGA. With that, not much
> >>> decision being made during run time based on the board. With this
> >>> handoff and tools approach, it will shield off the complexity of
> >>> hardware configuration and errors (if user change it manually without
> >>> tools help). Thanks
> >>
> >> Which nice copy of our approach. :-)
> >
> > Hmmm... is it true? This approach being used since few years back at
> > NIOS soft processor. Besides that, we are utilizing the SPL framework
> > for our second stage boot loader. I believe you guys are not using SPL
> > right? It seems you guys would need tools to generate and even build you
> > guys own version of boot loader. It creates high dependency for user to
> > your tools.
>
> Interesting discussion. :-)
> I believe we will use SPL at some point in future for Microblaze
> just because of easier maintenance . But will see.
Yup, utilizing SPL will gain you the power of open source :)
>
> I don't understand your point regarding to tool dependency. For DTSes
> I believe you are also generating this structure from design tools
> or you can write it by hand.
> We are also generating U-boot configuration but if someone wants to write
> it by hand they can.
I believe we have misalignment on the term used. For us, second stage
bootloader is referring to the bootloader loaded by BootROM. I believe
you guys are referring that as FSBL.
> > For our solution, customer can just grab the code from git and build it
> > using the normal U-Boot way (if they don't want to use the tools). With
> > the SPL also, we are taking advantage of open source community power to
> > make our second stage boot loader more powerful and user friendly to
> > user. Our user can grab any drivers or leverage the supports from the
> > open community too. I believe that is the power of open source :)
>
> We have the same for Microblaze and Zynq.
Same as above, I believe both of us are using U-Boot. But for bootloader
before U-Boot, we are using SPL while you guys using FSBL which is not
SPL framework, right? With that, I believe you guys would need a
proprietary tools to compile and build the FSBL. We would not have this
dependency when building the SPL code.
Thanks
Chin Liang
>
> Cheers,
> Michal
>
next prev parent reply other threads:[~2013-11-13 17:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 19:26 [U-Boot] [PATCH] Separate EBV Socrates board from Altera Cyclone 5 board Pavel Machek
2013-11-11 20:32 ` Chin Liang See
2013-11-11 20:33 ` Tom Rini
2013-11-12 8:22 ` Michal Simek
2013-11-12 9:56 ` Detlev Zundel
2013-11-12 10:17 ` Michal Simek
2013-11-12 14:46 ` Chin Liang See
2013-11-12 15:17 ` Michal Simek
2013-11-13 0:07 ` Dinh Nguyen
2013-11-13 14:39 ` Chin Liang See
2013-11-13 15:55 ` Michal Simek
2013-11-13 17:57 ` Chin Liang See [this message]
2013-11-14 7:23 ` Michal Simek
2013-11-12 15:25 ` Tom Rini
2013-11-12 9:53 ` Detlev Zundel
2014-01-13 8:29 ` Albert ARIBAUD
2014-05-27 13:12 ` [U-Boot] [PATCH v2] Separate EBV Socrates board from Altera Cyclone 5 board and from Virtual Target Pavel Machek
2014-05-27 13:42 ` Detlev Zundel
2014-05-27 13:59 ` Pavel Machek
2014-05-28 8:53 ` Detlev Zundel
2014-05-28 9:56 ` Pavel Machek
2014-05-28 10:36 ` Detlev Zundel
2014-05-28 12:49 ` Pavel Machek
2014-05-28 14:29 ` Wolfgang Denk
2014-05-28 18:26 ` Pavel Machek
2014-05-30 9:41 ` Detlev Zundel
2014-06-02 6:53 ` Chin Liang See
2014-06-05 10:45 ` Detlev Zundel
2014-06-02 7:22 ` Chin Liang See
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=1384365459.6899.13.camel@clsee-VirtualBox.altera.com \
--to=clsee@altera.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox