public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: NZG <ngustavson@emacinc.com>
To: linux-mtd@lists.infradead.org
Subject: inftl broken?
Date: Thu, 12 Oct 2006 09:43:13 -0500	[thread overview]
Message-ID: <200610120943.13429.ngustavson@emacinc.com> (raw)

I've been going throught the mailing lists and haven't been able to come to a 
clear conclusion as to the functionality of inftl. I see a lot of questions, 
but I have yet to find a conclusive answer.

When I attempt to use it, it appears to be broken.

I have build a vanilla 2.6.14.7 kernel, installed it on a debian system, and 
installed mtd-tools.

From the target I:
modprobe inftl
modprobe diskonchip

This correctly detects the diskon chip and creates a partition inftla

I create a secondary partition inftla1 with fdisk.
then:
mke2fs /dev/inftla1
mount /dev/inftla1 /mnt
cd /mnt
touch test
cd /
umount /mnt

I then reboot the system

modprobe inftl
modprobe diskonchip
mount /dev/inftla1 /mnt

and my test file is gone.

I have also attempted to use 2.6.18. It also fails, but differently.
It completely replaces the bad block chain every time the diskonchip driver 
mounts.

Now, I'm flexible in how this is to be used, but I need a working system.

My question is:
***********Is anyone using inftl successfully in any way?*************

Please include details, i.e. filesystem, kernel, utils, etc...
If it' s proprietary and you can't share, then at least say "yes".

If this doesn't work under any circumstances, please consider removing it from 
the kernel, or at least officially calling it broken.

I asked this same question on the IRC last night and no-one seemed to know.

NZG

                 reply	other threads:[~2006-10-12 14:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200610120943.13429.ngustavson@emacinc.com \
    --to=ngustavson@emacinc.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