public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] Writing a YAFFS image to NAND
Date: Fri, 3 Apr 2009 18:40:59 -0400	[thread overview]
Message-ID: <200904031841.02275.vapier@gentoo.org> (raw)
In-Reply-To: <49D65B4E.6080003@freescale.com>

On Friday 03 April 2009 14:54:06 Scott Wood wrote:
> 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.

i'm in windows atm so i cant post a proper patch, but this link should be 
useful:
http://blackfin.uclinux.org/git/?p=readonly-mirrors/u-
boot.git;a=commitdiff;h=b71bce9d98776f4b5aeecfae151f8961a6ef8e98
-mike

  reply	other threads:[~2009-04-03 22:40 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
2009-04-03 22:40   ` Mike Frysinger [this message]
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=200904031841.02275.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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