From: Matt Porter <porter@cox.net>
To: Khai Trinh <kqtrinh@yahoo.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 440 PCI adapter card DMA question
Date: Fri, 16 Aug 2002 13:50:24 -0700 [thread overview]
Message-ID: <20020816135024.A2119@home.com> (raw)
[Please, always start a new mail when starting a new thread. Don't
reply to an old one and change the subject, it messes up people
using mailbox threading.]
On Fri, Aug 16, 2002 at 11:39:15AM -0700, Khai Trinh wrote:
> On one of your response email to me, you said the
> 440GP maps PCI<->PLB 1:1 and I can use the PCI bus
> address directly as a PLB address to program the 440GP
> DMA controller.
>
> The thing is that the DMA high and low register only
> allows 36-bit programming whereas the PCI bus address
> given to me by the Host is 64-bit.
I was answering with respect to the Ebony PCI-X host bridge
configuration.
> Don't I have to manually setup the PCI-PLB mapping
> before I can program the DMA controller? OR the 440
> kernel has already handle that?
The PCI-X host bridge configuration in the Ebony port is
implemented for host operation only (i.e. it has set up
windows and controls BAR assignment within a controlled
PCI address space). If you need a special translation
for your particular adapter application, you will need
to modify that setup accordingly.
Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-08-16 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 20:50 Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-13 15:34 First steps to OCP device model integration Matt Porter
2002-08-16 18:39 ` 440 PCI adapter card DMA question Khai Trinh
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=20020816135024.A2119@home.com \
--to=porter@cox.net \
--cc=kqtrinh@yahoo.com \
--cc=linuxppc-embedded@lists.linuxppc.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).