From: Thomas Gleixner <tglx@linutronix.de>
To: manningc2@actrix.gen.nz, Earl Manning <emanning@austin.rr.com>,
linux-mtd@lists.infradead.org
Subject: Re: Generating a NAND Image
Date: Fri, 16 May 2003 01:08:42 +0200 [thread overview]
Message-ID: <200305160108.42152.tglx@linutronix.de> (raw)
In-Reply-To: <20030515215930.7E21D4099@blood.actrix.co.nz>
On Friday 16 May 2003 00:01, Charles Manning wrote:
> The one problem with doing it this way is that you end up with the bad
> blocks in your image file too. THis will be a problem when you go to
> manufacturing because the manufacturing writer needs to skip over bad
> blocks it detects as it writes. Your image will then not fit any more and
> you'd be marking good blocks bad.
True. Did not htink about that.
> Rather, IMHO, - if you're using YAFFS- suck the structure off the NAND
> onto a host (eg. NFS copy the directory structure to the host) and use
> mkyaffsimage. Send them the myyaffsimage output file. I guess there's a
> JFFSx process to do the same thing.
There's no OOB generator yet, but that's a good idea for volunteers :)
> Alternatively (useful to both YAFFS and JFFS2) hack nanddump.c to not
> write bad blocks to the dump file. This will definitely work for YAFFS, but
> I'm not 100% sure it will work for JFFS2.
Sure, why not. JFFS2 does not rely on bad blocks. :)
> ... and submit a patch :-).
:)
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2003-05-15 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 15:10 Generating a NAND Image Earl Manning
2003-05-15 16:48 ` Thomas Gleixner
2003-05-15 22:01 ` Charles Manning
2003-05-15 23:08 ` Thomas Gleixner [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=200305160108.42152.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=emanning@austin.rr.com \
--cc=linux-mtd@lists.infradead.org \
--cc=manningc2@actrix.gen.nz \
/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