From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Ian Molton <spyro@f2s.com>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Richard Purdie <rpurdie@rpsys.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MMC Driver RFC
Date: Fri, 14 Jan 2005 12:37:53 +0100 [thread overview]
Message-ID: <41E7AF11.6030005@drzeus.cx> (raw)
In-Reply-To: <41E5B177.4060307@f2s.com>
Nice too see that you're alive Ian ;)
I've been trying to send you some mail regarding your SD implementation
but I haven't received any replies. Perhaps they've gotten lost somewhere?
I've made my own SD patch using some of your work but also a lot of my
own stuff. I had some problems getting your patches to apply cleanly to
the current tree so I reimplemented it using your code as a template.
The patch can be found at:
http://projects.drzeus.cx/wbsd/sd.php
That page also contains the legal issues as I've understood them.
A summary of what I've done (relative your work):
* flags renamed to caps to better reflect what it does.
* SD_4_BITS changed to 4_BIT_DATA. Hopefully 4-bit mode in SD and MMC
will be compatible, at least on the driver level.
* HOST_ changed to MMC_ to conform with the rest of the macros.
* Added a function in the driver to test for SD read-only switch.
* Moved SD-specific commands to a separate section in the header so they
are more easily distinguished.
* SCR register is read from card and used when determining bus width.
* I've separated SD detection a bit.
* The mode (SD/MMC) of the host is stored. Since MMC uses a bus topology
and SD uses a star one it is useful to be able to see which mode the
controller is in.
I also couldn't find the reason for the ACMD flags you've added.
Application commands only differ in semantics, not format, so I couldn't
figure out why these where needed. Perhaps I'm missing something.
Ian Molton wrote:
>>
>> Unfortunately, such specs only cover MMC cards and not SD cards.
>
>
> ISTR seeing a SD card doc at some point
I have specs for SD cards from Sandisk and Toshiba. Both found on the
respective manufacturer's site using google. These have been the basis
for my work.
>
> Well I *know* I never saw the specs from the SD forum. I hacve never
> reverse engineered a SDHC core driver either (I have reverse engineered
> a chip driver but it contained no SD *protocol* information.
>
> as such my code should be 100% safe to commit to the kernel.
>
My code is based on the SD card specs I've found so it probably isn't as
safe.
Rgds
Pierre
next prev parent reply other threads:[~2005-01-14 11:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 21:10 MMC Driver RFC Richard Purdie
2005-01-12 21:43 ` Russell King
2005-01-12 22:07 ` Richard Purdie
2005-01-12 22:17 ` Russell King
2005-01-12 23:23 ` Ian Molton
2005-01-12 23:58 ` Richard Purdie
2005-01-14 11:37 ` Pierre Ossman [this message]
2005-01-14 14:55 ` Ian Molton
2005-01-16 12:22 ` Pierre Ossman
2005-01-16 13:19 ` Ian Molton
2005-01-16 19:43 ` Pierre Ossman
2005-01-16 23:17 ` Richard Purdie
2005-01-16 22:33 ` Alan Cox
2005-01-17 6:07 ` Pierre Ossman
2005-01-17 9:53 ` Richard Purdie
2005-01-17 11:59 ` 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=41E7AF11.6030005@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rpurdie@rpsys.net \
--cc=spyro@f2s.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