All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jorgen Lundman <lundman@lundman.net>
To: linux-mips@linux-mips.org
Subject: MIPS 4KEc with 2.6.15
Date: Mon, 07 Jan 2008 09:39:29 +0900	[thread overview]
Message-ID: <478174C1.2090708@lundman.net> (raw)


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

Should I try other mips-boards that may have this function call defined? 
Do I have other ways to avoid the cache coherence bug?

The /proc/ksyms is gone, so I do not think I am able to check what 
symbols their kernel has.

Lund


-- 
Jorgen Lundman       | <lundman@lundman.net>
Unix Administrator   | +81 (0)3 -5456-2687 ext 1017 (work)
Shibuya-ku, Tokyo    | +81 (0)90-5578-8500          (cell)
Japan                | +81 (0)3 -3375-1767          (home)

             reply	other threads:[~2008-01-07  0:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07  0:39 Jorgen Lundman [this message]
2008-01-07 12:08 ` MIPS 4KEc with 2.6.15 Ralf Baechle
2008-01-07 13:25   ` Jorgen Lundman
2008-01-07 15:52 ` David Daney
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=478174C1.2090708@lundman.net \
    --to=lundman@lundman.net \
    --cc=linux-mips@linux-mips.org \
    /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.