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: Mon, 22 Dec 2008 11:37:20 -0600 [thread overview]
Message-ID: <494FD050.7020405@freescale.com> (raw)
In-Reply-To: <loom.20081222T064929-412@post.gmane.org>
Daniel Ng wrote:
> Thanks for your helpful responses Scott and Ming Qian. Now, from reading the
> docco can you please verify my understanding is correct?-
>
> First, I need a basic DTS file which will give me a basic Device Tree. The
> cuboot*.c file takes care of adding other parameters to the Device Tree passed
> from u-boot via the old bd_info struct.
>
> Is this correct?
Yes.
> If so, would it be possible to do away with the DTS file
> altogether?
How, other than by encoding all the information about the board in code
rather than data, which would be a step backwards?
> On the other hand, would it be possible to do away with the
> cuboot*.c file by providing a complete DTS file?
Yes, though that eliminates the ability to dynamically set certain
parameters from the firmware. Better is to use an up-to-date u-boot,
and have u-boot fill in the dynamic fields (MAC address, clocks, command
line, etc) directly.
-Scott
next prev parent reply other threads:[~2008-12-22 17:37 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
2008-12-22 6:57 ` Daniel Ng
2008-12-22 17:37 ` Scott Wood [this message]
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=494FD050.7020405@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 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.