From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: "Menon, Nishanth" <x0nishan@ti.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Jffs2 issue on latest mtd for Sibley NOR
Date: Tue, 22 Nov 2005 19:15:29 +0300 [thread overview]
Message-ID: <43834421.1050509@yandex.ru> (raw)
In-Reply-To: <520AB2AD990DC04082102F77CA17263801CE70B4@dlee03.ent.ti.com>
Menon, Nishanth wrote:
> Hi All,
> I have been trying Sibley NOR flash and the latest (as of today) MTD
> tree on my kernel.
> When I use the character device, I am able to unlock, erase, write and
> read from it successfully. Unfortunately, when I try to use jffs2 on it,
> I face the following issue:
Could you please try to reproduce this on mtdram device which is just an
emulator of NOR flash in RAM ?
> CONFIG_JFFS2_FS=y
> CONFIG_JFFS2_FS_DEBUG=2
Uhh. Too much log rubbish will be produced with this.
> CONFIG_JFFS2_FS_WRITEBUFFER=y
This is not usually needed for NOR. is 'siblay' an exception? But JFFS2
still should work.
> CONFIG_JFFS2_ZLIB=y
> CONFIG_JFFS2_RTIME=y
> # CONFIG_JFFS2_RUBIN is not set
> # CONFIG_JFFS2_LZO is not set
> # CONFIG_JFFS2_LZARI is not set
> # CONFIG_JFFS2_CMODE_NONE is not set
> CONFIG_JFFS2_CMODE_PRIORITY=y
> # CONFIG_JFFS2_CMODE_SIZE is not set
> CONFIG_JFFS2_PROC=y
Uh, it is interesting. I did not know anything about this option. I
thought JFFS2 does not expose anything to /proc ...
--
Best Regards,
Artem B. Bityutskiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-11-22 16:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 15:55 Jffs2 issue on latest mtd for Sibley NOR Menon, Nishanth
2005-11-22 16:15 ` Artem B. Bityutskiy [this message]
2005-11-22 16:57 ` Nicolas Pitre
2005-11-22 17:01 ` Artem B. Bityutskiy
2005-11-22 22:24 ` Todd Poynor
2005-11-22 22:47 ` Nicolas Pitre
2005-12-03 22:01 ` Jared Hulbert
2005-11-23 18:09 ` Nicolas Pitre
[not found] <520AB2AD990DC04082102F77CA17263801D40623@dlee03.ent.ti.com>
2005-11-23 18:51 ` Nicolas Pitre
[not found] <520AB2AD990DC04082102F77CA17263801D4063E@dlee03.ent.ti.com>
2005-11-23 19:40 ` Nicolas Pitre
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=43834421.1050509@yandex.ru \
--to=dedekind@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=x0nishan@ti.com \
/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.