From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: linuxppc-embedded@ozlabs.org
Cc: Leonid <Leonid@a-k-a.net>
Subject: Re: PCI target implementation on AMCC PPC CPUs
Date: Tue, 11 Sep 2007 11:13:46 +0200 [thread overview]
Message-ID: <200709111113.46508.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <46E06259.5010305@ovro.caltech.edu>
Hi David,
we build a couple of PCI target designs using AMCC PowerPCs.
You are right that some things could be better. But ..
On Thursday 06 September 2007 22:26, David Hawkins wrote:
> There are several fundamental problems with the AMCC 440EP
> acting as a PCI target/slave;
>
> 2. Look in the data sheet and see if you can figure out
> how the host processor can generate an interrupt to
> the PowerPC core ... oops, you can't. That kind of
> makes it difficult to work with doesn't it.
You CAN! You can generate an interrupt to the PowerPC from the host
CPU bei writing to the PCI command register. You have to read the user manual
carefully. Perhaps it not that obvious.
Matthias
next prev parent reply other threads:[~2007-09-11 9:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 18:24 finding out the processor frequency Leisner, Martin
2007-09-06 18:43 ` Scott Wood
2007-09-06 19:15 ` Josh Boyer
2007-09-06 19:15 ` PCI target implementation on AMCC PPC CPUs Leonid
2007-09-06 20:15 ` David Hawkins
2007-09-06 23:30 ` Wolfgang Denk
2007-09-06 23:39 ` David Hawkins
2007-09-06 20:26 ` David Hawkins
2007-09-11 9:13 ` Matthias Fuchs [this message]
2007-09-11 17:32 ` David Hawkins
2007-09-11 18:17 ` David Hawkins
2007-09-12 7:17 ` Matthias Fuchs
2007-09-12 16:04 ` David Hawkins
[not found] <46E0B178.00C522.05513@m5-81.163.com>
2007-09-07 2:13 ` Leonid
2007-09-07 2:34 ` David Hawkins
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=200709111113.46508.matthias.fuchs@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--cc=Leonid@a-k-a.net \
--cc=linuxppc-embedded@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).