From: Artem Bityutskiy <dedekind@infradead.org>
To: Pontus Hedman <pontushedman@navcast.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Writing a ubinize'd image to fresh NANDFlash with a burner
Date: Wed, 14 Jan 2009 14:37:29 +0200 [thread overview]
Message-ID: <1231936649.5973.57.camel@localhost.localdomain> (raw)
In-Reply-To: <1231872781.16881.47.camel@phedman.navcastinc.local>
On Tue, 2009-01-13 at 13:53 -0500, Pontus Hedman wrote:
> I think all I have to do is insert 64 bytes of OOB data every 2048 bytes
> in that image to make it compliant. So I guess I would make that OOB
> data be all 0xFFs so that the flash OOB parts are left alone?
Probably. You may easily add one more ubinize command line option which
would make it put OOB data to the output image, just like you
described.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-01-14 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 16:55 Writing a ubinize'd image to fresh NANDFlash with a burner Pontus Hedman
2009-01-08 16:59 ` Artem Bityutskiy
2009-01-13 14:45 ` Artem Bityutskiy
2009-01-13 18:53 ` Pontus Hedman
2009-01-14 12:37 ` Artem Bityutskiy [this message]
2009-01-16 21:25 ` Pontus Hedman
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=1231936649.5973.57.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pontushedman@navcast.com \
/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