From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Kumar Amarjit <amarjit.kumar-7K+nh26gSkEAvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
amarjit.kumar.mtech-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: Writing Device Tree Source (DTS)
Date: Mon, 30 Nov 2009 14:57:54 -0600 [thread overview]
Message-ID: <20091130205754.GA11487@loki.buserror.net> (raw)
In-Reply-To: <200911230858.nAN8vsWf006884-QAxaCDP67tRcIBjhHP3Ktq0bRtRcJeJQ@public.gmane.org>
On Mon, Nov 23, 2009 at 02:27:44PM +0530, Kumar Amarjit wrote:
> Hi All,
> We are using PowerPc440 core on our Soc that consists of PCIe core, SAS core
> and many other things.
> We are writing DTS for our board to be used during booting, we have gone
> through various dts files available inside the Linux Kernel 2.6.31.
> Our board is closets match with Taishan board.
> While referring the Taishan.dts, we are unable to get the information
> regarding Interrupt-map and interrupt-map-mask property.
> Please refer to the snippet.......
> It would be great if anybody help me to understand the way they are writing
> these properties?
> I also gone through the DTS document booting-without-of but that does not
> help us, so anybody having any documents on How To Write DTS can help me
> out.
These properties are documented in ePAPR -- or you can look at the original
Open Firmware interrupt mapping recommended practice document plus the PCI
binding.
-Scott
prev parent reply other threads:[~2009-11-30 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 8:57 Writing Device Tree Source (DTS) Kumar Amarjit
[not found] ` <200911230858.nAN8vsWf006884-QAxaCDP67tRcIBjhHP3Ktq0bRtRcJeJQ@public.gmane.org>
2009-11-23 16:48 ` Yoder Stuart-B08248
2009-11-30 20:57 ` Scott Wood [this message]
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=20091130205754.GA11487@loki.buserror.net \
--to=scottwood-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=amarjit.kumar-7K+nh26gSkEAvxtiuMwx3w@public.gmane.org \
--cc=amarjit.kumar.mtech-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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.