From: Artem Bityutskiy <dedekind1@gmail.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: 'Matej Kupljen' <matej.kupljen@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Atlant Schmidt <aschmidt@dekaresearch.com>
Subject: Re: Unstable bits and JFFS2
Date: Fri, 13 Apr 2012 22:49:02 +0300 [thread overview]
Message-ID: <1334346542.2200.18.camel@brekeke> (raw)
In-Reply-To: <20120413183617.GA22004@pengutronix.de>
On Fri, 2012-04-13 at 20:36 +0200, Wolfram Sang wrote:
> Hi,
>
> > > > Artem, you said that this unstable bits only happen
> > > > during power cuts, is this right? Would those appear
> > > > also on simulated power cuts, the ones that integck
> > > > can produce?
>
> A bit of hijacking this thread, yet it fits somehow to the idea I got
> yesterday:
>
> There is the Open Project Proposal again, where the CEWG funds topics which
> improve embedded linux in general [1]. I wonder if it makes sense to hand in a
> proposal starting to tackle the 'unstable bits' issue. I could imagine task 1
> mentioned in the wiki page (1. Improve the existing power cut emulation
> infrastructure in UBIFS and start emulating unstable bits. Start with emulating
> only one type of unstable bits, e.g., type 1.) could be a good candidate for
> such a proposal. Since I am not deeply involved with this topic:
>
> 1) Is this task still needed?
> 2) Is it a good task for a 2-3 week period (I'd think so)
> 3) Are there people around up for the task?
>
> I'd be willing to write the proposal, if nobody else volunteers. (yet, given my
> constraints, I am not the right person to actually work on it). Even if the
> proposal doesn't get contracted, the topic itself might get some attention
> since it will be discussed in the CEWG.
Yes, definitely a hot topic now, I am swamped with lots of things and
never found time for writing proposals like this. Please, go ahead,
would be very appreciated. I might help reviewing it and amending.
prev parent reply other threads:[~2012-04-13 19:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 11:16 Unstable bits and JFFS2 Matej Kupljen
2012-04-02 17:12 ` Brian Norris
2012-04-04 9:17 ` Matej Kupljen
2012-04-04 10:54 ` Atlant Schmidt
2012-04-10 7:22 ` Matej Kupljen
2012-04-13 16:27 ` Artem Bityutskiy
2012-04-13 16:40 ` Atlant Schmidt
2012-04-13 17:01 ` Artem Bityutskiy
2012-04-14 4:21 ` Ricard Wanderlof
2012-04-22 14:25 ` Artem Bityutskiy
2012-04-13 18:36 ` Wolfram Sang
2012-04-13 19:49 ` Artem Bityutskiy [this message]
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=1334346542.2200.18.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=aschmidt@dekaresearch.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=matej.kupljen@gmail.com \
--cc=w.sang@pengutronix.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