From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Alex Dubov <oakad@yahoo.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Legacy memstick support + FTL questions
Date: Tue, 26 Jan 2010 23:43:57 +0200 [thread overview]
Message-ID: <1264542237.15306.14.camel@maxim-laptop> (raw)
Hi,
Since my xD/SmartMedia support is done (will send small update
tomorrow), I am switching focus to MemStick conteroller.
Since I am a perfectionist (at lest still am...) I want to have support
for both MemStick and MemStick pro.
Alex, I see that your PRO support is in kernel, not legacy support
isn't. Why?
Legacy MemSticks also are barebone like XD and thus need an FTL.
However, they don't have NAND interface.
My current goal is to take your ms_block.c, understand it, port to
latest kernel, and attempt a merge.
Its also possible to do the same I did with XD, write an MTD driver and
another FTL.
Since legacy memsticks are rare. I would like not to write mtd driver.
Also, any information, about memsticks is welcome. It would help me a
lot.
I assume that both Memstick, and Memstick Duo are similiar on hardware
level, (both bare flash).
Same for, Memstick PRO and MemStick PRO Duo.
Best regards,
Maxim Levitsky
next reply other threads:[~2010-01-26 21:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 21:43 Maxim Levitsky [this message]
2010-01-27 2:16 ` Legacy memstick support + FTL questions Alex Dubov
[not found] <1266091737.30330.16.camel@maxim-laptop>
2010-02-14 15:06 ` Alex Dubov
2010-02-14 19:03 ` Maxim Levitsky
2010-02-16 14:15 ` Alex Dubov
2010-02-16 23:49 ` Maxim Levitsky
2010-02-17 2:26 ` Alex Dubov
2010-02-17 23:39 ` Maxim Levitsky
2010-02-21 22:42 ` Maxim Levitsky
2010-02-22 14:04 ` Alex Dubov
2010-02-22 23:11 ` Maxim Levitsky
2010-02-23 9:01 ` Alex Dubov
2010-02-24 1:10 ` Maxim Levitsky
2010-02-24 2:20 ` 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=1264542237.15306.14.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=linux-mtd@lists.infradead.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