From: 신경수 <ksshin@essetel.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PCI DMA in GT64260
Date: Fri, 26 Sep 2003 14:33:59 +0900 [thread overview]
Message-ID: <003301c383ef$c9b17ae0$c50aa8c0@ksshin> (raw)
In-Reply-To: 3F738F27.8000200@mvista.com
Thank you.
I check the GPP Pins and test that pins with osciloscope.
At the time when CPU commands to the L2 S/W chip that
'transmit data', L2 S/W chip asserts PCI_REQ* signal(this is connected
to GPP pin) and GT64260 alos asserts PCI_GNT* signal(also this pin is
connected to GPP pin). and L2 S/W chip also asserts PCI_FRAME*
signal. So I think GPP setting is no problem.
I think that the value of BAR Regs in GT64260 Config Space is wrong,
so I try to change the value with PCI_CONFIG_ADDR, PCI_CONFIG_DATA,
when I scan PCI Bus, in bus no 0 or 1, dev no 0, I found GT64260 PCI Bridge,
But I cannot change the value of BAR in PCI CONFIG Space.
How can I change the value of BAR in PCI CONFIG Space.
another is,
you say that there are several working examples.
But I can't found any examples related to PCI_DMA or
changing the value of BAR in PCI CONFIG Space.
please let me know how to solve the PCI DMA
----- Original Message -----
From: "Mark A. Greer" <mgreer@mvista.com>
To: "신경수" <ksshin@essetel.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Sent: Friday, September 26, 2003 9:58 AM
Subject: Re: PCI DMA in GT64260
>
> 신경수 wrote:
>
> >Thank you for your response.
> >
> >Well, Instead of giving my all code, I give the register lists and the value
> >related to address decoding. please check the register and the value.
> >
> Well, there are several working examples that you can look at so I'm not
> going to spend much time groping through registers. However, from what
> you describe, I would guess that you have either a PCI arbitration
> problem or your PCI slave window is horked. I did a very quick look at
> the PCI slave windows & related regs and I didn't notice anything
> wrong--that doesn't mean there isn't--so it may be an arbitration problem.
>
> Are you using the 64260's PCI arbiter or do you have an external one? If
> 64260, then make sure that its configured correctly and that you have
> the appropriate GPP pins configured correctly. Again, several working
> examples so don't be shy about looking at them.
>
> Mark
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-26 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 7:54 PCI DMA in GT64260 신경수
2003-09-25 0:52 ` Mark A. Greer
2003-09-25 4:57 ` 신경수
2003-09-26 0:58 ` Mark A. Greer
2003-09-26 5:33 ` 신경수 [this message]
2003-09-26 18:46 ` Mark A. Greer
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='003301c383ef$c9b17ae0$c50aa8c0@ksshin' \
--to=ksshin@essetel.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgreer@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox