From: Vinayak Kale <vinayak.kale@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Subject: DTS for PowerPC 440 based board
Date: Sun, 22 Nov 2009 00:16:59 +0530 [thread overview]
Message-ID: <5eb65910911211046q433072f1nd2a6eb955593a37a@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
Hi,
I am porting 2.6.31 for a PowerPC 440 core based board. I have couple of
queries. I would really appreciate if someone could answer since i couldn't
find info from other places.
1) Is it mandatory to create a DTS file?
2) If uboot passes BDInfo struct to kernel instead of DT blob, then in this
case does kernel creates FDT at run time?
3) I believe in case of DTS, the kernel picks up the h/w info from DTS blob
so we need not hardcode any register addresses etc inside kernel other than
in dts file. What happens in case of uboot passing just BDInfo struct. How
do we specify the register addresses etc?
Thanks
Vinayak
[-- Attachment #2: Type: text/html, Size: 670 bytes --]
next reply other threads:[~2009-11-21 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 18:46 Vinayak Kale [this message]
2009-11-21 21:20 ` DTS for PowerPC 440 based board David Gibson
2009-11-23 3:32 ` Grant Likely
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=5eb65910911211046q433072f1nd2a6eb955593a37a@mail.gmail.com \
--to=vinayak.kale@gmail.com \
--cc=linuxppc-dev@lists.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).