From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Pierre Ossman" <drzeus-mmc@drzeus.cx>
Cc: "Bryan Wu" <cooloney.lkml@gmail.com>,
"Cai, Cliff" <Cliff.Cai@analog.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] split MMC_CAP_4_BIT_DATA
Date: Fri, 11 Jan 2008 04:08:53 -0500 [thread overview]
Message-ID: <8bd0f97a0801110108l66ab2bcdjb1323573445473f@mail.gmail.com> (raw)
In-Reply-To: <20080111094036.4c683791@poseidon.drzeus.cx>
On Jan 11, 2008 3:40 AM, Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> "Bryan Wu" <cooloney.lkml@gmail.com> wrote:
> > We were told this is an hardware design issue, so please help us to
> > workaround it in software side with Mike's patch.
>
> So it's far more probable that you've misdiagnosed your error than this being the actual problem.
the guys who design the silicon are telling us it doesnt work. our
tests show it not working. i'm not sure what else you want here.
> The fact that 4-bit MMC support has been present for some time and you're only now seeing a problem further supports that.
not in the least actually. we just started developing the driver. it
has seen no real world use. we've been testing things internally to
make sure the setup is sane. 4-bit MMC is coming up as not working.
-mike
next prev parent reply other threads:[~2008-01-11 9:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 18:29 Mike Frysinger
2008-01-08 19:21 ` Pierre Ossman
2008-01-08 19:40 ` Mike Frysinger
2008-01-08 20:49 ` Pierre Ossman
2008-01-08 21:44 ` Mike Frysinger
2008-01-09 7:21 ` Pierre Ossman
2008-01-09 2:32 ` Bryan Wu
2008-01-09 3:21 ` Cai, Cliff
2008-01-09 7:23 ` Pierre Ossman
2008-01-09 16:45 ` Bryan Wu
2008-01-10 8:54 ` Pierre Ossman
2008-01-10 9:22 ` Bryan Wu
2008-01-10 11:57 ` Pierre Ossman
2008-01-11 6:17 ` Bryan Wu
2008-01-11 6:25 ` Mike Frysinger
2008-01-11 8:40 ` Pierre Ossman
2008-01-11 9:08 ` Mike Frysinger [this message]
2008-01-11 9:35 ` Pierre Ossman
2008-01-11 9:47 ` Mike Frysinger
2008-01-11 10:05 ` Pierre Ossman
2008-01-11 10:22 ` Bryan Wu
2008-01-11 11:18 ` Pierre Ossman
2008-01-11 17:52 ` Robin Getz
2008-01-12 13:02 ` Robin Getz
2008-01-12 15:24 ` Bryan Wu
2008-01-12 15:39 ` Pierre Ossman
2008-01-09 4:23 ` Bryan Wu
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=8bd0f97a0801110108l66ab2bcdjb1323573445473f@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=Cliff.Cai@analog.com \
--cc=cooloney.lkml@gmail.com \
--cc=drzeus-mmc@drzeus.cx \
--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
all inboxes | Powered by JetHome®