From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: 2GB MMC/SD cards
Date: Mon, 29 May 2006 16:00:26 +0200 [thread overview]
Message-ID: <447AFE7A.3070401@drzeus.cx> (raw)
Hi Russell!
Not sure when you'll be back from your trip, but I'll leave this hanging
in your inbox until then. :)
I've been getting several complaints about the issue with sector sizes
and large MMC/SD cards. I seem to recall we discussed this earlier, but
I cannot find those mail and I don't remember our conclusions.
I do, however, have the following in both the SD and MMC card specs I
have (both sandisk though):
WRITE_BL_PARTIAL — defines whether partial block sizes can be used
in block write commands.
Table 3-25
WRITE_BL_PARTIAL Definition
0 Only the WRITE_BL_LEN block size, and its partial
derivatives in
resolution of units of 512 blocks, can be used for
block oriented data
write.
1 Smaller blocks can be used as well. The minimum
block size is one
byte.
So perhaps we should remove all the funky logic that's in mmc_block.c
right now and just always select a block size of 512 bytes? People have
been reporting that their Palms, cameras and USB readers will not accept
anything else.
Rgds
Pierre
next reply other threads:[~2006-05-29 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 14:00 Pierre Ossman [this message]
2006-06-03 14:15 ` 2GB MMC/SD cards Russell King
2006-06-03 15:02 ` Russell King
2006-06-03 18:40 ` Matt Reimer
2006-06-03 21:13 ` Pierre Ossman
2006-06-05 22:29 ` Jordan Crouse
2006-06-06 7:17 ` Richard Purdie
2006-06-05 22:52 ` Pierre Ossman
2006-06-07 9:08 ` Pierre Ossman
2006-06-07 16:58 ` Russell King
2006-06-07 20:36 ` Pierre Ossman
2006-06-08 23:01 ` Pierre Ossman
2006-06-22 15:08 ` Marcin Juszkiewicz
2006-08-13 10:14 ` Daniel Drake
2006-08-22 15:19 ` Juha Yrjola
2006-08-22 17:00 ` Jeff Chua
2006-08-23 18:28 ` Pierre Ossman
2006-08-25 9:07 ` Russell King
2006-06-03 21:11 ` 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=447AFE7A.3070401@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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