From: Philip Langdale <philipl@overt.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: linux-kernel@vger.kernel.org, John Gilmore <gnu@toad.com>
Subject: Re: [PATCH 2.6.19] mmc: Add support for SDHC cards
Date: Mon, 01 Jan 2007 07:20:21 -0800 [thread overview]
Message-ID: <459926B5.60505@overt.org> (raw)
In-Reply-To: <4597A327.8030408@drzeus.cx>
I will post the updated diff as a separate follow up.
Pierre Ossman wrote:
>
> When you have a commit message larger than the patch, you know there is
> something wrong. ;)
>
> Please skip the part about MMC at least.
Heh. I forget that you don't want to manually alter the email. Will do.
>
> Actually, the way the spec describes version 2.0 of the CSD leaves my
> stomach a bit upset. I think we will find cards that put bogus values in
> the fields, expecting most hosts to use the well defined values. So I'd
> prefer a switch statement here, where csd_struct == 1 results in hard
> coded values for many fields.
I'm less pessimistic than you about this, but I have no problems with
hard-coding.
>> + cmd.opcode = SD_SEND_IF_COND;
>>
>
> Put this in mmc_setup() with the rest of the initialisation. Hiding in
> here just confuses things.
Done. I thought we needed it before both SD_APP_SEND_OP_COND calls but
it's only needed before the second one so I've moved it inline into
mmc_setup.
> Also, please add a comment about why you manipulate the ocr.
Done.
>
> Wrong. R7 is defined as MMC_RSP_PRESENT|MMC_RSP_CRC|MMC_RSP_OPCODE.
>
> (So is R6 btw, wonder why that is...)
Ah - I knew they were both the same so I made R7 match R6. :-)
I've added OPCODE to both.
Thanks,
--phil
next prev parent reply other threads:[~2007-01-01 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 18:24 [PATCH 2.6.19] mmc: Add support for SDHC cards Philip Langdale
2006-12-22 18:50 ` Philip Langdale
2006-12-28 13:36 ` Pavel Machek
2007-01-01 17:49 ` Pierre Ossman
2006-12-31 11:46 ` Pierre Ossman
2007-01-01 15:20 ` Philip Langdale [this message]
2007-01-03 21:05 ` 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=459926B5.60505@overt.org \
--to=philipl@overt.org \
--cc=drzeus-list@drzeus.cx \
--cc=gnu@toad.com \
--cc=linux-kernel@vger.kernel.org \
/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