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:24:37 -0600 [thread overview]
Message-ID: <1355264677.13481.13@snotra> (raw)
In-Reply-To: <20121211011650.GV9044@bill-the-cat> (from trini@ti.com on Mon Dec 10 19:16:50 2012)
On 12/10/2012 07:16:50 PM, Tom Rini wrote:
> On Mon, Dec 10, 2012 at 07:09:55PM -0600, Scott Wood wrote:
> > 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?
> >
> > >+ /* find out how much actual bytes have been written */
> > >+ /* the difference is the amount of skip we must add from now on
> > >*/
> > >+ actual = nand_extent_skip_bad(&nand_info[dev], start, count);
> >
> > ...especially since you already need to interact with it here?
>
> I've been talking with Pantelis about this as well and in short, this
> series adds NAND support ala MMC (which is to say, (ab)using the
> command
> interface). I think he was thinking we need a bit more generic help
> to
> avoid having to duplicate the code the command interface also uses
> (state, sanity checking), iirc.
Some elaboration on what exactly he's relying on from the command line
interface would be nice.
-Scott
next prev parent reply other threads:[~2012-12-11 22:24 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 [this message]
2012-12-11 22:40 ` Tom Rini
2012-12-11 7:56 ` Lukasz Majewski
2012-12-11 22:23 ` Scott Wood
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=1355264677.13481.13@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 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.