All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Maxim Levitsky <slevmax@t2.technion.ac.il>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Alex Dubov <oakad@yahoo.com>,
	arnd@arndb.de, tglx@linutonix.de
Subject: Re: XD/smartmedia - how to implement it right?
Date: Sat, 21 Nov 2009 11:25:43 +0100	[thread overview]
Message-ID: <20091121102542.GA21136@logfs.org> (raw)
In-Reply-To: <1258763144.4997.12.camel@maxim-laptop>

On Sat, 21 November 2009 02:25:44 +0200, Maxim Levitsky wrote:
> 
> This thread is meant to continue discussion about XD/smartmedia support
> in linux.
> 
> I CC'd few peoples that participated in original discussion.
> 
> Alex Dubov attempted to write a driver for jmicron device (I have it
> btw), but this was rejected due to code duplication.
> 
> I successfully reverse engineered (in my free time) the XD card reader
> found on my laptop (ricoh based one)
> 
> I would like to know how you think to implement the subsystem support
> right.
> 
> I would go with mmc subsystem + FTL, but according to original thread,
> there are numerous problems with this approach.
> 
> Any advice is appreciated.

A novel approach might be to just send the code as a patch.  Last time
around noone seemed to have had a real look.

The "mtd uses blocking calls" argument I can help with.  For some other
project I've added non-blocking calls to mtd[1].

Biggest problems I see are a) the userspace interface and b) allowing
both raw flash access through MTD and block device access with an FTL.

[1] http://lists.infradead.org/pipermail/linux-mtd/2009-November/028065.html

Jörn

-- 
The wise man seeks everything in himself; the ignorant man tries to get
everything from somebody else.
-- unknown

  reply	other threads:[~2009-11-21 10:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-21  0:25 XD/smartmedia - how to implement it right? Maxim Levitsky
2009-11-21 10:25 ` Jörn Engel [this message]
2009-11-22 12:58   ` Maxim Levitsky
2009-11-24 23:50     ` Plan for adding XD support in mtd layer Maxim Levitsky
2009-11-25 10:40       ` Jörn Engel
2009-11-25 13:20         ` Maxim Levitsky
2009-11-25 15:34           ` Jörn Engel
2009-11-25 16:17             ` Maxim Levitsky
2009-11-25 20:59               ` Jörn Engel
2009-11-25 23:22                 ` Maxim Levitsky
2009-11-26  8:27                   ` Jörn Engel
2009-11-26 13:02                     ` Maxim Levitsky
2009-11-26 13:42                       ` Jörn Engel
2009-11-26 21:38                         ` Maxim Levitsky
2009-11-28  7:22   ` XD/smartmedia - how to implement it right? Alex Dubov
2009-11-28 10:36     ` Maxim Levitsky
2009-11-30 12:35       ` Alex Dubov
2009-11-30 13:58         ` Maxim Levitsky
2009-11-30 23:04           ` Maxim Levitsky
2009-12-01  8:22             ` Jörn Engel
2009-12-01 16:10               ` Alex Dubov
2009-12-01 16:41                 ` Maxim Levitsky
2009-12-11 23:48               ` Maxim Levitsky
2009-12-05 19:09           ` Pavel Machek
2009-12-06 21:27             ` Maxim Levitsky
2009-12-07 15:13               ` Arnd Bergmann

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=20091121102542.GA21136@logfs.org \
    --to=joern@logfs.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oakad@yahoo.com \
    --cc=slevmax@t2.technion.ac.il \
    --cc=tglx@linutonix.de \
    /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.