From: "mojtaba" <kernelppc@gmail.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Instruction OCM
Date: Mon, 19 May 2008 17:17:29 +0200 [thread overview]
Message-ID: <012401c8b9c3$74b947c0$5e2bd740$@com> (raw)
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Dear all,
I cannot run Linux when I have an instruction OCM in my design but, without
instruction OCM everything is fine. I tried to do some debugging. It seems
that the Linux memory management unit has a problem with that. After
entering the MMU initialization phase, it suddenly jumps to address
0x00000700 it get stuck there. Is there anybody who have tried a design with
instruction OCM? Do I need to do special configuration for the Linux kernel?
Regards,
Mojtaba
[-- Attachment #2: Type: text/html, Size: 2126 bytes --]
next reply other threads:[~2008-05-19 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 15:17 mojtaba [this message]
2008-05-19 16:58 ` Instruction OCM Stephen Neuendorffer
2008-05-20 8:31 ` mojtaba
2008-05-19 17:59 ` Koss, Mike (Mission Systems)
2008-05-19 18:53 ` Sergey Temerkhanov
2008-05-20 9:19 ` mojtaba
2008-05-20 11:11 ` Temerkhanov
2008-05-20 21:26 ` Stephen Neuendorffer
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='012401c8b9c3$74b947c0$5e2bd740$@com' \
--to=kernelppc@gmail.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).