From: Frank Haverkamp <haver@vnet.ibm.com>
To: dedekind@infradead.org
Cc: "Monte K. Copeland" <catboat@texas.net>,
MTD Mailinglist <linux-mtd@lists.infradead.org>,
Alexander Schmidt <alexs@linux.vnet.ibm.com>,
haver@vnet.ibm.com, Andreas Arnez <arnez@linux.vnet.ibm.com>
Subject: Re: ubi-utils cleanup
Date: Mon, 07 Jan 2008 14:12:19 +0100 [thread overview]
Message-ID: <1199711539.7595.5.camel@august> (raw)
In-Reply-To: <1199439724.6546.22.camel@august>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
Hi,
On Fri, 2008-01-04 at 10:42 +0100, Frank Haverkamp wrote:
> nand2bin and bin2nand are of the same kind and not UBI dependend. To be
> more widely used, those tools need more flexibility where the ECC data
> is placed in the OOB. Currently it is pretty much hard-coded for the
> layout we are using.
I added more flexibility to the nand2bin/bin2nand tools so that
different ECC layouts in the OOB can more easily be added. I did not
move them yet. Josh, this feature is probably what some of your
colleagues might be looking for.
I moved the scripts from the perl- the scripts-sub-directory since two
sub-dirs do not make a lot of sense like you already mentioned. I
changed the Makefile a little so that one can start the tests more
easily. I removed the obsolete documentation file.
You can find my proposed changes in my mtd-utils.git:
http://git.infradead.org/?p=users/haver/mtd-utils.git;a=summary
Regards,
Frank
--
IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032
Boeblingen, Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Herbert Kircher, Sitz der Gesellschaft: Böblingen,
Registergericht: Amtsgericht Stuttgart, HRB 243294
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5269 bytes --]
prev parent reply other threads:[~2008-01-07 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 9:46 ubi-utils cleanup Artem Bityutskiy
2008-01-04 9:42 ` Frank Haverkamp
2008-01-07 13:12 ` Frank Haverkamp [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=1199711539.7595.5.camel@august \
--to=haver@vnet.ibm.com \
--cc=alexs@linux.vnet.ibm.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=catboat@texas.net \
--cc=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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.