From: Dan Brown <dan.brown@nrl.navy.mil>
To: Braden Simpson <braden.simpson@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 and INFTL compatibility
Date: Thu, 09 Feb 2006 09:08:31 -0500 [thread overview]
Message-ID: <43EB4CDF.6040101@nrl.navy.mil> (raw)
In-Reply-To: <7e560e180602062009v7fbe544ay4a93751778626b07@mail.gmail.com>
Braden Simpson wrote:
> What do I need to do to stop the INFTL driver from corrupting the JFFS2
> partition?
Here's the deal. Basically, the INFTL driver was written assuming it's
the only driver using the device. However, I believe you can work
around this.
When the INFTL driver is loaded (or when your kernel boots, if it's
compiled in), it searches through each MTD device. It rejects anything
that isn't a DiskOnChip. For each DiskOnChip, it scans for the *first*
BDTL partition, and mounts it as an INFTL volume. It can't distinguish
between a corrupted INFTL volume and something that isn't INFTL at all
(such as JFFS2).
So, make sure your INFTL partition is FIRST, then your jffs2. If this
was already the case for you, I'll have to give this some more thought.
The relevant code is find_boot_record() in inftlmount.c.
You mentioned that you had to patch fill_autooob_layout(). If you think
this is relevant to other users, please consider posting your changes
and the reason for them on this list.
Good luck!
-Dan
next prev parent reply other threads:[~2006-02-09 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 4:09 JFFS2 and INFTL compatibility Braden Simpson
2006-02-09 14:08 ` Dan Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-07 3:32 Braden Simpson
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=43EB4CDF.6040101@nrl.navy.mil \
--to=dan.brown@nrl.navy.mil \
--cc=braden.simpson@gmail.com \
--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