From: Alex Dubov <oakad@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: Pierre Ossman <drzeus@drzeus.cx>, Andrew Morton <akpm@osdl.org>
Subject: MemoryStick / Pro support
Date: Fri, 2 Nov 2007 06:23:48 -0700 (PDT) [thread overview]
Message-ID: <331462.7246.qm@web36703.mail.mud.yahoo.com> (raw)
After a much longer, than expected, time I managed to implement a support for MemoryStick (read-only currently, as there's still a subtle data corruption bug with writes) and MemoryStick Pro cards. The implementation follows the MMC driver model (there exist MSIO cards, but none are supported at the moment). The MS Pro support appears stable from what I can learn from user reports. Nevertheless, I've implemented a couple of diagnostics files in the "sys" filesystem, as well as low level format facility for legacy MS cards.
Currently only TI Flashmedia adapters are supported, but I'm working on a JMicron JMB38x adapter support and I know for sure that it'll be easy to support a Winbond 528 adapter, as I used its GPLed driver as a reference for a more generic implementation.
I would like to get an advice on the way to arrange the files in the kernel tree. My current idea is:
memstick.h -> include/linux
memstick.c -> drivers/memstick ("bus" support)
ms_block.c -> drivers/memstick (legacy MS storage support)
mspro_block.c -> drivers/memstick (MS Pro storage support)
tifm_ms.c -> drivers/memstick (TI Flashmedia low level driver)
I also wonder, where do I send the patches if nobody currently maintains this thing?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next reply other threads:[~2007-11-02 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 13:23 Alex Dubov [this message]
2007-11-07 6:15 ` Andrew Morton
2007-11-07 6:35 ` Pierre Ossman
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=331462.7246.qm@web36703.mail.mud.yahoo.com \
--to=oakad@yahoo.com \
--cc=akpm@osdl.org \
--cc=drzeus@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®