From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] SPL Dfu update
Date: Wed, 30 Oct 2013 14:28:32 +0100 [thread overview]
Message-ID: <52710980.6020302@denx.de> (raw)
In-Reply-To: <20131030135838.034ce78c@amdc308.digital.local>
Hi Lukasz, hi Michael,
On 30/10/2013 13:58, Lukasz Majewski wrote:
> In general the presented structure is correct.
>
> However, I've got other concerns:
>
> The DFU + composite + gadget + UDC driver code is large (around 24KiB
> in binary size [1] for the TRATS).
>
> I'm not sure if this size would be acceptable for SPL. Of course there
> are some spots for code base size reduction (like optimizing and often
> hardcoding code ported from linux kernel).
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 ?
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================
next prev parent reply other threads:[~2013-10-30 13:28 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 [this message]
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
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=52710980.6020302@denx.de \
--to=sbabic@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