From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPL Dfu update
Date: Wed, 30 Oct 2013 16:07:08 -0400 [thread overview]
Message-ID: <20131030200708.GS19303@bill-the-cat> (raw)
In-Reply-To: <20131030195814.670C4380C14@gemini.denx.de>
On Wed, Oct 30, 2013 at 08:58:14PM +0100, Wolfgang Denk wrote:
> 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?
The answer, of debatable value, is that we can't download the whole
thing at once to the target device. One could wrap the logic and load
SPL, then load special task U-Boot, at least in the examples I know well
enough to talk about them (the TI parts).
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20131030/4225a0cd/attachment.pgp>
prev parent reply other threads:[~2013-10-30 20:07 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
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 [this message]
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=20131030200708.GS19303@bill-the-cat \
--to=trini@ti.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.