Kars de Jong <[EMAIL PROTECTED]> writes: |> I'll dig up my patch to see if I can get it working again, but I remember it |> being a bit kludgy because we have no equivalent of ppc_flush_icache() on |> m68k. There is __cache_flush() in libgcc (or was it libc?) but its API is |> quite different. And instead of flushing a cache line (?) for each relocated |> address (which is what PPC seems to do) we might be better off flushing the |> cache for the entire relocated section after it's been relocated (I think |> __cache_flush() wants a start address and a length argument). |> Or maybe we should use the m68k cacheflush syscall() instead. |> |> Anyone? Andreas? What's better?
The __cache_flush function in libgcc _is_ essentially the cacheflush syscall. Note that glibc has cacheflush too, so just use that. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE GmbH, Deutschherrnstr. 15-19, D-90429 N�rnberg Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
