From: Scott Wood <oss@buserror.net>
To: Giuseppe Lippolis <giu.lippolis@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: AW: problem with cuImage.mpc834x_mds image
Date: Fri, 24 Mar 2017 17:10:05 -0500 [thread overview]
Message-ID: <1490393405.2944.53.camel@buserror.net> (raw)
In-Reply-To: <006101d2a4e5$82bebcd0$883c3670$@gmail.com>
On Fri, 2017-03-24 at 22:27 +0100, Giuseppe Lippolis wrote:
> >
> Therefore the code crash during the call in:
> bl setup_common_caches
>
>
> I'm using the iomega_150d based on the MPC8347.
>
> Do you have some tips about the setup_common_caches?
Once caching is enabled[1] you won't be able to do I/O until the MMU is set up
for an uncached I/O mapping.
-Scott
[1] Or at some similar point during early init. It's been a while since I
worked on chips like this, so I don't recall the details of which caches are
enabled on kernel entry and whether there's some magic to exempt I/O, but I do
remember there being a stretch of time during init where doing I/O was a
problem.
prev parent reply other threads:[~2017-03-24 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 21:12 problem with cuImage.mpc834x_mds image Giuseppe Lippolis
2016-06-04 0:01 ` Scott Wood
2017-03-24 21:27 ` AW: " Giuseppe Lippolis
2017-03-24 22:10 ` Scott Wood [this message]
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=1490393405.2944.53.camel@buserror.net \
--to=oss@buserror.net \
--cc=giu.lippolis@gmail.com \
--cc=linuxppc-dev@lists.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 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.