[packages/kernel.git] / linux-2.4.19-PPC-agpgart_be.patch

--- linux-2.4.19/drivers/char/agp/agpgart_be.c.org	Fri Sep 13 10:26:51 2002
+++ linux-2.4.19/drivers/char/agp/agpgart_be.c	Fri Sep 13 10:26:29 2002
@@ -69,7 +69,7 @@
 {
 #if defined(__i386__) || defined(__x86_64__)
 	asm volatile ("wbinvd":::"memory");
-#elif defined(__alpha__) || defined(__ia64__) || defined(__sparc__)
+#elif defined(__alpha__) || defined(__ia64__) || defined(__sparc__) || defined(__powerpc__)
 	/* ??? I wonder if we'll really need to flush caches, or if the
 	   core logic can manage to keep the system coherent.  The ARM
 	   speaks only of using `cflush' to get things in memory in
Commit	Line	Data
cf8b3ace	1	--- linux-2.4.19/drivers/char/agp/agpgart_be.c.org Fri Sep 13 10:26:51 2002
	2	+++ linux-2.4.19/drivers/char/agp/agpgart_be.c Fri Sep 13 10:26:29 2002
	3	@@ -69,7 +69,7 @@
	4	{
	5	#if defined(__i386__) \|\| defined(__x86_64__)
	6	asm volatile ("wbinvd":::"memory");
	7	-#elif defined(__alpha__) \|\| defined(__ia64__) \|\| defined(__sparc__)
	8	+#elif defined(__alpha__) \|\| defined(__ia64__) \|\| defined(__sparc__) \|\| defined(__powerpc__)
	9	/* ??? I wonder if we'll really need to flush caches, or if the
	10	core logic can manage to keep the system coherent. The ARM
	11	speaks only of using `cflush' to get things in memory in