From: Johannes Berg <johannes@sipsolutions.net>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
linuxppc-dev@ozlabs.org, sam@ravnborg.org,
David Miller <davem@davemloft.net>,
Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: [PATCH] powerpc swsusp: make altivec code depend on CONFIG_ALTIVEC
Date: Wed, 07 Nov 2007 13:59:44 +0100 [thread overview]
Message-ID: <1194440384.4470.10.camel@johannes.berg> (raw)
In-Reply-To: <1194428323.4055.3.camel@johannes.berg>
This makes the altivec code in swsusp_32.S depend on CONFIG_ALTIVEC to
avoid build failures for systems that don't have altivec. I'm not sure
whether the code will actually work for other systems, but it was merged
for just ppc32 rather than powermac a very long time ago.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
---
--- everything.orig/arch/powerpc/kernel/swsusp_32.S 2007-11-07 13:27:12.441517359 +0100
+++ everything/arch/powerpc/kernel/swsusp_32.S 2007-11-07 13:27:25.251519911 +0100
@@ -133,10 +133,12 @@ _GLOBAL(swsusp_arch_suspend)
/* Resume code */
_GLOBAL(swsusp_arch_resume)
+#ifdef CONFIG_ALTIVEC
/* Stop pending alitvec streams and memory accesses */
BEGIN_FTR_SECTION
DSSALL
END_FTR_SECTION_IFSET(CPU_FTR_ALTIVEC)
+#endif
sync
/* Disable MSR:DR to make sure we don't take a TLB or
prev parent reply other threads:[~2007-11-07 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 10:34 2.6.24-rc1-git15 Kernel build fails on powerpc - Unrecognized opcode: `dssall' Kamalesh Babulal
2007-11-06 10:46 ` Balbir Singh
2007-11-06 10:54 ` Johannes Berg
2007-11-06 11:10 ` David Miller
2007-11-06 11:28 ` Kamalesh Babulal
2007-11-06 13:39 ` Balbir Singh
2007-11-06 15:44 ` Andy Whitcroft
2007-11-07 9:38 ` Johannes Berg
2007-11-07 12:49 ` Johannes Berg
2007-11-07 12:59 ` Johannes Berg [this message]
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=1194440384.4470.10.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=balbir@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sam@ravnborg.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 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).