Message ID | 46e1c7760902110418n276de9b2xa2169839b9e25dc0@mail.gmail.com |
---|---|
State | Not Applicable, archived |
Delegated to: | David Miller |
Headers | show |
As an interesting side effect, the patch caused my mesh module to stop working. It crashes. Risto -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Risto Suominen <risto.suominen@gmail.com> Date: Wed, 11 Feb 2009 14:31:43 +0200 > As an interesting side effect, the patch caused my mesh module to stop > working. It crashes. I think you need to take this discussion to linuxppc-dev at this point. Nobody amongst the networking developers can say whether your NOT_COHERENT_CACHE change is a valid or desirable way to solve the problem, nor what side effects it might have. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
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.