From: David Woodhouse <dwmw2@infradead.org>
To: adr <mtd@mcmen.demon.co.uk>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
Mtd <linux-mtd@lists.infradead.org>
Subject: Re: Writing an mtd user module
Date: Mon, 09 Sep 2002 08:35:23 +0100 [thread overview]
Message-ID: <23606.1031556923@redhat.com> (raw)
In-Reply-To: <200209082049.02572.mtd@mcmen.demon.co.uk>
mtd@mcmen.demon.co.uk said:
> What was wrong, the documentation on the websiste or my
> interpretation of it? Am I to take it the notification functions are
> irrelevant except when devfs is being used?
The notification functions are irrelevant if you don't want to be notified
when new devices are added or when devices go away.
In the case of the mtdblock device, yes that means they're irrelevant when
devfs is not used. Only in the case where devfs is used do you need to do
anything (change contents of /dev/mtdblock/) on addition/removal of devices.
You probably want something like JFFS2's read_super() or get_sb() functions
to allow you to mount a single device.
--
dwmw2
prev parent reply other threads:[~2002-09-09 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-08 16:26 Writing an mtd user module adr
2002-09-08 17:36 ` Jörn Engel
2002-09-08 19:49 ` adr
2002-09-09 7:35 ` David Woodhouse [this message]
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=23606.1031556923@redhat.com \
--to=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.org \
--cc=mtd@mcmen.demon.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox