public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, jffs-dev@axis.com
Subject: Re: jffs on non-MTD device?
Date: Fri, 25 May 2001 09:44:10 +0100	[thread overview]
Message-ID: <24676.990780250@redhat.com> (raw)
In-Reply-To: <20010525005253.A16005@bug.ucw.cz>
In-Reply-To: <20010525005253.A16005@bug.ucw.cz>


pavel@suse.cz said:
> I'm trying to run jffs on my ATA-flash disk (running ext2 could kill
> some flash cells too soon, right?) but it refuses:

CompactFlash does wear levelling internally. 

>         if (MAJOR(dev) != MTD_BLOCK_MAJOR) {
>                 printk(KERN_WARNING "JFFS: Trying to mount a "
>                        "non-mtd device.\n");
>                 return 0;
>         }

> What are reasons for this check? 

JFFS doesn't actually use the block device interface. Specifying it in the 
mount command is simply a hack to make life easier, which nobody's yet 
managed to obsolete. We actually use the underlying MTD device:

        mtd = get_mtd_device(NULL, MINOR(dev));

If you want JFFS (or JFFS2) on a CF device - in the apparent absence of any 
other relatively low overhead, compressing, journalling file system to use 
on it - then you need to provide a translation driver similar to the mtdram 
one which fakes an MTD device, using a block device as backing store.

--
dwmw2



  reply	other threads:[~2001-05-25  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-24 22:52 jffs on non-MTD device? Pavel Machek
2001-05-25  8:44 ` David Woodhouse [this message]
2001-06-11 11:45 ` Padraig Brady
2001-06-11 12:41 ` David Woodhouse

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=24676.990780250@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jffs-dev@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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