public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Matt Reimer <mattjreimer@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: 2GB MMC/SD cards
Date: Wed, 7 Jun 2006 17:58:37 +0100	[thread overview]
Message-ID: <20060607165837.GE13165@flint.arm.linux.org.uk> (raw)
In-Reply-To: <44869794.9080906@drzeus.cx>

On Wed, Jun 07, 2006 at 11:08:36AM +0200, Pierre Ossman wrote:
> New information. Version 4.2 of the MMC spec changes the wording to this:
> 
> * WRITE_BL_LEN
> Block length for write operations. See READ_BL_LEN for field coding.
> Note that the support for 512B write access is mandatory for all cards.
> 
> Similar wording for READ_BL_LEN, but that isn't of interest to us.

I wonder if all 2GB cards are >= v4.2 of the spec?  If so, we could
do what would appear correct to both the spec and reality, and select
512 byte blocksizes irrespective if they conform to v4.2 or later.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-06-07 16:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-29 14:00 2GB MMC/SD cards Pierre Ossman
2006-06-03 14:15 ` 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 [this message]
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=20060607165837.GE13165@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattjreimer@gmail.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