Jorgen, You should not be using the atlas definition. Try the tangox one instead. With the flush_cache_page changes, FUSE works fine for me using 2.6.15 and Sigma's tango2 board. Mark Lin On Jan 7, 2008 10:52 AM, David Daney <ddaney@xxxxxxxxxx> wrote: > Jorgen Lundman wrote: > > > > Hello list, > > > > 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 defined: > > > > fuse: Unknown symbol flush_cache_page > > There are cache coherency issues on the 8634. You should be using the > vendor's very most recent kernels. For me they seem to have resolved > the cache issues. > > Also as noted by others, you need the exact kernel sources if you are > going to build working modules. > > David Daney > >