From: Vincent Katz <vincent.katz@laposte.net>
To: jhartmann@precisioninsight.com
Cc: paulus@samba.org, linuxppc-dev@lists.linuxppc.org, paulus@au.ibm.com
Subject: AGP : ATI128,powerpc
Date: 14 Nov 2001 21:52:42 +0100 [thread overview]
Message-ID: <1005771164.6732.19.camel@avalon> (raw)
Hi,
Linux version : 2.4.14
File with a supposed probleme : linux/drivers/char/agp/agpgart_be.c
I have a powerpc with an ati128 AGP.
When i compile the kernel i have this error : error "Please define
flush_cache."
this error come from the function flush_cache in agpgart_be.c where
definition for powerpc are not setting . Why ?
> static inline void flush_cache(void)
>{
>#if defined(__i386__) || defined(__x86_64__)
> asm volatile ("wbinvd":::"memory");
>#elif defined(__alpha__) || defined(__ia64__) || defined(__sparc__)
> /* ??? 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
> preparation for power failure.
>
> If we do need to call `cflush', we'll need a target page,
> as we can only flush one page at a time.
>
> Ditto for IA-64. --davidm 00/08/07 */
> mb();
>#else
>#error "Please define flush_cache."
>#endif
>}
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-11-14 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-14 20:52 Vincent Katz [this message]
2001-11-14 21:09 ` AGP : ATI128,powerpc Kevin B. Hendricks
2001-11-14 21:23 ` Jörn Nettingsmeier
2001-11-14 21:38 ` Benjamin Herrenschmidt
2001-11-14 21:26 ` Benjamin Herrenschmidt
2001-11-15 14:12 ` Vincent Katz
2001-11-15 14:45 ` Benjamin Herrenschmidt
2001-11-15 17:21 ` Vincent Katz
[not found] <20011114230308.04E9D18077@haven.ozlabs.ibm.com>
2001-11-14 18:11 ` Paul Mackerras
2001-11-15 9:20 ` Jörn Nettingsmeier
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=1005771164.6732.19.camel@avalon \
--to=vincent.katz@laposte.net \
--cc=jhartmann@precisioninsight.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@au.ibm.com \
--cc=paulus@samba.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).