From: Junping Zhang <JZhang@erinc.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Junping Zhang" <JZhang@erinc.com>
Cc: linux-mtd@lists.infradead.org
Subject: RE: seeking help on JFFS2
Date: Tue, 5 Nov 2002 14:56:56 -0500 [thread overview]
Message-ID: <F4608F665DF5D311B231009027B70F700131DF9D@MAIL> (raw)
Jörn,
I just tested 2.4.19 with shared-zlib patch, same behavior. I could use
the JFFS2 system,
but it will eventually crash after a while.
The flash chip is original from Motorola: 8M, 80 pin SIMM, SM73228. I
used Christian's
map file. Since JFFS works on it without any problem, should I safely assume
the MTD layer
is correct?
I appreciate your thought, but my company won't let me give people
direct access. I will
check out the latest MTD from cvs tonight and give it a try tomorrow.
Thanks
- Junping
> -----Original Message-----
> From: Jörn Engel [SMTP:joern@wohnheim.fh-wedel.de]
> Sent: Tuesday, November 05, 2002 2:31 PM
> To: Junping Zhang
> Cc: linux-mtd@lists.infradead.org
> Subject: Re: seeking help on JFFS2
>
> On Tue, 5 November 2002 12:39:31 -0500, Junping Zhang wrote:
> > Yes, the minor number is 2, and I checked mkfs.jffs2 source, hex is ok.
> I
> > also tried with
> > the method you mentioned, the crashed happened right away.
>
> Ok.
>
> > I just tried using the stock JFFS2 in 2.4.18 kernel. It actually got me
> > further than JFFS2
> > in my mtd-20021022 snapshot, I could use either image or direct mount to
> > create JFFS2,
> > but it still crashed under stress test. On the other hand, JFFS works
> quite
> > well.
>
> Ok.
>
> > Does stock 2.4.19 have a stable JFFS2 without patch? I downloaded a
> > shared-zlib patch
> > for 2.4.19-pre10 but am not sure it will fix my JFFS2 problem.
>
> 2.4.19 should have a stable jffs2, as should 2.4.18. You can try
> 2.4.19, but I don't expect any better behaviour.
>
> What flashes do you exactly use? And can you provide ssh login to the
> development host?
>
> Jörn
>
> --
> If you're willing to restrict the flexibility of your approach,
> you can almost always do something better.
> -- John Carmack
next reply other threads:[~2002-11-05 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 19:56 Junping Zhang [this message]
2002-11-05 21:08 ` seeking help on JFFS2 Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 18:26 Junping Zhang
2002-11-06 16:09 Junping Zhang
2002-11-06 16:14 ` David Woodhouse
2002-11-07 8:28 ` Joakim Tjernlund
2002-11-07 8:49 ` David Woodhouse
2002-11-06 13:13 Junping Zhang
2002-11-05 17:39 Junping Zhang
2002-11-05 19:31 ` Jörn Engel
2002-11-05 17:17 Jeffrey Lim
2002-11-05 19:32 ` Jörn Engel
2002-11-05 13:40 Junping Zhang
2002-11-05 16:41 ` Jörn Engel
2002-11-06 3:57 ` Darren Freeman
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=F4608F665DF5D311B231009027B70F700131DF9D@MAIL \
--to=jzhang@erinc.com \
--cc=joern@wohnheim.fh-wedel.de \
--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