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: Mon, 05 Jun 2006 17:57:25 +0200 [thread overview]
Message-ID: <44845465.9020505@drzeus.cx> (raw)
In-Reply-To: <77C7F7CB1230A74A9D19C0C111E6EDBE41C7BA@DLEE09.ent.ti.com>
Khasim, Syed wrote:
> Hi Pierre,
>
> A quick search to write_bl_partial and read_bl_partial in MMC spec gave
> the following lines.
>
Thanks. Unfortunately, it wasn't the response I was hoping for as it
isn't consistent with what we've been seeing with other MMC and SD readers.
> I think you already have this pointer to SD spec, might be helpful to
> others.
>
> http://www.sdcard.org/sd_memorycard/Simplified%20Physical%20Layer%20Spec
> ification.PDF
>
>
I have to admit, I hadn't looked that closely at that spec as it didn't
cover the protocol properly. But it actually said something about this
issue:
4.3.2 2GByte Card
To make 2GByte card, the Maximum Block Length (READ_BL_LEN=WRITE_BL_LEN)
shall be set to
1024 bytes. But Block Length set by CMD16 shall be up to 512 bytes to
keep consistency with 512
bytes Maximum Block Length cards (Less than and equal 2GByte cards).
Could you have a second look in the MMC spec and see if there are
similar provisions?
Rgds
Pierre
next prev parent reply other threads:[~2006-06-05 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 14:36 Plea for MMC spec owners Khasim, Syed
2006-06-05 15:57 ` 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 22:19 Khasim, Syed
2006-06-05 22:40 ` Pierre Ossman
2006-06-05 15:34 Khasim, Syed
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=44845465.9020505@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