From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPL Dfu update
Date: Wed, 30 Oct 2013 20:58:14 +0100 [thread overview]
Message-ID: <20131030195814.670C4380C14@gemini.denx.de> (raw)
In-Reply-To: <CAOf5uw=1yvf8xde--7bP2y0joPhj9WcEhE8jS8Y05+WYZ_wGBQ@mail.gmail.com>
Dear Michael Trimarchi,
In message <CAOf5uw=1yvf8xde--7bP2y0joPhj9WcEhE8jS8Y05+WYZ_wGBQ@mail.gmail.com> you wrote:
>
> > Apart of the fact that is possible to add DFU to SPL, I am missing which
> > is the real advantage. One goal of having split U-Boot into two images
> > (SPL and U-Boot) is also to get a simpler and smaller image, letting the
> > main U-Boot image doing the rest (hush shell, further drivers, and so
> > on). We are now trying to push features that we currently have into SPL.
> > Well, why cannot we simply run U-Boot if we need a DFU update ? Which
> > are the real advantages for having DFU in SPL ?
>
> USB flashing (no serial, no display) only otg
This does not answer Stefano's question: why do it in SPL, what's
wrong with loading the real U-Boot for this purpose?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
IMPORTANT NOTICE TO PURCHASERS: The Entire Physical Universe, Inclu-
ding This Product, May One Day Collapse Back into an Infinitesimally
Small Space. Should Another Universe Subsequently Re-emerge, the
Existence of This Product in That Universe Cannot Be Guaranteed.
next prev parent reply other threads:[~2013-10-30 19:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 8:28 [U-Boot] SPL Dfu update Michael Trimarchi
2013-10-30 8:38 ` Michael Trimarchi
2013-10-30 12:58 ` Lukasz Majewski
2013-10-30 13:15 ` Michael Trimarchi
2013-10-30 13:28 ` Stefano Babic
2013-10-30 13:29 ` Michael Trimarchi
2013-10-30 13:44 ` Tom Rini
2013-10-30 13:52 ` Michael Trimarchi
2013-10-30 14:19 ` Otavio Salvador
2013-10-30 14:24 ` Stefano Babic
2013-10-30 14:32 ` Eric Nelson
2013-10-30 15:58 ` Michael Trimarchi
2013-10-30 20:01 ` Wolfgang Denk
2013-10-30 20:08 ` Eric Nelson
2013-10-30 14:34 ` Michael Trimarchi
2013-10-30 19:33 ` Tom Rini
2013-10-30 19:43 ` Michael Trimarchi
2013-10-30 19:47 ` Tom Rini
2013-10-30 19:58 ` Michael Trimarchi
2013-10-30 20:04 ` Tom Rini
2013-10-30 20:03 ` Wolfgang Denk
2013-10-30 20:06 ` Michael Trimarchi
2013-10-30 19:36 ` Tom Rini
2013-10-30 19:58 ` Wolfgang Denk [this message]
2013-10-30 20:01 ` Michael Trimarchi
2013-10-30 20:11 ` Wolfgang Denk
2013-10-30 20:35 ` Michael Trimarchi
2013-10-30 20:53 ` Otavio Salvador
2013-10-30 21:37 ` Michael Trimarchi
2013-10-31 13:20 ` Tom Rini
2013-11-08 22:09 ` Michael Trimarchi
2013-10-30 20:07 ` Tom Rini
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=20131030195814.670C4380C14@gemini.denx.de \
--to=wd@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 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.