Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jorgen Lundman <lundman@lundman.net>
To: Mark Lin <lin.mark@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: MIPS 4KEc with 2.6.15
Date: Wed, 09 Jan 2008 08:00:26 +0900	[thread overview]
Message-ID: <4784008A.1020106@lundman.net> (raw)
In-Reply-To: <24f397b0801081402j24f7000cr841090ba5ab9bcc1@mail.gmail.com>

Yeha I would love to use tangox, but there is none with Linux, at least 
no tarball of the kernel I have found?

Where can I get tangox?

Lund


Mark Lin wrote:
> 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@avtrex.com> 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
>>
>>
> 

-- 
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-08 23:00 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
2008-01-08 22:02   ` Mark Lin
2008-01-08 23:00     ` Jorgen Lundman [this message]
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=4784008A.1020106@lundman.net \
    --to=lundman@lundman.net \
    --cc=lin.mark@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox