public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Afzal Mohammed <afzal.mohd.ma@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFC] dfu: ram support
Date: Mon, 9 Sep 2013 20:52:03 +0530	[thread overview]
Message-ID: <20130909152203.GA3391@afzal-ThinkPad-R50e> (raw)
In-Reply-To: <20130909085058.53c1921c@amdc308.digital.local>

Hi Lukasz Majewski,

On Mon, Sep 09, 2013 at 08:50:58AM +0200, Lukasz Majewski wrote:

> > 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
> > dump through usb, if it is worth.

> Above idea sounds very interesting. 

Thanks

> One minor thing: 
> It also would be good to have dfu_alt_info environment properly defined
> to have "ram" alt setting for beagle bone. Then we would have at least
> one board which supports this new feature.

Sure

> > +enum dfu_ram_op {
> > +	DFU_OP_READ = 1,
> > +	DFU_OP_WRITE,
> > +};

> Minor:
> Now I've realised that the dfu_nand_op and dfu_mmc_op have the same
> defines. Maybe it is a good time to combine this and store it at
> dfu.h?

Yes it is better

> Despite one minor comment, I like the code and looking forward for a
> patch :-).

Thanks, will wait for a working day for those on other side of the
globe and if no negative, would repost addressing your comments.

Regards
Afzal

      reply	other threads:[~2013-09-09 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-08 12:38 [U-Boot] [PATCH RFC] dfu: ram support Afzal Mohammed
2013-09-09  6:50 ` Lukasz Majewski
2013-09-09 15:22   ` Afzal Mohammed [this message]

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=20130909152203.GA3391@afzal-ThinkPad-R50e \
    --to=afzal.mohd.ma@gmail.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