public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Vinit Agnihotri <vinit.agnihotri@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Yet Another UBI Question
Date: Mon, 19 Nov 2007 11:41:05 +0200	[thread overview]
Message-ID: <1195465265.1119.24.camel@sauron> (raw)
In-Reply-To: <9b52d64c0711190124p6730356ep3b0c7a381863a905@mail.gmail.com>

On Mon, 2007-11-19 at 14:54 +0530, Vinit Agnihotri wrote:
> Hi,
> As a part of work I have work with UBI & character drivers i.e. cdev.c in UBI.
> Can we think of implementing block device drivers instead of cdev to
> implement volume?
> That way we'll not be needing any block emulation layer on top of
> volume cdev & user will be able to
> put any file system on top of it.
> Will it complicate volume management or wear levelling anyway????

Sorry, not sure what you mean. UBI character devices represent UBI
volumes, they give you a possibility to update volumes, to read them, to
fetch different kind of information. So we need them.

An UBI volume is not a block device
(http://www.linux-mtd.infradead.org/faq/ubi.html#L_ext2_over_ubi)

You do have to write quite complex layer of code to implement FTL on top
of UBI. Once you've done this, just expose the resulting block devices
as /dev/ubiblock0 block device nodes. This is how I see it.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2007-11-19  9:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 20:50 UBI in Shipping Products ?? Johnson, Charles F
2007-10-24 22:39 ` Yet Another UBI Question Johnson, Charles F
2007-11-19  8:59   ` Artem Bityutskiy
2007-11-19  9:24   ` Vinit Agnihotri
2007-11-19  9:41     ` Artem Bityutskiy [this message]
2007-11-19 10:06       ` Vinit Agnihotri
2007-11-19 14:20         ` Artem Bityutskiy
2007-10-26 12:17 ` UBI in Shipping Products ?? Josh Boyer
2007-10-26 15:36   ` Johnson, Charles F

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=1195465265.1119.24.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=vinit.agnihotri@gmail.com \
    /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