From: Konstantin Kletschke <lists@ku-gbr.de>
To: Nicolas Pitre <nico@cam.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: XIP issues introduced between 2.6.12 and 2.6.13
Date: Wed, 12 Oct 2005 19:06:43 +0200 [thread overview]
Message-ID: <87r7aqvf4s.wl%kletschke@synertronixx.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0510121248520.23357@localhost.localdomain>
At Wed, 12 Oct 2005 12:52:49 -0400 (EDT),
Nicolas Pitre <nico@cam.org> wrote:
> OK.... Let me resume that:
>
> 1) you have an XIP kernel
Yes.
> 2) if you use NFS everything is fine
NFS used in both cases as root file system.
> 3) if you use JFFS2 built as a module everything _appears_ fine
Yes.
> 4) if you use JFFS2 built-in it crashes.
Yes.
> When JFFS2 is modular, are MTD drivers modular as well?
In both cases built in.
Only difference a "jffs2" in lsmod output or not :-)
K
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
next prev parent reply other threads:[~2005-10-12 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 16:30 XIP issues introduced between 2.6.12 and 2.6.13 Konstantin Kletschke
2005-10-12 16:52 ` Nicolas Pitre
2005-10-12 17:06 ` Konstantin Kletschke [this message]
2005-10-12 17:47 ` Nicolas Pitre
2005-10-12 20:11 ` Konstantin Kletschke
2005-10-12 20:44 ` Konstantin Kletschke
-- strict thread matches above, loose matches on Subject: below --
2005-10-13 9:43 Konstantin Kletschke
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=87r7aqvf4s.wl%kletschke@synertronixx.de \
--to=lists@ku-gbr.de \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.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