public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Pierre Ossman <drzeus-list@drzeus.cx>,
	linux-kernel@vger.kernel.org, rmk+lkml@arm.linux.org.uk
Cc: Jordan Crouse <jordan.crouse@amd.com>
Subject: Re: 2GB MMC/SD cards
Date: Tue, 06 Jun 2006 08:17:00 +0100	[thread overview]
Message-ID: <1149578221.5520.4.camel@localhost.localdomain> (raw)
In-Reply-To: <20060605222908.GC4996@cosmic.amd.com>

On Mon, 2006-06-05 at 16:29 -0600, Jordan Crouse wrote:
> I'm not 100% sure what the community stance is on using the simplified specs.
> I do believe the answer lies definitively within, but I'll refrain from
> quoting it to avoid any legal complaints.  For the longest time, my gut
> feeling has been that 512 byte writes were always accepted - but since all of
> our 2G and 4G cards support WRITE_BL_PARTIAL, we haven't had a chance to 
> prove the argument one way or the other.
> 
> We first heard about very large card issues from one of our customers, and
> we haven't heard any more problems since we gave them a patch to force the
> sector size on all SD/MMC cards to 512 bytes.  Thats just anecdotal evidence,
> but it is food for thought.

For what its worth this is the feeling I get from the users of the
Zaurus kernels as well. For the PXA driver, there is the added
complication that it doesn't support block sizes > 1023 but I've had no
complaints since I limited it to 512.

Richard


  reply	other threads:[~2006-06-06  7:21 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 [this message]
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=1149578221.5520.4.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=drzeus-list@drzeus.cx \
    --cc=jordan.crouse@amd.com \
    --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