From: Eugene Surovegin <ebs@ebshome.net>
To: joe seb <joe.seb8@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Linux port failing on MIPS32 24Kc
Date: Sun, 12 Jul 2009 03:39:06 -0700 [thread overview]
Message-ID: <20090712103906.GA4019@gate.ebshome.net> (raw)
In-Reply-To: <4f9abdc70907090405l4cd75251jbee5fbe123690e90@mail.gmail.com>
On Thu, Jul 09, 2009 at 04:35:30PM +0530, joe seb wrote:
> 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.
One thing to check is that your FPGA guys used correct memory models
for caches, etc. We had very "funny" Liux failures when 24K FPGA
emulation build was using async memories for caches insted of sync
ones.
--
Eugene
next prev parent reply other threads:[~2009-07-12 10:39 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
2009-07-12 10:39 ` Eugene Surovegin [this message]
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=20090712103906.GA4019@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=joe.seb8@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