All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/3] dfu: ram support
Date: Fri, 13 Sep 2013 15:44:54 +0200	[thread overview]
Message-ID: <201309131544.55160.marex@denx.de> (raw)
In-Reply-To: <cover.1379055111.git.afzal.mohd.ma@gmail.com>

Dear Afzal Mohammed,

> Hi,
> 
> DFU spec mentions it as a method to upgrade firmware (software stored
> in writable non-volatile memory). It also says other potential uses of
> DFU is beyond scope of the spec.
> 
> Here such a beyond the scope use is being attempted - directly pumping
> binary images from host via USB to RAM. This facility is a developer
> centric one in that it gives advantage over upgrading non-volatile
> memory for testing new images every time during development and/or
> testing.
> 
> Directly putting image onto RAM would speed up upgrade process. This and
> convenience was the initial thoughts that led to doing this, speed
> improvement over MMC was only 1 second though - 6 sec on RAM as opposed
> to 7 sec on MMC in beagle bone, perhaps enabling cache and/or optimizing
> DFU framework to avoid multiple copy for ram (if worth) may help, and
> on other platforms and other boot media like NAND maybe improvement
> would be higher.
> 
> And for a platform that doesn't yet have proper DFU suppport for
> non-volatile media's, DFU to RAM can be used.
> 
> Another minor advantage would be to increase life of mmc/nand as it
> would be less used during development/testing.
> 
> usage: <image name> ram <start address> <size>
> eg. kernel ram 0x81000000 0x1000000
> 
> Downloading images to RAM using DFU is not something new, this is
> acheived in openmoko also.
> 
> DFU on RAM can be used for extracting RAM contents to host using dfu
> upload. Perhaps this can be extended to io for squeezing out register
> 
> In addition to ram support, a minor unification of dfu read/write enum's
> currently duplicated in mmc/nand is done, helping ram support too.
> 
> Also dfu ram support is added for am335x SoC based boards.
> 
> Based on: usb master branch
> 

CCing Heiko, can you please ACK/NAK ?

Best regards,
Marek Vasut

  parent reply	other threads:[~2013-09-13 13:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13  7:14 [U-Boot] [PATCH v3 0/3] dfu: ram support Afzal Mohammed
2013-09-13  7:16 ` [U-Boot] [PATCH v3 1/3] dfu: unify mmc/nand read/write ops enum Afzal Mohammed
2013-09-13 13:49   ` Marek Vasut
2013-09-13  7:16 ` [U-Boot] [PATCH v3 2/3] dfu: ram support Afzal Mohammed
2013-09-13 10:13   ` Lukasz Majewski
2013-09-13 13:51   ` Marek Vasut
2013-09-13 15:37     ` Gerhard Sittig
2013-09-13 16:05       ` Lukasz Majewski
2013-09-13 16:13       ` Marek Vasut
2013-09-13 17:05       ` Afzal Mohammed
2013-09-13 17:11         ` Afzal Mohammed
2013-09-13  7:17 ` [U-Boot] [PATCH v3 3/3] am335x_evm: enable DFU RAM Afzal Mohammed
2013-09-13 13:44 ` Marek Vasut [this message]
2013-09-14  6:17   ` [U-Boot] [PATCH v3 0/3] dfu: ram support Afzal Mohammed

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=201309131544.55160.marex@denx.de \
    --to=marex@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 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.