From: David Gibson <david@gibson.dropbear.id.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, Eddie Dawydiuk <eddie@embeddedarm.com>
Subject: Re: Example dts file
Date: Sat, 18 Apr 2009 10:40:18 +1000 [thread overview]
Message-ID: <20090418004018.GA6187@yookeroo.seuss> (raw)
In-Reply-To: <fa686aa40904171012i7f67f6b6sae9a7fd4ff8e3807@mail.gmail.com>
On Fri, Apr 17, 2009 at 11:12:43AM -0600, Grant Likely wrote:
> On Fri, Apr 17, 2009 at 11:04 AM, Eddie Dawydiuk <eddie@embeddedarm.com> wrote:
> > Hello,
> >
> > I'm working on creating a dts file for a custom board based on the Yosemite
> > AMCC 440EP evaluation board. We have an FPGA connected to the PCI bus, and
> > I'm a bit unsure how to describe this in the dts file. The FPGA implements
> > an SD card core, RTC core, Nand core... Can anyone point me to an example
> > dts file I can refer to?
>
> If it is attached to the PCI bus, then you don't need to describe it
> in the .dts file. PCI can reliably probe for devices. Your driver
> should know what devices are present based on the PCI vendor and
> device IDs.
However, for onboard PCI devices it's often necessary to have a node
giving at least the interrupt routing information, because this can't
generally be probed by PCI.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2009-04-18 0:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 17:04 Example dts file Eddie Dawydiuk
2009-04-17 17:12 ` Grant Likely
2009-04-18 0:40 ` David Gibson [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=20090418004018.GA6187@yookeroo.seuss \
--to=david@gibson.dropbear.id.au \
--cc=eddie@embeddedarm.com \
--cc=grant.likely@secretlab.ca \
--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 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).