summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorPeter Horton <zero@colonel-panic.org>2010-06-12 10:11:56 +0900
committerWolfgang Denk <wd@denx.de>2010-06-23 00:00:05 +0200
commitceeba0030844b2e84ce4e47f4be7ad347cd1e827 (patch)
tree8903a60773f7df2da0afcc95967bd2c3892db4e3 /drivers
parentb8c4eea56b5f41f9bdbb89d3d5c79b7d282d513c (diff)
downloadu-boot-imx-ceeba0030844b2e84ce4e47f4be7ad347cd1e827.zip
u-boot-imx-ceeba0030844b2e84ce4e47f4be7ad347cd1e827.tar.gz
u-boot-imx-ceeba0030844b2e84ce4e47f4be7ad347cd1e827.tar.bz2
UBI: initialise update marker
UBI: initialise update marker The in kernel copy of a volume's update marker is not initialised from the volume table. This means that volumes where an update was unfinnished will not be treated as "forbidden to use". This is basically that the update functionality was broken. Signed-off-by: Peter Horton <zero@colonel-panic.org> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com> Acked-by: Stefan Roese <sr@denx.de>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/mtd/ubi/vtbl.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/mtd/ubi/vtbl.c b/drivers/mtd/ubi/vtbl.c
index 9264ac6..f679f06 100644
--- a/drivers/mtd/ubi/vtbl.c
+++ b/drivers/mtd/ubi/vtbl.c
@@ -520,6 +520,7 @@ static int init_volumes(struct ubi_device *ubi, const struct ubi_scan_info *si,
vol->reserved_pebs = be32_to_cpu(vtbl[i].reserved_pebs);
vol->alignment = be32_to_cpu(vtbl[i].alignment);
vol->data_pad = be32_to_cpu(vtbl[i].data_pad);
+ vol->upd_marker = vtbl[i].upd_marker;
vol->vol_type = vtbl[i].vol_type == UBI_VID_DYNAMIC ?
UBI_DYNAMIC_VOLUME : UBI_STATIC_VOLUME;
vol->name_len = be16_to_cpu(vtbl[i].name_len);