From: Brad Beveridge <bbeveridge@bluewatersys.com>
To: linux-mtd@lists.infradead.org
Subject: Removable flash storage
Date: Wed, 17 Nov 2004 16:06:12 +1300 [thread overview]
Message-ID: <419AC024.1060202@bluewatersys.com> (raw)
Hello all.
I am working with a device that has 3 nand flash slots, two are internal
and not removable, one is external and is removable.
We currently have a single driver that registers partitions on each card
at kernel boot time. All three cards work, and we use yaffs as a
filesystem on top of MTD.
I am trying to come up with a clean way of allowing the external card to
be inserted/removed at runtime.
One solution is to have a seperate nand driver for that card & build it
as a module, then simply modprobe/rmmod. However, that solution isn't
so great because we then have two driver source files that are
essentially the same.
We also thought that a /proc based solution might work, where you write
"eject 3" or something to /proc/mtd.
What will play nicest with MTD as it stands? If I need to break the
driver up, is there any suggestions for minimising code duplication?
Cheers
Brad
next reply other threads:[~2004-11-17 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 3:06 Brad Beveridge [this message]
[not found] ` <419BCFA2.5090900@bluewatersys.com>
2004-11-17 23:23 ` Removable flash storage Brad Beveridge
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=419AC024.1060202@bluewatersys.com \
--to=bbeveridge@bluewatersys.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