U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v2 1/5] spl: dfu: add dfu support in SPL
Date: Wed, 27 Jul 2016 11:25:20 -0400	[thread overview]
Message-ID: <20160727152520.GB22973@bill-the-cat> (raw)
In-Reply-To: <6C6B28D4DC342643927BEAFCE8707BF6762AB8A1@DBDE04.ent.ti.com>

On Wed, Jul 27, 2016 at 02:04:24PM +0000, B, Ravi wrote:
> Hi Tom
> 
> Missed this thread to reply.
> 
> >> index ef12f9f..ed3e295 100644
> >> --- a/Kconfig
> >> +++ b/Kconfig
> >> @@ -336,6 +336,33 @@ config SPL_FIT_IMAGE_POST_PROCESS
> >>  	  injected into the FIT creation (i.e. the blobs would have been pre-
> >>  	  processed before being added to the FIT image).
> >>  
> >> +config SPL_DFU_SUPPORT
> >> +	bool "Enable SPL with DFU to load binaries to memory device"
> >> +	depends on USB && TARGET_DRA7XX_EVM
> 
> >This seems needlessly restrictive.
> 
> Yes, I do agree, at present only dra7x platform  support BOOT_DEVICE_DFU.
> if we make it generic, then other platform should also enable the SPL-DFU
> support for their respective platform (similar to [RFC PATCH v2 5/5] dra7x: configs: enable SPL-DFU support).

That's what I'm saying, this all looks generic today, except for the
restriction here in Kconfig.  Yes, boards that want to use it will have
to fill in plumbing, but that's normal.

> >> diff --git a/common/command.c b/common/command.c index 
> >> e5d9b9c..d1c049c 100644
> >> --- a/common/command.c
> >> +++ b/common/command.c
> >> @@ -520,7 +520,7 @@ enum command_ret_t cmd_process(int flag, int argc, char * const argv[],
> >>  	if (argc > cmdtp->maxargs)
> >>  		rc = CMD_RET_USAGE;
> >>  
> >> -#if defined(CONFIG_CMD_BOOTD)
> >> +#if defined(CONFIG_CMD_BOOTD) && !defined(CONFIG_SPL_BUILD)
> >>  	/* avoid "bootd" recursion */ Check whether they use DMA or PIO mode.
> 
> >>  	else if (cmdtp->cmd == do_bootd) {
> >>  		if (flag & CMD_FLAG_BOOTD) {
> 
> >Why do we need this?
> 
> Actually CONFIG_CMD_BOOTD is not required for SPL-DFU. 
> But cmd/Kconfg has defined CONFIG_CMD_BOOTD by default, which is causing compilation error for "do_bootd" not defined.
> Again do_bootd depends on CONFIG_CMD_BOOTM which is not defined for SPL.
> 
> What is best way? What do you suggest ?

First, what is the exact compile error you get?  And second, probably
disable CMD_BOOTD.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160727/a61e7466/attachment.sig>

  reply	other threads:[~2016-07-27 15:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 14:53 [U-Boot] [RFC PATCH v2 0/5] SPL: DFU Support in SPL Ravi Babu
2016-07-21 14:53 ` [U-Boot] [RFC PATCH v2 1/5] spl: dfu: add dfu support " Ravi Babu
2016-07-22 13:41   ` Tom Rini
2016-07-27 14:04     ` B, Ravi
2016-07-27 15:25       ` Tom Rini [this message]
2016-07-28  4:09         ` B, Ravi
2016-07-28 13:22           ` Tom Rini
2016-07-21 14:53 ` [U-Boot] [RFC PATCH v2 2/5] common: dfu: saperate the dfu common functionality Ravi Babu
2016-07-22 13:41   ` Tom Rini
2016-07-21 14:53 ` [U-Boot] [RFC PATCH v2 3/5] spl: dfu: adding dfu support functions for SPL-DFU Ravi Babu
2016-07-22 13:41   ` Tom Rini
2016-07-21 14:53 ` [U-Boot] [RFC PATCH v2 4/5] dra7x: boot: add dfu bootmode support Ravi Babu
2016-07-22 13:41   ` Tom Rini
2016-07-25 14:17     ` B, Ravi
2016-07-25 14:38       ` Tom Rini
2016-07-25 14:53         ` B, Ravi
2016-07-21 14:53 ` [U-Boot] [RFC PATCH v2 5/5] dra7x: configs: enable SPL-DFU support Ravi Babu
2016-07-22 13:42   ` Tom Rini
2016-07-22 13:42 ` [U-Boot] [RFC PATCH v2 0/5] SPL: DFU Support in SPL Tom Rini
2016-07-25 14:40   ` B, Ravi
2016-07-25 14:58     ` Tom Rini
2016-07-25 15:25       ` B, Ravi
2016-07-25 15:34         ` Tom Rini
2016-07-25 15:41           ` B, Ravi

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=20160727152520.GB22973@bill-the-cat \
    --to=trini@konsulko.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