Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: joe seb <joe.seb8@gmail.com>
To: David VomLehn <dvomlehn@cisco.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Linux port failing on MIPS32 24Kc
Date: Thu, 9 Jul 2009 16:35:30 +0530	[thread overview]
Message-ID: <4f9abdc70907090405l4cd75251jbee5fbe123690e90@mail.gmail.com> (raw)
In-Reply-To: <20090708182906.GB31285@cuplxvomd02.corp.sa.net>

[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]

Hi David, Ralf,

This is a new FPGA based platform which has MIPS 24k core and we are trying
to bring up linux on this. MIPS cpu is running at 50MHz.

Other than ram, we have UART available and its a 8250 compatible UART which
is connected to one of the HW interrupt line. The MIPS timer interrupt is
connected to HW4 interrupt line.  So in our platform file, we provide the
irq dispatch function for these two irq lines. There is no driver which uses
the DMA.

We did another experiment where we replaced init application with a memory
test code which malloc and run incremental pattern test on the allocated
memory and we see sometimes this test is failing. The failure is happening
for a cache line, when we dump ddr corresponding to that cache line, we see
that, that particular cache line is not flushed to ddr and all the other
cache lines are fine. So, not sure any issue with flushing the write-back.
We checked the linux code and did not see any place dcache is flushed for a
particular line, its always for a page(blast_dcache functions). Is our
finding correct?

Regards,
Joe

On Wed, Jul 8, 2009 at 11:59 PM, David VomLehn <dvomlehn@cisco.com> wrote:

> On Wed, Jul 08, 2009 at 06:17:42PM +0530, joe seb wrote:
> > Hi,
> >
> > We made the following changes and tried,
> >
> > -> applied the patch given by you.
> > -> changed the PHYS_OFFSET to 0x10000000 to match our memory offset.
> > -> cache write back mode enabled
> >
> > Still we face the same problem. It crashes at different points when it
> > enters the user space. I have attached one of the logs.
> >
> > But in cache write through mode it works.
>
> Another thought: if it works with write through, but not write back, you
> may have a device driver that isn't flushing/invalidating cache
> appropriately
> before doing DMA. This is much more important on MIPS than many other
> processors.
>
> Is this a new platform or one that has been working for a while?
>
> David VomLehn
>

[-- Attachment #2: Type: text/html, Size: 2460 bytes --]

  reply	other threads:[~2009-07-09 11:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08  8:07 Linux port failing on MIPS32 24Kc joe seb
2009-07-08 10:37 ` Ralf Baechle
2009-07-08 12:47   ` joe seb
2009-07-08 18:29     ` David VomLehn
2009-07-09 11:05       ` joe seb [this message]
2009-07-12 10:39         ` Eugene Surovegin
2009-07-08 18:25   ` David VomLehn
2009-07-08 19:11     ` Maciej W. Rozycki
2009-07-13 14:47   ` joe seb

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=4f9abdc70907090405l4cd75251jbee5fbe123690e90@mail.gmail.com \
    --to=joe.seb8@gmail.com \
    --cc=dvomlehn@cisco.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@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