On Thu, 25 Aug 2005, Al Viro wrote:
> On Thu, Aug 25, 2005 at 09:59:05AM -0400, Sam Creasey wrote: > > > I have been a little out of it for a while on the sun3 stuffs, I'll admit > > (cursed day job), but I really, really intend to get recent 2.6 running > > again. Knowing that the rest of m68k is at least compiling is a good > > start point. Still, I'm going with Geert, and I'm not sure where the > > compile regressions would have come from (outside of the video/serial > > drivers, which don't compile in m68k CVS either). > > > > What compile failures are you seeing? > > After looking at that for a while... It's the second hairball in there ;-) > flush_icache_range()/flush_icache_user_range() stuff, with all related > fun. Note that mainline has flush_ichace_range() in memory.c, which is > not picked by sun3. Huh, my last compiling 2.6 sun3 tree ((old) m68k CVS) has those in arch/m68k/mm/cache.c, which sun3 did use. Ok, sounds like I need to make sure those are broken out sanely. I'm pretty sure memory.c is a bad place for that, since (as you observed), it's motorola-mmu only code (or, at least, was...) I'm considerably less scared now. :) -- Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
