public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Frank Haverkamp <haver@vnet.ibm.com>
To: dedekind@infradead.org
Cc: Alexander Schmidt <alexs@linux.vnet.ibm.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [MTD] UBI: Per volume update marker
Date: Fri, 26 Jan 2007 09:47:45 +0100	[thread overview]
Message-ID: <1169801265.4389.14.camel@localhost.localdomain> (raw)
In-Reply-To: <1169748994.9477.15.camel@sauron>

Hi Artem,

On Thu, 2007-01-25 at 20:16 +0200, Artem Bityutskiy wrote:

> The patch in general (did not look closely to the details) looks good
> for me. But are you sure you want this patch? It was a requirement from
> your team to implement the update marker. 

The requirement was that we are able to avoid using an UBI volume where
the update was interrupted, and _not_ the update marker. The
update-marker was just one idea how this feature could be implemented.
Alexanders proposal is another idea, which we think helps to reduce
complexity.

> Note, your patch means that
> the boot-loader needs to read and interpret the volume table which
> increases its size.
> 

The simplest form of our boot-loader does not know anything about the
volume table and update maker block at all, but just deals with static
volumes. If all blocks of a static volumes are available and have good
CRC the boot-code will use it.

There is also a boot-code enhancement done by Josh which exploits the
volume table and possibly the update marker. If we decide to use the new
mechansim, I think this code needs a little adjustement too, but I think
we can handle that. If that becomes neccessary we also hope that some
complexity will go away there.

Alexander will update the patch according to the comments you gave in
your last mail and resend the patch.

Frank

  parent reply	other threads:[~2007-01-26  8:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24  9:19 [MTD] UBI: Per volume update marker Alexander Schmidt
2007-01-25 18:16 ` Artem Bityutskiy
2007-01-25 19:19   ` Josh Boyer
2007-01-26  8:47   ` Frank Haverkamp [this message]
2007-01-26 10:43     ` Artem Bityutskiy
2007-01-26  8:04 ` Artem Bityutskiy
2007-01-29 10:47   ` Alexander Schmidt
2007-01-29 13:02     ` Artem Bityutskiy
2007-01-29 16:36       ` Alexander Schmidt
2007-01-30 13:01         ` Artem Bityutskiy
2007-01-30 13:44         ` Artem Bityutskiy
2007-01-30 15:36         ` Artem Bityutskiy
2007-01-30 18:35         ` Artem Bityutskiy
2007-01-30 19:00         ` Artem Bityutskiy

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=1169801265.4389.14.camel@localhost.localdomain \
    --to=haver@vnet.ibm.com \
    --cc=alexs@linux.vnet.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox