From: "dedekind" <dedekind@yandex.ru>
To: dwmw2@infradead.org
Cc: dedekind@yandex.ru, jwboyer@gmail.com, linux-mtd@lists.infradead.org
Subject: Re: State of UBI
Date: Sun, 10 Sep 2006 21:00:04 +0400 (MSD) [thread overview]
Message-ID: <45044494.000002.04222@tide.yandex.ru> (raw)
In-Reply-To: <1157885559.2977.136.camel@pmac.infradead.org>
>I had envisaged that it would be fairly much akin to
>another partitioning layer, perhaps requiring a few extra methods to be
>added to the mtd_info.
To be more persuadive - I'll add to my previous mail.
It is similar to disc partitions and LVM volumes.
One can create can create several partitions. Then feed some of them to
LVM and create one or more volume groups (which is similar to UBI device(s)).
Then create logical volumes in each volume group (similar to create UBI volumes
within each UBI device).
E.g., the simplest configuration:
1. hda1 for /boot (otherwise the bootloader has to be smart and understand
LVM tables)
2. hda2 for LVM
3. and then create as many logical volumes as you want.
And in my previous example it is similar.
1. mtd0 for the kernel (otherwise the bootloader has to be smart enough
to understand UBI format)
2. mtd1 for UBI
3. then create as many UBI volumes as you want.
Full analogy with LVM. It'd be strange not to follow this model.
Artem.
next prev parent reply other threads:[~2006-09-10 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 2:22 State of UBI Josh Boyer
2006-09-10 8:47 ` dedekind
2006-09-10 10:52 ` David Woodhouse
2006-09-10 12:35 ` Josh Boyer
2006-09-10 13:19 ` dedekind
2006-09-10 17:00 ` dedekind [this message]
2006-09-10 17:44 ` David Woodhouse
2006-09-11 6:11 ` dedekind
2006-09-10 12:32 ` Josh Boyer
2006-09-10 13:34 ` dedekind
2006-09-10 14:11 ` Josh Boyer
2006-09-10 14:23 ` dedekind
2006-09-11 8:11 ` David Woodhouse
2006-09-11 9:19 ` dedekind
2006-09-11 13:21 ` 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=45044494.000002.04222@tide.yandex.ru \
--to=dedekind@yandex.ru \
--cc=dwmw2@infradead.org \
--cc=jwboyer@gmail.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