public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: haver@vnet.ibm.com
Cc: "Artem B. Bityutskiy" <dedekind@oktetlabs.ru>,
	"Monte K. Copeland" <catboat@texas.net>,
	Andreas Arnez <arnez@de.ibm.com>,
	MTD Mailinglist <linux-mtd@lists.infradead.org>,
	Alexander Schmidt1 <ALEXSCHM@de.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: ubi-utils: Moving mkpfi, pfiflash, ... to old-tools
Date: Mon, 18 Feb 2008 17:28:36 +0200	[thread overview]
Message-ID: <1203348516.3758.14.camel@sauron> (raw)
In-Reply-To: <1203342580.8085.23.camel@august>

On Mon, 2008-02-18 at 14:49 +0100, Frank Haverkamp wrote:
> We need the tool-chain to generate PFI files for the code-update
> process. Those pfi-files are suited to be used in streaming mode
> together with the pfiflash utility. We use the for NOR and NAND flash
> system the same pfi. Therefor the pfi format does not contain flash
> geometry information e.g. vid-hdr-offset, erase-block size.

Yeah. I tried to use the tools but they did not generate correct UBI
images. I tried to fix this and found out that the internals are too
messy to be maintainable, at least by me.

I cleaned-up what I could, made the utilities consistent, small, and
easy to maintain.

Vs. the PFI stuff, I also tried to clean-up this, but gave up after few
days, and just implemented another utility - ubinize.

I know what is PFI and I decided not to do this, because pfi =
configuration ini file + ubi images. I figured that it does not make
much sense to inroduce this additional magic format.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2008-02-18 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 13:49 ubi-utils: Moving mkpfi, pfiflash, ... to old-tools Frank Haverkamp
2008-02-18 15:28 ` Artem Bityutskiy [this message]
2008-02-18 16:01 ` Thomas Gleixner
2008-02-18 16:49   ` Frank Haverkamp
2008-02-18 16:53     ` Josh Boyer
2008-02-19  8:47       ` Frank Haverkamp
2008-02-19 12:29         ` Josh Boyer
2008-02-19 12:56           ` Frank Haverkamp
2008-02-18 21:26     ` Thomas Gleixner
2008-02-20 10:10       ` Artem Bityutskiy
2008-02-19  9:34     ` Artem Bityutskiy
2008-02-19  9:57       ` Frank Haverkamp

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=1203348516.3758.14.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=ALEXSCHM@de.ibm.com \
    --cc=arnez@de.ibm.com \
    --cc=catboat@texas.net \
    --cc=dedekind@oktetlabs.ru \
    --cc=haver@vnet.ibm.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.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