From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <liml@rtr.ca>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Zang Roy-r61911 <tie-fei.zang@freescale.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Alexandre.Bounine@tundra.com,
Yang Xin-Xin-r48390 <Xin-Xin.Yang@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>
Subject: Re: [PATCH/2.6.17-rc4 10/10] bugs fix for marvell SATA on powerp c pl atform
Date: Thu, 18 May 2006 17:07:35 -0400 [thread overview]
Message-ID: <446CE217.2070703@pobox.com> (raw)
In-Reply-To: <446CDE26.8090504@rtr.ca>
Mark Lord wrote:
> Jeff Garzik wrote:
>> Benjamin Herrenschmidt wrote:
>>> On Thu, 2006-05-18 at 12:03 +0800, Zang Roy-r61911 wrote:
> ..
>>>> @@ -1567,13 +1570,18 @@ static void mv5_read_preamp(struct mv_ho
>>>> static void mv5_enable_leds(struct mv_host_priv *hpriv, void __iomem
>>> *mmio)
>>>> {
>>>> u32 tmp;
>>>> -
>>>> +#ifndef CONFIG_PPC
>>>> writel(0, mmio + MV_GPIO_PORT_CTL);
>>>> +#endif
>>>
>>> You'll have to do better here too... I don't wee why when compiled on
>>> PPC, this driver should "magically" not clear those bits... At the very
>>> least, you should test the machine type if you want to do something
>>> specific to your platform, but first, you'll have to convince Jeff why
>>> this change has to be done in the first place and if there is a better
>>> way to handle it.
>>
>> Correct... it does seem some bugs were found, but #ifdef powerpc is
>> certainly out of the question. We want the driver to work without
>> ifdefs on all platforms.
>
> Yup. I have a powerpc platform here with PCI-X, and a PCI-X Marvell card
> to try in it. So I'll pick up these changes and try to integrate them a
> little more nicely in my internal updated driver, and then pass it on to
When will this happen? I'm getting worried that useful stuff is
disappearing into the Mark Lord ether, with no changes appearing on the
other side. Haven't seen patches from you in weeks.
I'm happy that you have an updated internal driver, but that helps no
one else.
Jeff
next prev parent reply other threads:[~2006-05-18 21:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 4:03 [PATCH/2.6.17-rc4 10/10] bugs fix for marvell SATA on powerp c pl atform Zang Roy-r61911
2006-05-18 7:02 ` Benjamin Herrenschmidt
2006-05-18 15:26 ` Jeff Garzik
2006-05-18 20:50 ` Mark Lord
2006-05-18 21:07 ` Jeff Garzik [this message]
2006-05-18 21:37 ` Mark Lord
2006-05-26 8:39 ` Sven Luther
2006-05-26 8:56 ` Jeff Garzik
2006-05-26 8:58 ` Sven Luther
2006-05-26 11:41 ` Mark Lord
2006-05-26 11:42 ` Sven Luther
2006-05-26 13:19 ` Mark Lord
2006-05-26 14:15 ` Sven Luther
2006-05-26 15:47 ` Mark Lord
2006-05-26 16:01 ` Sven Luther
2006-05-26 16:15 ` Sven Luther
2006-05-26 16:21 ` Mark Lord
2006-05-26 16:25 ` Sven Luther
2006-05-18 12:01 ` Ric Wheeler
-- strict thread matches above, loose matches on Subject: below --
2006-05-19 4:06 Zang Roy-r61911
2006-05-19 4:12 Zang Roy-r61911
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=446CE217.2070703@pobox.com \
--to=jgarzik@pobox.com \
--cc=Alexandre.Bounine@tundra.com \
--cc=Xin-Xin.Yang@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=tie-fei.zang@freescale.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;
as well as URLs for NNTP newsgroup(s).