From: adr <mtd@mcmen.demon.co.uk>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Mtd <linux-mtd@lists.infradead.org>
Subject: Re: Writing an mtd user module
Date: Sun, 8 Sep 2002 20:49:02 +0100 [thread overview]
Message-ID: <200209082049.02572.mtd@mcmen.demon.co.uk> (raw)
In-Reply-To: <20020908173635.GA19559@wohnheim.fh-wedel.de>
On Sunday 08 Sep 2002 6:36 pm, Jörn Engel wrote:
> On Sun, 8 September 2002 17:26:50 +0100, adr wrote:
> > Having written a driver module for the Dreamcast flash cartridge/vmu, I
> > am now attempting to write a user module that works with the default fs
> > on the Dreamcast flash (see http://mc.pp.se/dc/vms/flashmem.html if you
> > are interested in knowing more about that).
> >
>
> The block devices don't need to be notified of any changes, devfs
> does. When you "ls /dev/mtdblock", you want to see all the devices
> currently registered.
> To reach that goal, on 'insmod slram something", which creates a new
> device, mtdblock has to be notified of the change in order to change
> the devfs entries.
>
> Now, for an fs, you only need one device, known from mount to umount,
> so register_mtd_user() is pointless for that purpose.
>
> Jrn
I'm not sure I fully understand this :-<
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?
Adrian
next prev parent reply other threads:[~2002-09-08 19:47 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 [this message]
2002-09-09 7:35 ` 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=200209082049.02572.mtd@mcmen.demon.co.uk \
--to=mtd@mcmen.demon.co.uk \
--cc=joern@wohnheim.fh-wedel.de \
--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