From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Russell King" <rmk@arm.linux.org.uk>
Cc: linux-mips@linux-mips.org, drzeus@drzeus.cx
Subject: Re: Force MMC/SD to 512 byte block sizes
Date: Mon, 9 Jan 2006 10:49:36 -0700 [thread overview]
Message-ID: <20060109174936.GJ17575@cosmic.amd.com> (raw)
In-Reply-To: <20060106165930.GC16093@flint.arm.linux.org.uk>
On 06/01/06 16:59 +0000, Russell King wrote:
> On Fri, Jan 06, 2006 at 09:44:06AM -0700, Jordan Crouse wrote:
> > This patch is not specific to the AU1200 SD driver, but thats what
> > we used to debug and verify this, so thats why it is applied against
> > the linux-mips tree. Pierre, I'm sending this to you too, because I thought
> > you may be interested.
>
> NACK. Please wait until the next round of patches get merged and then
> revalidate this.
Ok - I saw your fixes. Looks good to me.
I'm still sticking to the (assumption|hypothesis|foolish fantasy) that
even cards that do not support partial block writes will still support
512 byte writes - mainly because I just don't see those ASICs in the
el-Cheapo card readers being capable of doing the advanced buffering
to convert 512 <-> 1024 or 2048, and hopefully one of these days I'll
find a card to prove that. Until then, I don't have a leg to stand on,
so I'll quietly hang back.
Jordan
--
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>
next prev parent reply other threads:[~2006-01-09 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 16:44 [PATCH] Force MMC/SD to 512 byte block sizes Jordan Crouse
2006-01-06 16:59 ` Russell King
2006-01-06 17:42 ` Jordan Crouse
2006-01-09 17:49 ` Jordan Crouse [this message]
2006-01-06 17:04 ` [PATCH] " Pierre Ossman
2006-01-06 17:50 ` Jordan Crouse
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=20060109174936.GJ17575@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=drzeus@drzeus.cx \
--cc=linux-mips@linux-mips.org \
--cc=rmk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.