mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bryan Wu" <cooloney.lkml@gmail.com>
To: "Robin Getz" <rgetz@blackfin.uclinux.org>
Cc: "Pierre Ossman" <drzeus-mmc@drzeus.cx>,
	"Mike Frysinger" <vapier.adi@gmail.com>,
	"Cai, Cliff" <Cliff.Cai@analog.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] split MMC_CAP_4_BIT_DATA
Date: Sat, 12 Jan 2008 23:24:56 +0800	[thread overview]
Message-ID: <386072610801120724m77ac82d2h55374be25dbc5f9a@mail.gmail.com> (raw)
In-Reply-To: <200801120802.37259.rgetz@blackfin.uclinux.org>

On Jan 12, 2008 9:02 PM, Robin Getz <rgetz@blackfin.uclinux.org> wrote:
> On Fri 11 Jan 2008 12:52, Robin Getz pondered:
>
> > On Fri 11 Jan 2008 04:35, Pierre Ossman pondered:
> > > On Fri, 11 Jan 2008 04:08:53 -0500
> > > "Mike Frysinger" <vapier.adi@gmail.com> wrote:
> > >
> > > > On Jan 11, 2008 3:40 AM, Pierre Ossman <drzeus-mmc@drzeus.cx> wrote:
> > > > > 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.
> > > >
> > >
> > > More information. You have not provided any speculation as to why it
> > > doesn't work, or what you've done to figure it out.
> >
> > I have been trying to get the detailed information from the hardware
> > (silicon designer) guy about why he believes support for 4-bit MMC is
> > not there, but I have not heard back yet.
> >
> > As soon as I hear from them - and either understand why 4-bit MMC doesn't
> > work, or if the Blackfin docs are incorrect (either is OK outcome) - I will
> > let you know.
>
> According to the HW folks - it is exactly as Pierre indicated - in theory it
> should work, 4-bit MMC requires usage of different set of commands as
> compared to 4-bit SD, so it should be just software - although no one has
> tested it yet.
>

Vivi is helping us to do the test again, and she will fire a bug
tracker about this issue next week.
So we can debug it again.

> So I guess this is back on Bryan/Cliff to make work....
>
> Thanks for pushing back.
>

Yes, Thanks a lot Pierre.
-Bryan Wu

  reply	other threads:[~2008-01-12 15:25 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
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 [this message]
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=386072610801120724m77ac82d2h55374be25dbc5f9a@mail.gmail.com \
    --to=cooloney.lkml@gmail.com \
    --cc=Cliff.Cai@analog.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgetz@blackfin.uclinux.org \
    --cc=vapier.adi@gmail.com \
    /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®