All of lore.kernel.org
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: Trouble "Transferring control to Linux (at address 00000000)"
Date: Thu, 02 Jul 2009 15:23:36 +0200	[thread overview]
Message-ID: <m2iqibp6av.fsf@ohwell.denx.de> (raw)
In-Reply-To: 20090701170436.GA502@b07421-ec1.am.freescale.net

Hi Scott,

> On Wed, Jul 01, 2009 at 02:13:29PM +0200, Detlev Zundel wrote:
>> Hi,
>> 
>> > As for my device tree, I reverted back to the original version with
>> > nothing filled in and just replaced 0xfa20xxxx with 0xf000xxxx as Gary
>> > suggested earlier.
>> 
>> Would it be a problem to also dynamically fixup IMMR in the device tree
>> from U-Boot?
>
> Yes.  It can appear in multiple places in the device tree (for exmaple,
> in things like the localbus and pci nodes where we have some IMMR
> registers but need ranges to point outside IMMR); this introduces more
> dependencies between u-boot and the input dtb than just getting the
> address right in the first place.

Ah, I see - the IMMR address is duplicated because the nodes you mention
are not children of "soc", so they cannot reference that parent address
space.

I guess re-arranging the hierarchy is not viable, but maybe we can
include this orthogonal parent-child relation.  For example, could a
"reg-parent" phandle solve this duplication?

Cheers
  Detlev

--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu@denx.de

  reply	other threads:[~2009-07-02 13:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 16:13 Trouble "Transferring control to Linux (at address 00000000)" Mikhail Zaturenskiy
2009-06-26 16:55 ` Scott Wood
2009-06-26 17:12   ` Mikhail Zaturenskiy
2009-06-27 21:01     ` Frank Svendsbøe
2009-06-29 17:53       ` Mikhail Zaturenskiy
2009-06-29 18:02         ` Gary Thomas
2009-06-29 18:13           ` Mikhail Zaturenskiy
2009-06-29 18:41             ` Scott Wood
2009-06-29 20:24               ` Mikhail Zaturenskiy
2009-06-29 20:31                 ` Scott Wood
2009-06-29 20:46                   ` Mikhail Zaturenskiy
2009-06-29 21:03                     ` Scott Wood
2009-06-30 16:11                       ` Mikhail Zaturenskiy
2009-06-30 17:48                         ` Mikhail Zaturenskiy
2009-07-01 12:13                           ` Detlev Zundel
2009-07-01 17:04                             ` Scott Wood
2009-07-02 13:23                               ` Detlev Zundel [this message]
2009-07-01 17:40                           ` Mikhail Zaturenskiy

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=m2iqibp6av.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --cc=linuxppc-dev@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.