From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Writing a YAFFS image to NAND
Date: Fri, 03 Apr 2009 13:54:06 -0500 [thread overview]
Message-ID: <49D65B4E.6080003@freescale.com> (raw)
In-Reply-To: <1238784243.8002.260.camel@blackhole>
Peter Barada wrote:
> Is there support in the 2009.03 version of U-boot to allow writing a
> YAFFS image created by mkyaffs2image to NAND, including the meta-data in
> the OOB?
Not that I know of (unless something in cmd_yaffs2.c can do it).
> Looking over the nand write/read commands, they look to ignore the OOB
> data interleaved in the image (i.e. 2048+16 bytes per page for
> large-block NAND). I did see a patch from fmandarino on the list, but
> that doesn't look to be in the 2009.03 codebase.
That was several years ago; if someone wants to submit a proper patch
against current u-boot (without the pre-2.6.18 support, or at least with
the newer format being the default), I'll apply it. Better yet would be
a more general mechanism whereby the user specifies how many OOB bytes
are interleaved in the supplied image, without any specific knowledege
of yaffs.
-Scott
next prev parent reply other threads:[~2009-04-03 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 18:44 [U-Boot] Writing a YAFFS image to NAND Peter Barada
2009-04-03 18:54 ` Scott Wood [this message]
2009-04-03 22:40 ` Mike Frysinger
2009-05-19 23:29 ` Mike Frysinger
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=49D65B4E.6080003@freescale.com \
--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.