public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ian Campbell <ijc+uboot@hellion.org.uk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] sunxi: Support uploading 'boot.scr' to RAM over USB OTG in FEL mode
Date: Fri, 27 Feb 2015 16:39:45 +0000	[thread overview]
Message-ID: <1425055185.14641.249.camel@hellion.org.uk> (raw)
In-Reply-To: <1424746131-11740-1-git-send-email-siarhei.siamashka@gmail.com>

On Tue, 2015-02-24 at 04:48 +0200, Siarhei Siamashka wrote:
> In order to fully support booting the whole system over USB OTG
> without relying on anything else (MMC, SATA, USB sticks, ...), it
> is possible to upload the 'boot.scr' file to DRAM using the 'fel'
> tool. But U-Boot still needs to be able to pick it up there before
> checking any other boot media.
> 
> Signed-off-by: Siarhei Siamashka <siarhei.siamashka@gmail.com>
> ---
> 
> The patch might be not the best way to implement this. But it would
> be great if U-Boot had out of the box support for:
>     http://linux-sunxi.org/index.php?title=FEL/USBBoot&oldid=13134#Boot_the_whole_system_over_USB_.28u-boot_.2B_kernel_.2B_initramfs.29
> 
> One of the bad things about this patch is that the "scriptaddr"
> variable needs to be hardcoded and protected agaist modifications
> (if this address is to be used from the SPL).

Perhaps use a separate dedicated/hardcoded address for the FEL boot
script to avoid adding unusual semantics to $scriptaddr (which might
surprise users not using fel)?

If the FEL address has to be 0x43100000 for compatibility with existing
instructions/tools that might mean moving the current scriptaddr
elsewhere. I think we can live with that.

> Also I'm not sure how this all could fit into the
> "config_distro_bootcmd.h" model, so I even have not tried
> that yet.

Just at a quick glance, based on the PXE entry something like:

#define BOOTENV_DEV_FEL(devtypeu, devtypel, instance) \
	"bootcmd_fel=source ...\0"

i.e. all the magic params are irrelevant in this case. Perhaps
"bootcmd_"#devtypel"=...\0" but I don't think that's needed in this
instance. BOOTENV_DEV_PXE doesn't bother at least.

Then in BOOT_TARGET_DEVICES include "func(FEL, fel, na)"

Ian.

  reply	other threads:[~2015-02-27 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24  2:48 [U-Boot] [RFC] sunxi: Support uploading 'boot.scr' to RAM over USB OTG in FEL mode Siarhei Siamashka
2015-02-27 16:39 ` Ian Campbell [this message]
2015-03-01 21:37   ` Siarhei Siamashka
2015-03-03  8:31     ` Ian Campbell
2015-03-04 14:18       ` Siarhei Siamashka
2015-03-05  7:42         ` Ian Campbell

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=1425055185.14641.249.camel@hellion.org.uk \
    --to=ijc+uboot@hellion.org.uk \
    --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