mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Alex Dubov <oakad@yahoo.com>
Cc: Ben Dooks <ben@fluff.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Smartmedia/xd card support - request for comments
Date: Thu, 17 Apr 2008 15:38:17 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.1.10.0804171535581.3261@apollo.tec.linutronix.de> (raw)
In-Reply-To: <257448.48285.qm@web36701.mail.mud.yahoo.com>

On Thu, 17 Apr 2008, Alex Dubov wrote:
> --- Ben Dooks <ben@fluff.org> wrote:
> 
> > On Thu, Apr 17, 2008 at 01:50:33AM -0700, Alex Dubov wrote:
> > > I've implemented, with generous help from JMicron, a native support for Smartmedia/xD picture
> > card
> > > media. Currently, only JMicron backend is available, but TI expressed some interest in this
> > too,
> > > so TI Flashmedia backend may soon follow.
> > > 
> > > Smartmedia cards are quite akin to the dumb flash chips, but they have their quirks that put
> > them
> > > aside as a separate media type.
> > 
> > They're NAND chips, just with a standard ECC/block replacement
> > stratergy... why isn't this under drivers/mtd ?
> > 
> 
> They have nothing to do with JFFS or UBI (it's an interchange
> format).  They require FTL. 

MTD is independent of JFFS2 and UBI. It's the hardware abtraction
layer on which you build an FTL.

> On the other hand, "SmartMedia reader"
> is a rather definite kind of animal that exists on its own.

No it is not. SmardMedia is a bare NAND chip, which is already covered
by MTD. There are already other FTLs on top of MTD and the SmartMedia
format just can be added to those.

Thanks,
	tglx


  parent reply	other threads:[~2008-04-17 13:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17  8:50 Alex Dubov
2008-04-17  9:01 ` Ben Dooks
2008-04-17  9:11   ` Alex Dubov
2008-04-17 13:10     ` Andy Lutomirski
2008-04-17 13:36       ` Arnd Bergmann
2008-04-17 13:38     ` Thomas Gleixner [this message]
2008-04-17 14:07       ` Jörn Engel
2008-04-17 19:11         ` Thomas Gleixner
2008-04-17 21:21           ` Jörn Engel
2008-04-18  8:47             ` Alex Dubov
2008-04-18  9:35               ` Thomas Gleixner
2008-04-19  2:49                 ` Alex Dubov
2008-04-19  5:56                   ` Thomas Gleixner
2008-04-18 14:00               ` Jörn Engel
2008-04-19  3:05                 ` Alex Dubov
2008-04-19  6:37                   ` Thomas Gleixner
2008-04-19 16:35                     ` Jörn Engel
2008-04-20  2:25                     ` Alex Dubov
2008-04-17 13:35 ` Thomas Gleixner
2008-04-17 14:19 ` Jörn Engel
2008-04-19  8:31 matthieu castet
2008-04-20 16:01 ` Jörn Engel
2008-04-21  1:33   ` Alex Dubov

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=alpine.LFD.1.10.0804171535581.3261@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=ben@fluff.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome