From: Charles Manning <manningc2@actrix.gen.nz>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: NAND simulator
Date: Mon, 12 Dec 2005 06:53:33 +1300 [thread overview]
Message-ID: <200512120653.33614.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <439C2DA3.9090405@yandex.ru>
On Monday 12 December 2005 02:46, Artem B. Bityutskiy wrote:
> Charles Manning wrote:
> > Yes please.
>
> Uhh, will pospone this for now, will try to repair JFFS2 which doesn't
> work after the last month's commits. Crud! Not sure whom to blame so far.
>
> > Can nandsim simulate storage larger than physical RAM (just swapping out)
> > or would this need special support (eg. add some block device support?
> > We're getting people in YAFFSland who are working with 8Gbytes of flash
> > (and it will only get bigger!) and I expect you'd want large emulations
> > to stress JFFS3. Being able to simulate areas up to, say, 16Gbytes for
> > now would be a nice thing.
>
> Well, did not plan it. But we probably may add this functionality. We
> may borrow it from mtd2blk ...
>
> > A way of simulating a failure (bit flip, write error) would also be handy
> > for testing fs and ecc error handling.
>
> Yeah, good feature. But I'm not sure how to implement an interface for
> this. It is probably easier to hack nandsim and add this manually...
Manual hacking does work. I have done stuff like that in the past. Perhaps
dynamic hacking could be done via procfs?
eg, perhaps somethiong like
echo "flip 12345 400 1" > /procfs/nandsim # flip bit 1 in byte 400, page
12345
next prev parent reply other threads:[~2005-12-11 17:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 12:07 NAND simulator Artem B. Bityutskiy
2005-12-10 22:28 ` Charles Manning
2005-12-11 13:46 ` Artem B. Bityutskiy
2005-12-11 17:53 ` Charles Manning [this message]
2005-12-11 22:07 ` Josh Boyer
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=200512120653.33614.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--cc=dedekind@yandex.ru \
--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