From: "Kluba, Patrik" <pajko@halom.u-szeged.hu>
To: linux-mtd@lists.infradead.org
Subject: Re: combine 2 mtds into a single mtd device?
Date: Tue, 09 Nov 2004 09:54:22 +0100 [thread overview]
Message-ID: <opsg6wcwrvwtryne@mail.halom.u-szeged.hu> (raw)
In-Reply-To: <20041109083203.11121.qmail@sina.com.tw>
Hi!
Look at drivers/mtdconcat.c. This implements a device concatenation layer.
Every function is included to handle multiple MTD devices as a virtual
one. The virtual device must be created with the exported
mtd_concat_create function, and must be destroyed with the
mtd_concat_destroy after use. This function does not register devices, you
should write a module which calls mtd_concat_create with proper parameters
and registers the newly created device.
For example, drivers/mtd/maps/dilnetpc.c is a good starting point.
--
pajko
On Tue, 09 Nov 2004 16:32:02 +0800, <mjabe@sina.com.tw> wrote:
> The follow is my MTD partition:
>
> How to combine MTD1 and MTD2 into a single mtd device?
prev parent reply other threads:[~2004-11-09 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 8:32 combine 2 mtds into a single mtd device? mjabe
2004-11-09 8:54 ` Kluba, Patrik [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=opsg6wcwrvwtryne@mail.halom.u-szeged.hu \
--to=pajko@halom.u-szeged.hu \
--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