From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Nicolas Pitre <nico@cam.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] MMC updates
Date: Thu, 10 May 2007 15:58:26 +0200 [thread overview]
Message-ID: <46432502.4050901@drzeus.cx> (raw)
In-Reply-To: <4642B122.5070609@drzeus.cx>
Hi Nicolas,
You seem to be the source of this workaround, and also the maintainer of
PXA. So I guess this falls into your lap either way. Highlights from my
discussion with Russell:
Pierre Ossman wrote:
> Russell King wrote:
>
>> > Dug out from the ARM kautobuild...
>> >
>> > drivers/mmc/host/pxamci.c: In function 'pxamci_cmd_done':
>> > drivers/mmc/host/pxamci.c:236: error: 'MMC_ALL_SEND_CID' undeclared (first use in this function)
>> > drivers/mmc/host/pxamci.c:236: error: (Each undeclared identifier is reported only once
>> > drivers/mmc/host/pxamci.c:236: error: for each function it appears in.)
>> > drivers/mmc/host/pxamci.c:237: error: 'MMC_SEND_CSD' undeclared (first use in this function)
>> > drivers/mmc/host/pxamci.c:238: error: 'MMC_SEND_CID' undeclared (first use in this function)
>> >
>> >
>>
>
> What are opcode defines doing in the driver?
Pierre Ossman wrote:
> Russell King wrote:
>
>> See the comments immediately above and below its use.
>>
>> Welcome to buggy hardware.
>>
>>
>>
>
> I've read through the erratum, and to me it seems like the bug affects
> all long replies, not just these codes. So I think the code should be
> fixed to look at the response flag, not the opcode.
>
> Do you have hardware so that you can test such a change?
>
>
I guess the same question goes to you. :)
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-05-10 14:01 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 15:22 [GIT PULL] MMC updates Pierre Ossman
2007-05-05 4:24 ` Pierre Ossman
2007-05-05 4:45 ` Linus Torvalds
2007-05-09 18:56 ` Russell King
2007-05-09 19:06 ` Pierre Ossman
2007-05-09 22:12 ` Russell King
2007-05-10 5:44 ` Pierre Ossman
2007-05-10 7:51 ` Russell King
2007-05-10 13:58 ` Pierre Ossman [this message]
2007-05-10 14:52 ` Nicolas Pitre
2007-05-12 15:38 ` Nicolas Pitre
2007-05-12 16:12 ` Pierre Ossman
2007-05-12 16:22 ` Russell King
2007-05-12 17:55 ` Nicolas Pitre
2007-05-13 3:13 ` [PATCH] fix PXA27x MMC workaround for bad CRC with 136 bit response Nicolas Pitre
2007-05-13 15:59 ` Pierre Ossman
-- strict thread matches above, loose matches on Subject: below --
2008-04-19 7:28 [GIT PULL] MMC updates Pierre Ossman
2008-02-09 9:50 Pierre Ossman
2007-12-12 19:12 Pierre Ossman
2007-12-18 7:57 ` Pierre Ossman
2007-11-21 17:56 Pierre Ossman
2007-10-17 20:44 Pierre Ossman
2007-10-17 20:48 ` Dan Williams
2007-10-10 19:21 Pierre Ossman
2007-10-12 5:30 ` Linus Torvalds
2007-10-12 5:45 ` Pierre Ossman
2007-10-12 12:18 ` Kay Sievers
2007-10-12 13:53 ` Pierre Ossman
2007-10-12 19:55 ` Pierre Ossman
2007-10-12 20:05 ` Nicolas Pitre
2007-10-12 20:35 ` Pierre Ossman
2007-10-12 21:00 ` Pierre Ossman
2007-10-13 5:29 ` Randy Dunlap
2007-10-13 7:03 ` Pierre Ossman
2007-09-11 15:26 Pierre Ossman
2007-08-23 5:18 Pierre Ossman
2007-08-09 14:34 Pierre Ossman
2007-07-26 13:15 Pierre Ossman
2007-07-21 0:36 Pierre Ossman
2007-07-10 20:43 Pierre Ossman
2007-06-13 17:24 Pierre Ossman
2007-06-08 8:09 Pierre Ossman
2007-05-24 5:46 Pierre Ossman
2007-05-14 16:55 Pierre Ossman
2007-05-08 20:45 Pierre Ossman
2007-05-09 5:55 ` Pierre Ossman
2007-05-09 6:03 ` Nick Piggin
2007-05-09 6:27 ` Pierre Ossman
2007-05-09 6:35 ` Nick Piggin
2007-05-09 7:51 ` Pierre Ossman
2007-05-09 8:05 ` Nick Piggin
2007-05-09 9:11 ` Stefan Richter
2007-05-09 15:44 ` Pierre Ossman
2007-02-11 15:33 Pierre Ossman
2007-02-04 20:11 Pierre Ossman
2007-01-15 5:46 Pierre Ossman
2007-01-04 12:49 Pierre Ossman
2007-01-10 19:51 ` Pierre Ossman
2006-12-11 11:45 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=46432502.4050901@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.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 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.