From: "Jörn Engel" <joern@logfs.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Alex Dubov <oakad@yahoo.com>
Subject: Re: [PATCH 9/9] mtd: Add new SmartMedia/xD FTL
Date: Fri, 8 Jan 2010 16:29:45 +0100 [thread overview]
Message-ID: <20100108152945.GC31872@logfs.org> (raw)
In-Reply-To: <1262963524.12577.23.camel@maxim-laptop>
On Fri, 8 January 2010 17:12:04 +0200, Maxim Levitsky wrote:
>
> This implements new readwrite SmartMedia/xd FTL.
>
> It depends on nand driver to define proper oob layout that excludes
> all ecc areas and nothing more.
>
> Support for very old 256 byte/page devices is not yet enabled/complete.
> For these devices, all ecc handling will be done inside this FTL
> due to wierd oob layout.
>
> Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
> ---
> drivers/mtd/Kconfig | 12 +
> drivers/mtd/Makefile | 1 +
> drivers/mtd/sm_ftl.c | 1043 ++++++++++++++++++++++++++++++++++++++++++++++++++
> drivers/mtd/sm_ftl.h | 75 ++++
sm_ftl is certainly nicer than ssfdc.c - at least I can decrypt the
acronym. But I am missing a reason why ssfdc is not sufficient and we
need yet another implementation of the same ftl.
Or maybe ssfdc is sufficient or barely sufficient and just needs a small
patch?
Jörn
--
He that composes himself is wiser than he that composes a book.
-- B. Franklin
WARNING: multiple messages have this Message-ID (diff)
From: "Jörn Engel" <joern@logfs.org>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
Alex Dubov <oakad@yahoo.com>
Subject: Re: [PATCH 9/9] mtd: Add new SmartMedia/xD FTL
Date: Fri, 8 Jan 2010 16:29:45 +0100 [thread overview]
Message-ID: <20100108152945.GC31872@logfs.org> (raw)
In-Reply-To: <1262963524.12577.23.camel@maxim-laptop>
On Fri, 8 January 2010 17:12:04 +0200, Maxim Levitsky wrote:
>
> This implements new readwrite SmartMedia/xd FTL.
>
> It depends on nand driver to define proper oob layout that excludes
> all ecc areas and nothing more.
>
> Support for very old 256 byte/page devices is not yet enabled/complete.
> For these devices, all ecc handling will be done inside this FTL
> due to wierd oob layout.
>
> Signed-off-by: Maxim Levitsky <maximlevitsky@gmail.com>
> ---
> drivers/mtd/Kconfig | 12 +
> drivers/mtd/Makefile | 1 +
> drivers/mtd/sm_ftl.c | 1043 ++++++++++++++++++++++++++++++++++++++++++++++++++
> drivers/mtd/sm_ftl.h | 75 ++++
sm_ftl is certainly nicer than ssfdc.c - at least I can decrypt the
acronym. But I am missing a reason why ssfdc is not sufficient and we
need yet another implementation of the same ftl.
Or maybe ssfdc is sufficient or barely sufficient and just needs a small
patch?
Jörn
--
He that composes himself is wiser than he that composes a book.
-- B. Franklin
next prev parent reply other threads:[~2010-01-08 15:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 15:04 RFC: [PATCH V2 0/9 Integration of SmartMedia/xD into mtd subsystem Maxim Levitsky
2010-01-08 15:04 ` Maxim Levitsky
2010-01-08 15:05 ` [PATCH 1/9] MTD: call remove notifiers before removing the device Maxim Levitsky
2010-01-08 15:05 ` Maxim Levitsky
2010-01-08 15:06 ` [PATCH 2/9] MTD: create lockless versions of {get,put}_mtd_device Maxim Levitsky
2010-01-08 15:06 ` Maxim Levitsky
2010-01-08 15:21 ` [PATCH 2/9] MTD: create lockless versions of {get, put}_mtd_device Jörn Engel
2010-01-08 15:21 ` [PATCH 2/9] MTD: create lockless versions of {get,put}_mtd_device Jörn Engel
2010-01-08 15:27 ` Maxim Levitsky
2010-01-08 15:27 ` Maxim Levitsky
2010-01-08 15:31 ` [PATCH 2/9] MTD: create lockless versions of {get, put}_mtd_device Jörn Engel
2010-01-08 15:31 ` [PATCH 2/9] MTD: create lockless versions of {get,put}_mtd_device Jörn Engel
2010-01-08 15:07 ` [PATCH 3/9] MTD: blkdevs: make hotplug work Maxim Levitsky
2010-01-08 15:07 ` Maxim Levitsky
2010-01-08 15:08 ` [PATCH 4/9] MTD: make mtdtrans thread freezable Maxim Levitsky
2010-01-08 15:08 ` Maxim Levitsky
2010-01-08 15:08 ` [PATCH 5/9] MTD: nand subsystem, export nand_do_read_oob and nand_do_write_oob Maxim Levitsky
2010-01-08 15:08 ` Maxim Levitsky
2010-01-08 15:09 ` [PATCH 6/9] mtd: common module for smartmedia/xD support Maxim Levitsky
2010-01-08 15:09 ` Maxim Levitsky
2010-01-08 15:10 ` [PATCH 7/9] MTD: add few workarounds to nand system for SmartMedia/xD chips Maxim Levitsky
2010-01-08 15:10 ` Maxim Levitsky
2010-01-08 15:11 ` [PATCH 8/9] mtd: Add nand driver for ricoh xD/SmartMedia reader Maxim Levitsky
2010-01-08 15:11 ` Maxim Levitsky
2010-01-08 15:12 ` [PATCH 9/9] mtd: Add new SmartMedia/xD FTL Maxim Levitsky
2010-01-08 15:12 ` Maxim Levitsky
2010-01-08 15:29 ` Jörn Engel [this message]
2010-01-08 15:29 ` Jörn Engel
2010-01-08 15:35 ` Maxim Levitsky
2010-01-08 15:35 ` Maxim Levitsky
2010-01-08 16:04 ` RFC: [PATCH V2 0/9 Integration of SmartMedia/xD into mtd subsystem Jörn Engel
2010-01-08 16:04 ` Jörn Engel
2010-01-08 17:40 ` Maxim Levitsky
2010-01-08 17:40 ` Maxim Levitsky
2010-01-09 0:26 ` Jörn Engel
2010-01-09 0:26 ` Jörn Engel
2010-01-11 22:24 ` Maxim Levitsky
2010-01-11 22:24 ` Maxim Levitsky
-- strict thread matches above, loose matches on Subject: below --
2010-01-12 19:28 RFC: [PATCH V3 " Maxim Levitsky
2010-01-12 19:37 ` [PATCH 9/9] MTD: Add new SmartMedia/xD FTL Maxim Levitsky
2010-01-12 19:37 ` Maxim Levitsky
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=20100108152945.GC31872@logfs.org \
--to=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=maximlevitsky@gmail.com \
--cc=oakad@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.