From: Scott Wood <scottwood@freescale.com>
To: Daniel Ng <daniel_ng11@lycos.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Device Tree setup for 8272-based board
Date: Fri, 19 Dec 2008 14:03:55 -0600 [thread overview]
Message-ID: <494BFE2B.2010103@freescale.com> (raw)
In-Reply-To: <loom.20081219T062005-806@post.gmane.org>
Daniel Ng wrote:
> We are migrating our PowerPC 8272-based board from 2.6.14 to 2.6.27.
>
> One of the big changes is the need for a Device Tree for bootup.
>
> So far, my bootup looks like the below (using u-boot).
>
> I am just using arch/powerpc/boot/cuboot-824x.c
cuboot-824x is for 8240, 8245, and similar chips. You want cuboot-pq2.
> When I change the settings in mpc8272ads.dts and do a fresh recompile, the
> settings do not change. However, if I use another cuboot*.c file, I get a
> different set of printed settings eg. 2 ethernet ports instead of 1. This is
> fine, but I don't see where in the cuboot*.c file these settings are
> specified. Can someone suggest where these might be?
The cuboot file defines things like TARGET_CPM2 or TARGET_824x, which
influences the compilation of the bd_t struct. It's messy, which is why
we use device trees now. :-)
-Scott
next prev parent reply other threads:[~2008-12-19 20:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 6:31 Device Tree setup for 8272-based board Daniel Ng
2008-12-19 16:37 ` mingqian
2008-12-19 20:03 ` Scott Wood [this message]
2008-12-22 6:57 ` Daniel Ng
2008-12-22 17:37 ` Scott Wood
2008-12-23 0:52 ` Daniel Ng
2008-12-23 16:09 ` Scott Wood
2008-12-23 23:21 ` Daniel Ng
-- strict thread matches above, loose matches on Subject: below --
2009-01-16 1:22 Daniel Ng
2009-01-16 3:40 ` Daniel Ng
2009-01-16 18:14 ` Scott Wood
2009-01-19 1:58 ` Daniel Ng
2009-01-19 17:29 ` Scott Wood
2009-01-20 7:23 ` Daniel Ng
2009-01-20 16:41 ` Scott Wood
2009-01-21 7:37 ` Daniel Ng
2009-01-21 17:52 ` Scott Wood
2009-01-22 7:47 ` Daniel Ng
2009-01-22 17:05 ` 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=494BFE2B.2010103@freescale.com \
--to=scottwood@freescale.com \
--cc=daniel_ng11@lycos.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).