From: Pierre Ossman <drzeus-list@drzeus.cx>
To: "Khasim, Syed" <x0khasim@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Plea for MMC spec owners
Date: Tue, 06 Jun 2006 00:40:01 +0200 [thread overview]
Message-ID: <4484B2C1.6020100@drzeus.cx> (raw)
In-Reply-To: <77C7F7CB1230A74A9D19C0C111E6EDBE41CF48@DLEE09.ent.ti.com>
Khasim, Syed wrote:
> Hi Pierre,
>
> Regarding 2GB, the MMC specification doesn't state any thing clearly as
> the SD spec does.
>
>
That's too bad as I was hoping we could avoid guesswork. :-/
> As per my understanding, MMC (of all sizes) by default should be set to
> operate in 512B (mandatory). This is true for both read and write. With
> this default setup, I feel MMC card (<=2GB) should work as is with BLEN
> set to 512.
>
That is my feeling as well. But it would have been nice to back it up
with an official spec.
> However, if the size of MMC is greater than 2GB then it switches to
> sector access mode (<=2GB operates in byte access) and we are supposed
> to read from EXT_CSD register for getting the density of card. I was
> wondering if for some reason on some of the cards it's switching to this
> mode and therefore it's not consistent across all the 2GB MMCs.
>
>
This voodoo you speak of is rather unknown to us since we lack a real
MMC4 spec. ;-)
Rgds
Pierre
next prev parent reply other threads:[~2006-06-05 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 22:19 Plea for MMC spec owners Khasim, Syed
2006-06-05 22:40 ` Pierre Ossman [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 14:44 Khasim, Syed
2006-06-06 21:39 ` Pierre Ossman
2006-06-06 23:49 ` Kyungmin Park
2006-06-07 9:04 ` Pierre Ossman
2006-06-07 10:10 ` Pierre Ossman
2006-06-16 11:04 ` Pierre Ossman
2006-06-05 15:34 Khasim, Syed
2006-06-05 14:36 Khasim, Syed
2006-06-05 15:57 ` Pierre Ossman
2006-06-05 8:52 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=4484B2C1.6020100@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-omap-open-source@linux.omap.com \
--cc=x0khasim@ti.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