public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 3/7] dfu: Remove dependency on HUSH parser in SPL
Date: Wed, 23 Jan 2019 07:54:12 +0100	[thread overview]
Message-ID: <20190123075412.09b13c2f@jawa> (raw)
In-Reply-To: <20190122234150.GV28173@bill-the-cat>

Hi Tom,

> On Tue, Jan 22, 2019 at 11:43:33PM +0100, Lukasz Majewski wrote:
> > On Thu, 17 Jan 2019 13:43:04 -0600
> > "Andrew F. Davis" <afd@ti.com> wrote:
> >   
> > > CLI support with the HUSH parser is not currently SPL safe due to
> > > it's use of realloc. That function is not defined for SPLs that
> > > use SYS_MALLOC_SIMPLE. CLI support can be built in to SPL and some
> > > functions do work, but use of some like run_command() will cause
> > > build to fail. When no SPL code calls this function build works as
> > > the compiler removes this unreachable code so the unresolved
> > > symbols are ignored.
> > > 
> > > If DFU support is enabled in SPL then MMU DFU support may get
> > > brought in also, this code does make a call to run_command()
> > > causing build to fail if the HUSH parser is not built-in. To
> > > break this odd and unneeded dependency chain we use
> > > CONFIG_IS_ENABLED where appropriate to prevent calls into HUSH
> > > code from SPL. This also removes our need to pull in the rather
> > > unrelated source file when SPL_DFU is defined. 
> > 
> > If I remember correctly the HUSH was _required_ by TI to be able to
> > use DFU in SPL (and that was a rationale to add it to SPL - which
> > IMHO was wrong from the outset).
> > 
> > What has changed that it is not needed anymore?  
> 
> To be fair, it was probably me-at-TI rather than TI that said it was
> required.  At the time it was enough of a PITA to try and handle all
> of the cases that the dfu cli command handled via API calls instead
> that at least in my opinion, it wasn't worth re-whacking everything
> else. Times have changed it seems :)
> 

I don't mind :-).

Less code in SPL - the better.


Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190123/7d5a0ef7/attachment.sig>

  reply	other threads:[~2019-01-23  6:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 19:43 [U-Boot] [PATCH v3 0/7] Add USB boot to HS DRA7xx/AM57xx Andrew F. Davis
2019-01-17 19:43 ` [U-Boot] [PATCH v3 1/7] spl: Kconfig: Drop the _SUPPORT postfix from SPL_DFU Andrew F. Davis
2019-01-22 22:40   ` Lukasz Majewski
2019-01-27  3:52   ` [U-Boot] [U-Boot, v3, " Tom Rini
2019-01-17 19:43 ` [U-Boot] [PATCH v3 2/7] dfu: Make DFU support more SPL friendly Andrew F. Davis
2019-01-22 22:41   ` Lukasz Majewski
2019-01-27  3:52   ` [U-Boot] [U-Boot, v3, " Tom Rini
2019-01-17 19:43 ` [U-Boot] [PATCH v3 3/7] dfu: Remove dependency on HUSH parser in SPL Andrew F. Davis
2019-01-22 22:43   ` Lukasz Majewski
2019-01-22 23:41     ` Tom Rini
2019-01-23  6:54       ` Lukasz Majewski [this message]
2019-01-23 14:13         ` Andrew F. Davis
2019-01-27  3:52   ` [U-Boot] [U-Boot, v3, " Tom Rini
2019-01-17 19:43 ` [U-Boot] [PATCH v3 4/7] ARM: mach-omap2: Kconfig: Allow OMAP5 devices to set entry point Andrew F. Davis
2019-01-27  3:52   ` [U-Boot] [U-Boot, v3, " Tom Rini
2019-01-17 19:43 ` [U-Boot] [PATCH v3 5/7] defconfigs: Add config for DRA7xx High Security EVM with USB Boot support Andrew F. Davis
2019-01-27  3:51   ` [U-Boot] [U-Boot, v3, " Tom Rini
2019-01-28 17:43     ` Andrew F. Davis
2019-01-17 19:43 ` [U-Boot] [PATCH v3 6/7] defconfigs: Add config for AM57xx High Security EVM with USB/UART " Andrew F. Davis
2019-01-17 19:43 ` [U-Boot] [PATCH v3 7/7] doc: ti-secure: Add ULO info for AM57xx/DRA7xx secure devices from TI Andrew F. Davis

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=20190123075412.09b13c2f@jawa \
    --to=lukma@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