linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jochen Friedrich <jochen@scram.de>
To: Scott Wood <scottwood@freescale.com>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: mpc 860 boot linux2.6.23 problem
Date: Wed, 17 Oct 2007 20:54:54 +0200	[thread overview]
Message-ID: <47165A7E.1070206@scram.de> (raw)
In-Reply-To: <47162AE7.80305@freescale.com>

Hi Scott,

> I just pulled Wolfgang's latest u-boot tree, and I don't see any fdt or 
> ft_ calls in cpu/mpc8xx, nor in any 8xx board that I recognize.
>
> I may have been unclear in that I was talking about device tree support 
> in u-boot, not the kernel.  Obviously there's device tree support in the 
> kernel, as evidenced by my reference to using cuImage.
>   

Can u-boot work on dtb trees embedded in an cuImage, at all?
How would command line arguments work without a chosen
node?

I tried to boot a mpc823 using the 3 argument mboot command.
u-boot processed the dtb and added the chosen node correctly,
however the kernel immediately oopsed with unable to access
virtual memory when accessing the dtb memory as this memory
was not contained in the kernel MMU space.

Thanks,
Jochen

  parent reply	other threads:[~2007-10-17 18:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15  3:15 mpc 860 boot linux2.6.23 problem keng_629
2007-10-15 17:17 ` Scott Wood
2007-10-15 23:38   ` Wolfgang Denk
2007-10-16 16:18     ` Scott Wood
2007-10-17  2:58       ` Dan Malek
2007-10-17 15:31         ` Scott Wood
2007-10-17 16:40           ` Dan Malek
2007-10-17 17:26             ` Scott Wood
     [not found]               ` <200710190724253750363@126.com>
2007-10-21 13:43                 ` keng_629
2007-10-17 18:54           ` Jochen Friedrich [this message]
2007-10-17 19:15             ` Scott Wood

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=47165A7E.1070206@scram.de \
    --to=jochen@scram.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=scottwood@freescale.com \
    /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).