From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [DFU] Implement NAND dfu support
Date: Tue, 11 Dec 2012 16:23:17 -0600 [thread overview]
Message-ID: <1355264597.13481.12@snotra> (raw)
In-Reply-To: <20121211085625.03a6aece@amdc308.digital.local> (from l.majewski@samsung.com on Tue Dec 11 01:56:25 2012)
On 12/11/2012 01:56:25 AM, Lukasz Majewski wrote:
> Hi Scott,
>
> > On 12/10/2012 09:24:32 AM, Pantelis Antoniou wrote:
> > > + sprintf(cmd_buf, "nand %s %p %llx %llx",
> > > + op == DFU_OP_READ ? "read" : "write",
> > > + buf, start, count);
> > > +
> > > + debug("%s: %s 0x%p\n", __func__, cmd_buf, cmd_buf);
> > > + ret = run_command(cmd_buf, 0);
> >
> > Why not use the C interface to NAND?
>
> We also support there eMMC (both with raw and file systems). Moreover
> we had this discussion some time ago (if we shall use "command" or
> native C API).
I don't see how "nand %s %p %llx %llx" supports anything that the NAND
C API doesn't support.
I can't follow every discussion that happens on this list, on the off
chance it might eventually become relevant to NAND. "Some time ago" is
not an easily followed reference to the archives.
-Scott
next prev parent reply other threads:[~2012-12-11 22:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 15:24 [U-Boot] [PATCH] [DFU] Implement NAND dfu support Pantelis Antoniou
2012-12-11 1:09 ` Scott Wood
2012-12-11 1:16 ` Tom Rini
2012-12-11 22:24 ` Scott Wood
2012-12-11 22:40 ` Tom Rini
2012-12-11 7:56 ` Lukasz Majewski
2012-12-11 22:23 ` Scott Wood [this message]
2012-12-12 8:35 ` Lukasz Majewski
2012-12-11 9:38 ` Pantelis Antoniou
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=1355264597.13481.12@snotra \
--to=scottwood@freescale.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