From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Alex Dubov <oakad@yahoo.com>
Cc: "Jörn Engel" <joern@logfs.org>,
linux-kernel <linux-kernel@vger.kernel.org>, arnd <arnd@arndb.de>
Subject: Re: XD/smartmedia - how to implement it right?
Date: Tue, 01 Dec 2009 18:41:51 +0200 [thread overview]
Message-ID: <1259685711.18599.22.camel@maxim-laptop> (raw)
In-Reply-To: <621988.63882.qm@web37601.mail.mud.yahoo.com>
On Tue, 2009-12-01 at 08:10 -0800, Alex Dubov wrote:
>
> --- On Tue, 12/1/09, Jörn Engel <joern@logfs.org> wrote:
>
> > From: Jörn Engel <joern@logfs.org>
> > Subject: Re: XD/smartmedia - how to implement it right?
> > To: "Maxim Levitsky" <maximlevitsky@gmail.com>
> > Cc: "Alex Dubov" <oakad@yahoo.com>, "linux-kernel" <linux-kernel@vger.kernel.org>, arnd@arndb.de, tglx@linutonix.de
> > Date: Tuesday, December 1, 2009, 12:22 AM
> > On Tue, 1 December 2009 01:04:26
> > +0200, Maxim Levitsky wrote:
> > >
> > > Alex, could you do me a favor, and explain why partial
> > block writes
> > > don't work?
> > > What happens if its done?
> >
> > With the Alauda and the limited set of cards I tried they
> > work.
> >
> > Jörn
> >
>
> It's a bug particular to jmicron controllers.
Thanks!
So, I will write the driver for my controller using nand subsystem, and
then, I see what to do next.
If you write your mtd driver, I have no objection to port my driver to
yours (I assume that there will be a common core, just like the nand
subsystem, and small drivers.)
And the last question probably:
I know that xD is very similar to nand, but due to things like the
above, maybe full mtd driver is really better.
There will be some code duplication, but on the other hand the driver
could follow the way windows driver works more closely, thus making it
more compatable with xD cards.
So if I or Alex write the full blown mtd driver, there will be no
objections because of code duplication?
Anyway, now I am going to stop talking and start coding (I did quite in
depth review of mtd and nand systems already)
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-12-01 16:41 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
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 [this message]
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=1259685711.18599.22.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=arnd@arndb.de \
--cc=joern@logfs.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