From: Frank Haverkamp <haver@vnet.ibm.com>
To: tglx@linutronix.de
Cc: Alexander Schmidt <alexs@linux.vnet.ibm.com>,
linux-mtd@lists.infradead.org
Subject: Re: [RFC] [PATCH 1/1] [MTD] UBI: implement per-volume update
Date: Thu, 01 Feb 2007 14:35:45 +0100 [thread overview]
Message-ID: <1170336945.15083.5.camel@localhost.localdomain> (raw)
In-Reply-To: <1170335439.29240.277.camel@localhost.localdomain>
Hi Thomas,
On Thu, 2007-02-01 at 14:10 +0100, Thomas Gleixner wrote:
> On Thu, 2007-02-01 at 12:21 +0200, Artem Bityutskiy wrote:
> > This patch removes the global update marker support and everything
> > related to it. Now we have per-volume update marker bit in the
> > volume table. This makes us incompatible with older UBI images but
> > this is not a big deal - UBI is not used so widely so far and we
> > can afford dropping legacy stuff now.
>
> Uuurgh. Incompatible in what way ? Does this mean you cannot boot from
> an existing image anymore ?
No if that would be the case, I would have objected to the patch.
What it should do is to remove the need to have the update marker
block. Instead of the update marker block Alexander is using a flag in
the volume info table per volume to indicate that an update is going on.
>
> tglx
The compatibility issue is that if you want to update a system with
a not yet cleaned up "old style update marker" the new kernel does
not know what to do with the now unknown ubi-update-volume. The
compatibility flag we decided for the update-volume is "reject", which
will cause ubi not to accept the mtd.
Frank
next prev parent reply other threads:[~2007-02-01 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 10:21 [RFC] [PATCH 0/1] [MTD] UBI: implement per-volume update Artem Bityutskiy
2007-02-01 10:21 ` [RFC] [PATCH 1/1] " Artem Bityutskiy
2007-02-01 13:10 ` Thomas Gleixner
2007-02-01 13:22 ` Artem Bityutskiy
2007-02-01 13:26 ` Artem Bityutskiy
2007-02-01 13:35 ` Frank Haverkamp [this message]
2007-02-01 13:32 ` [RFC] [PATCH 0/1] " Alexander Schmidt
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=1170336945.15083.5.camel@localhost.localdomain \
--to=haver@vnet.ibm.com \
--cc=alexs@linux.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 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.