From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "Artem B. Bityutskiy" <dedekind@yandex.ru>
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: blkmtd and name_to_dev_t
Date: Tue, 4 Apr 2006 10:46:59 +0200 [thread overview]
Message-ID: <20060404084659.GA11384@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <4432318E.5050002@yandex.ru>
On Tue, 4 April 2006 12:42:54 +0400, Artem B. Bityutskiy wrote:
>
> This is a bit out of context and I'm not arguing. Just wanted to note.
> Mount and linux long support device-less mount. The beset way to mount
> JFFS2 would be to do like this:
>
> mount mtd0 /mnt/jffs2 -t jffs2
>
> No need to have any fake block device, no need to have any device node
> at all. JFFS2 seems to (not sure) not support this but it is trivial to add.
>
> I tend to think that this mtdblock fake stuff is some ancient crap and
> has to go and not confuse people.
Artem, this is the other way around. You are talking about having a
fake block device to mount jffs2 on mtd. mtd->bd
I was talking about having a fake mtd on top of a block device to
mount jffs2 on it. bd->mtd
Yes, the whole translate this into that business around mtd is rather
confusing. It is unfortunate that a struct block_device is not
sufficient for flash purposes (yet?).
Jörn
--
Sometimes, asking the right question is already the answer.
-- Unknown
next prev parent reply other threads:[~2006-04-04 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060329232520.1677d2b3.akpm@osdl.org>
[not found] ` <442C0494.2040609@zytor.com>
[not found] ` <20060330114014.53150d1b.akpm@osdl.org>
2006-03-30 23:36 ` blkmtd and name_to_dev_t H. Peter Anvin
2006-03-31 8:38 ` Jörn Engel
2006-03-31 15:10 ` H. Peter Anvin
2006-04-04 2:56 ` Eric W. Biederman
2006-04-04 3:07 ` H. Peter Anvin
2006-04-04 8:30 ` Jörn Engel
2006-04-04 8:42 ` Artem B. Bityutskiy
2006-04-04 8:46 ` Jörn Engel [this message]
2006-04-04 8:57 ` Artem B. Bityutskiy
2006-04-04 3:11 ` Josh Boyer
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=20060404084659.GA11384@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dedekind@yandex.ru \
--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