From: Scott Wood <scottwood@freescale.com>
To: Alexandros Kostopoulos <akostop@inaccessnetworks.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: pq2fads support...
Date: Fri, 27 Jul 2007 12:45:44 -0500 [thread overview]
Message-ID: <46AA2F48.3020702@freescale.com> (raw)
In-Reply-To: <op.tv4vfiaunhx3hy@phoenix>
Alexandros Kostopoulos wrote:
> Thanks for your reply, Scott,
>
> one question though: I am NOT using the bootwrapper, I'm instead
> feeding dtb and uImage directly to u-boot. This probably means that
> I should fill in lots of stuff manually into dts, right?
No, u-boot should fill in the same stuff. It may require the empty
fields to be there, though (it definitely requires it if you're using
the old, non-libfdt code -- if you are, you should also remove the
/chosen node, or else you'll get two of them).
> But, (and please forgive my ignorance) who does actually fill in
> stuff (like e.g. clock-frequency or bus-frequency), except, of
> course, from the trivial modifications u-boot does to dtb? The
> wrapper script seems to do nothing more that simply running dtc on
> dts.
In the bootwrapper case, it's the code in cuboot-pq2.c and devtree.c.
In the no-bootwrapper case, it's u-boot.
-Scott
next prev parent reply other threads:[~2007-07-27 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 12:24 pq2fads support Alexandros Kostopoulos
2007-07-27 16:35 ` Scott Wood
2007-07-27 17:12 ` Alexandros Kostopoulos
2007-07-27 17:45 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 14:23 PQ2FADS Support Kevin A. Sapp
2003-10-18 21:03 ` Wolfgang Denk
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=46AA2F48.3020702@freescale.com \
--to=scottwood@freescale.com \
--cc=akostop@inaccessnetworks.com \
--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.