From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
To: Bosi Daniele <Daniele.Bosi@mta.it>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: R: UBI corruption on a NOR flash
Date: Fri, 11 Jan 2013 12:23:45 +0100 [thread overview]
Message-ID: <50EFF641.9080503@aimvalley.nl> (raw)
In-Reply-To: <BE7AFD5DB9EB17418CAAAEEA76697290190E878AAB@mta-mail.MTA.INT>
On 01/11/13 10:00, Bosi Daniele wrote:
> Norbert,
> thank you very much for your quick support.
> I've downloaded the ubifs-v2.6.32.git linux as you suggested us, but I see a lot a differences regarding UBI with our very old 2.6.24.6 kernel.
>
> Do you think this is the only work we can do? Are there other possible solutions to fix the issue we have? (Like for example applying the patch showed in http://lists.infradead.org/pipermail/linux-mtd/2010-December/033322.html) ?
>
> Thank you again
> Daniele Bosi
>
I would update to the ubi/ubifs backported v2.6.32 because:
- the ubi/mtd CFI buffer write patch involves several patches, with one or two
patches/updates lateron
- other NOR flash (power cut) problems were solved as well and you're not sure
which one hurts you
Actually, we are very lucky Artem still maintains (or maintained?) ubifs-v2.6.32.git
since v2.6.32 is more than 3 years old.
---
Norbert
next prev parent reply other threads:[~2013-01-11 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 13:43 UBI corruption on a NOR flash Bosi Daniele
2013-01-10 10:28 ` Norbert van Bolhuis
2013-01-11 9:00 ` R: " Bosi Daniele
2013-01-11 11:23 ` Norbert van Bolhuis [this message]
2013-01-17 13:09 ` 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=50EFF641.9080503@aimvalley.nl \
--to=nvbolhuis@aimvalley.nl \
--cc=Daniele.Bosi@mta.it \
--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.