From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Risto Suominen <risto.suominen@gmail.com>
Cc: LinuxPPC-dev@ozlabs.org
Subject: Re: [PATCH 002/002] de2104x: support for systems lacking cache coherence
Date: Fri, 13 Feb 2009 14:25:57 +1100 [thread overview]
Message-ID: <1234495557.26036.0.camel@pasglop> (raw)
In-Reply-To: <46e1c7760902120322r11cffbdcgff330a242ca586fb@mail.gmail.com>
On Thu, 2009-02-12 at 13:22 +0200, Risto Suominen wrote:
> Here is a patch that helped me to get my de2104x NIC working on my
> PowerMac 5500. As an interesting side effect, it also made my mesh
> module crash.
>
> Background can be found here: http://www.spinics.net/lists/netdev/msg88488.html
I'll catch up with the discussion in netdev, I think the workaround
should be in the driver... Or if not, we can do special dma-ops just for
that device.
Just to make sure I didn't miss something, please send me a tarball
of /proc/device-tree of your machine.
Cheers,
Ben.
> Risto
>
> Allow setting NOT_COHERENT_CACHE explicitly.
>
> Signed-off-by: Risto Suominen <Risto.Suominen@gmail.com>
> ---
> The testing is done on kernel version 2.6.24.
>
> --- a/arch/powerpc/platforms/powermac/Kconfig.org 2008-01-25
> 00:58:37.000000000 +0200
> +++ b/arch/powerpc/platforms/powermac/Kconfig 2009-02-10
> 17:44:24.000000000 +0200
> @@ -18,4 +18,10 @@ config PPC_PMAC64
> select PPC_970_NAP
> default y
>
> -
> +config NOT_COHERENT_CACHE
> + bool "Incoherent cache"
> + default n
> + help
> + Setting this option may be necessary for avoiding cache-related
> + problems with some network cards on some platforms. An example is
> + 2104x and PowerMac 5500.
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2009-02-13 3:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 11:22 [PATCH 002/002] de2104x: support for systems lacking cache coherence Risto Suominen
2009-02-13 3:25 ` Benjamin Herrenschmidt [this message]
2009-02-13 3:26 ` Benjamin Herrenschmidt
2009-02-13 15:58 ` Risto Suominen
-- strict thread matches above, loose matches on Subject: below --
2009-02-07 21:30 Risto Suominen
2009-02-09 7:27 ` Fwd: " Risto Suominen
2009-02-09 7:45 ` David Miller
2009-02-09 8:22 ` Risto Suominen
2009-02-09 8:29 ` David Miller
2009-02-09 8:35 ` Risto Suominen
2009-02-09 16:58 ` Krzysztof Halasa
2009-02-09 19:22 ` Risto Suominen
2009-02-09 22:51 ` David Miller
2009-02-10 1:45 ` Krzysztof Halasa
2009-02-10 1:50 ` David Miller
2009-02-10 23:21 ` David Miller
2009-02-11 12:18 ` Risto Suominen
2009-02-11 12:31 ` Risto Suominen
2009-02-11 21:39 ` David Miller
2009-02-13 3:42 ` Benjamin Herrenschmidt
2009-02-10 1:01 ` Andrew Morton
2009-02-10 1:07 ` David Miller
2009-02-10 7:16 ` Risto Suominen
2009-02-10 7:16 ` Risto Suominen
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=1234495557.26036.0.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=LinuxPPC-dev@ozlabs.org \
--cc=risto.suominen@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 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.