On Mon, Jun 27, 2005 at 01:45:39PM +0100, Maciej W. Rozycki wrote: > Are you sure CONF_SC isn't set? I've checked that after we saw a crash in __flush_cache_all(). > That would be weird, it's one of the boot-mode settings so it would be > hard to get it wrong. What's printed upon bootstrap about caches? I don't have the console working yet, we just put enough prom_printf()s to work out, what was going wron. > (but it may break elsewhere). Have I heard: "serious brain damage" from > you? Well, I couldn't agree more... well, I haven't digged deep enough, to have a good opion on the whole issue. I'm also not sure, whether adding the blast_scache_nop() stuff is the way to go. I'd probably throw out the switch case over CPU types and use a single test before calling r4k_blast_scache(). Hmm, the probably cheapest version would be: if (r4k_blast_scache) r4k_blast_scache(); Problem solved. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessary a good idea. [ RFC1925, 2.3 ]
