All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Jorgen Lundman <lundman@lundman.net>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS 4KEc with 2.6.15
Date: Mon, 07 Jan 2008 07:52:47 -0800	[thread overview]
Message-ID: <47824ACF.7050003@avtrex.com> (raw)
In-Reply-To: <478174C1.2090708@lundman.net>

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

  parent reply	other threads:[~2008-01-07 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07  0:39 MIPS 4KEc with 2.6.15 Jorgen Lundman
2008-01-07 12:08 ` Ralf Baechle
2008-01-07 13:25   ` Jorgen Lundman
2008-01-07 15:52 ` David Daney [this message]
2008-01-08 22:02   ` Mark Lin
2008-01-08 23:00     ` Jorgen Lundman
2008-01-09 21:29       ` David Daney
2008-01-10  4:06         ` Jorgen Lundman
2008-01-10 16:36           ` Martin Michlmayr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47824ACF.7050003@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=lundman@lundman.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.