From: Artem Bityutskiy <dedekind@infradead.org>
To: Vitaly Wool <vwool@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org, kbaidarov <kbaidarov@dev.rtsoft.ru>
Subject: Re: [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD
Date: Mon, 20 Nov 2006 15:39:44 +0200 [thread overview]
Message-ID: <1164029984.5597.100.camel@sauron> (raw)
In-Reply-To: <4561A84A.9000807@ru.mvista.com>
On Mon, 2006-11-20 at 16:06 +0300, Vitaly Wool wrote:
> Artem Bityutskiy wrote:
> > I am talking about something like this:
> >
> > http://lists.infradead.org/pipermail/linux-mtd/2004-May/009683.html
> >
> This one unconditionally changes mtdblock, doesn't it?
Yes.
Basically speaking, mtdblock was designed for NOR flashes and there were
no bad eraseblocks at all. Now you want to utilize it on NANDs. So you
add BB-awareness functionality. And I still think you should changd
mtdblock_ro instead of adding new driver.
Why? Because if you change mtdblock_ro:
1. you do not change semantics at all. in case of old BB-less flashes
all stays the same old way. So I do not understand why you need a new
device number.
2. You make mtdblock_ro workable on NAND. You extend it. You have right
to slightly change the semantics. 1:1 mapping makes no sense in this
case, so it is logical to skip bad blocks. Instead you add a new driver.
Strange.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-11-20 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 15:40 [PATCH] [MTD] BLOCK_RO: Readonly Block Device Layer Over MTD kbaidarov
2006-11-18 13:15 ` Artem Bityutskiy
2006-11-18 13:33 ` Josh Boyer
2006-11-18 13:35 ` Artem Bityutskiy
2006-11-18 13:40 ` Artem Bityutskiy
2006-11-20 12:15 ` Vitaly Wool
2006-11-20 12:46 ` Artem Bityutskiy
2006-11-20 13:06 ` Vitaly Wool
2006-11-20 13:39 ` Artem Bityutskiy [this message]
2006-11-20 13:20 ` Konstantin Baydarov
2006-11-20 12:11 ` Vitaly Wool
2006-11-20 12:05 ` Vitaly Wool
2006-11-20 14:52 ` Josh Boyer
2006-11-21 10:30 ` Vitaly Wool
2006-11-22 16:56 ` Konstantin Baydarov
2006-12-02 16:41 ` Konstantin Baydarov
2007-09-27 15:05 ` Gregory CLEMENT
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=1164029984.5597.100.camel@sauron \
--to=dedekind@infradead.org \
--cc=kbaidarov@dev.rtsoft.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=vwool@ru.mvista.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