All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Radensky <felix@allot.com>
To: Simon Evans <spse@secret.org.uk>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Block device as MTD
Date: Wed, 27 Jun 2001 09:49:39 +0300	[thread overview]
Message-ID: <3B398202.CC5B6125@allot.com> (raw)
In-Reply-To: E15EzJQ-0008Px-00@spoinky.secret.org.uk

Simon Evans wrote:

> I have checked this into CVS now. The following files are affected:
>
> drivers/mtd/devices/blkmtd.c  - the driver itself
> drivers/mtd/devices/Config.in
> drivers/mtd/devices/Makefile
> patches/Configure.help
>
> Please consider this alpha software. It uses raw/io to the disk (not via
> the buffer cache). Basic usage is:
>
> modprobe blkmtd device=/dev/floppy/0  etc
>
> If you are going to put a JFFS2 fs on the device, please note that
> it can take quite a while to mount because JFFS2 scans every block.
> A 96MB CF card took about 2 minutes.
>
> On the plus side, if you have more memory then the size of the device,
> you should find the whole device in the page cache ;)
>
> cheers
> si
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

Hi,

We have CF slot on our board, but no IDE controllers. Can I still use your
blkmtd.c driver to access CF ? If not, what approach should I take to
utilize
CF (adding IDE controller is not an option) ?

Thanks in advance.

Felix.

  parent reply	other threads:[~2001-06-27  6:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 10:33 Block device as MTD Simon Evans
2001-06-26 18:22 ` Tim Riker
2001-06-26 20:19 ` Simon Evans
2001-06-26 21:41   ` Bao C. Ha
2001-06-26 20:58     ` Simon Evans
2001-06-26 23:12   ` kira brown
2001-06-26 23:32     ` Bao C. Ha
2001-06-27  6:49   ` Felix Radensky [this message]
2001-06-27 22:03     ` Simon Evans
2001-06-27 23:41       ` Bill Roman
  -- strict thread matches above, loose matches on Subject: below --
2001-06-28  7:39 Michel Stempin

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=3B398202.CC5B6125@allot.com \
    --to=felix@allot.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=spse@secret.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.