From: Scott Wood <scottwood@freescale.com>
To: "Gray, Steve - UK" <Steve.Gray@peek-traffic.co.uk>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Ucode/BD conflict on PowerPC 860
Date: Thu, 23 Oct 2008 10:31:48 -0500 [thread overview]
Message-ID: <490098E4.6090908@freescale.com> (raw)
In-Reply-To: <85A8D9AB423A3A4ABD022AD90C989C4D010904A2@uksv0008.peek.prv>
Gray, Steve - UK wrote:
> I have tried a few things, including setting the range of muram to
> ranges = <0x0 0x3000 0x1000>;
>
> Am I correct to assume this will push the muram above the microcode??
No, that will confuse the kernel into thinking that muram starts at IMMR
offset 0x3000. You need to change the reg property of the data subnode
to <0x1000 0xc00>, so that you restrict the allocation range without
affecting the offset that is subtracted from the physical address to
obtain the value given to the CPM.
-Scott
next prev parent reply other threads:[~2008-10-23 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 10:02 Mounting PRAMFS support Pieter
2008-08-12 18:11 ` Wolfgang Denk
2008-08-13 9:30 ` Pieter
2008-10-23 7:59 ` Ucode/BD conflict on PowerPC 860 Gray, Steve - UK
2008-10-23 15:31 ` Scott Wood [this message]
2008-10-24 13:03 ` Gray, Steve - UK
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=490098E4.6090908@freescale.com \
--to=scottwood@freescale.com \
--cc=Steve.Gray@peek-traffic.co.uk \
--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).