linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Dan Malek <dan@embeddedalley.com>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: mpc 860 boot linux2.6.23 problem
Date: Wed, 17 Oct 2007 10:31:51 -0500	[thread overview]
Message-ID: <47162AE7.80305@freescale.com> (raw)
In-Reply-To: <85100356-D95B-4343-98BE-66080EA9887D@embeddedalley.com>

Dan Malek wrote:
> 
> On Oct 16, 2007, at 12:18 PM, Scott Wood wrote:
> 
>> Upgrading to the latest u-boot certainly shouldn't hurt, but I don't
>> think there's any device tree support for 8xx yet,
> 
> Have you tried it?  Works for me.  In fact, most
> of the development you see today was done
> by Pantelis on the 8xx.

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.

-Scott

  reply	other threads:[~2007-10-17 15:32 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 [this message]
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
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=47162AE7.80305@freescale.com \
    --to=scottwood@freescale.com \
    --cc=dan@embeddedalley.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).