From: Scott Wood <scottwood@freescale.com>
To: zhanglei459 <zhanglei459@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: how to understand pci section in device tree source file
Date: Mon, 23 Jun 2008 12:02:10 -0500 [thread overview]
Message-ID: <485FD712.8010500@freescale.com> (raw)
In-Reply-To: <18070474.post@talk.nabble.com>
zhanglei459 wrote:
> I guess which refer to host-pci bridge ATMU,is right?
Yes.
> But how to descripe
> added-on pci chip,whose BAR0 and BAR1 are IO spaces, BAR2 and BAR3 are MEM
> spaces.
You don't need to -- this can be probed at run-time.
-Scott
prev parent reply other threads:[~2008-06-23 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 14:30 how to understand pci section in device tree source file zhanglei459
2008-06-23 17:02 ` 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=485FD712.8010500@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=zhanglei459@gmail.com \
/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.