public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus@drzeus.cx>
To: Madhusudhan c <cr.madhusudhan@gmail.com>
Cc: linux-kernel@vger.kernel.org, philipl@overt.org
Subject: Re: MMCv4 support (8-bit support missing)
Date: Thu, 19 Apr 2007 18:25:18 +0200	[thread overview]
Message-ID: <462797EE.2050808@drzeus.cx> (raw)
In-Reply-To: <ff1613620704190704n2cf37c9dv43536bb8fc0d4c79@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

Madhusudhan c wrote:
> 
> The bus test procedure from this patch can be adopted to the MMCv4
> support in the MMC core with small changes to do bus testing procedure
> only if the host sets the capability to support 8-bit. That way we
> dont break the legacy code. What do you think?
> 

Until 8-bit SD shows up, at which point things go to hell again.

You need to present a valid case for why we need this bus testing stuff. The
spec never requires it, and neither does any cards. So this is just crud that we
know causes problems and doesn't give us anything back.

Rgds
Pierre



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]

  reply	other threads:[~2007-04-19 16:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17  6:59 MMCv4 support (8-bit support missing) Madhusudhan c
2007-04-17 15:15 ` Philip Langdale
2007-04-18  8:46 ` Pierre Ossman
2007-04-18 11:53   ` Madhusudhan c
2007-04-18 14:21     ` Pierre Ossman
2007-04-19 14:04       ` Madhusudhan c
2007-04-19 16:25         ` Pierre Ossman [this message]
2007-04-20 11:21           ` Madhusudhan c
2007-04-20 16:12             ` Philip Langdale
2007-04-24  5:03             ` Pierre Ossman
2007-04-26  3:34               ` Madhusudhan c
2007-04-27  6:20                 ` 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=462797EE.2050808@drzeus.cx \
    --to=drzeus@drzeus.cx \
    --cc=cr.madhusudhan@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipl@overt.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