On Mon, Jan 07, 2008 at 09:39:29AM +0900, Jorgen Lundman wrote:
> I have an embedded device running 2.6.15 kernel on a MIPS 4KEc 300MHz CPU.
> It was configured for Sigma's tango2 board, which I know nothing about, so
> I picked a mips-board by random, "atlas", and found I can produce working
> kernel module compiles.
> However, when I compiled FUSE kernel module, it behaves erratically in a
> way making the FUSE developer think I may have come across the cache
> coherency bug in arm and mips, fixed sometime around 2.6.17.
> Since I can not change the kernel that is running, I was looking for
> alternate solutions. FUSE itself has a work around, that calls
> flush_cache_page(), but I found that mips-board atlas does not have this
While you may not be able to change the kernel running on your board,
you should be building any modules against kernel headers of the exact
kernel running and configured for the platform and CPU you're using.
Mixing and matching different versions and configurations may work but
frequently it will fail silently.