Hi,
we build some 4xx based PMC modules in the past. These boards can
run as host (processor PMC or so called monarch mode) or as PCI endpoint
(non-monarch mode). I would like to use the same DT (and kernel) in both
modes.
Currently I set the status property of the PCI node to disabled to
On Tue, 2008-11-04 at 12:17 +0100, Matthias Fuchs wrote:
I must admit that I am not sure what you mean by (pci-endpoint)
_name_.
Do you mean something like this:
PCI: [EMAIL PROTECTED] {
endpoint = pci-endpoint;
...
To many endpoint appearances
On Tuesday 04 November 2008 07:16, Benjamin Herrenschmidt wrote:
It is device_type for PCIe right now, I'm afraid. This was what we agreed
upon. Here a code sniplet from the patch:
/* Check if device_type property is set to pci or pci-endpoint.
* Resulting from this setup this
Hi Ben,
On Thursday 30 October 2008 21:15, Benjamin Herrenschmidt wrote:
On Thu, 2008-10-30 at 11:58 +0100, Matthias Fuchs wrote:
I need to connect to the PCI command write interrupt on a 440EPx
platform. This is UIC0/int#5.
Where should I add this interrupt in the DT? To the PCI node?
On Monday 03 November 2008 12:54, Stefan Roese wrote:
On Monday 03 November 2008, Benjamin Herrenschmidt wrote:
On Mon, 2008-11-03 at 10:10 +0100, Matthias Fuchs wrote:
Adding this interrupt to the PCI node would make (logical) sense. But
on PCI adapter (add-in cards) designs we typically
On Monday 03 November 2008 11:57, Benjamin Herrenschmidt wrote:
On Mon, 2008-11-03 at 10:10 +0100, Matthias Fuchs wrote:
Adding this interrupt to the PCI node would make (logical) sense. But
on PCI adapter (add-in cards) designs we typically disable the PCI node
of the DT to disable PCI
On Monday 03 November 2008, Benjamin Herrenschmidt wrote:
On Mon, 2008-11-03 at 10:10 +0100, Matthias Fuchs wrote:
Adding this interrupt to the PCI node would make (logical) sense. But
on PCI adapter (add-in cards) designs we typically disable the PCI node
of the DT to disable PCI PnP. This
On Mon, 2008-11-03 at 10:10 +0100, Matthias Fuchs wrote:
Adding this interrupt to the PCI node would make (logical) sense. But
on PCI adapter (add-in cards) designs we typically disable the PCI node
of the DT to disable PCI PnP. This should not prevent us from adding the
interrupt to the
I will try to add endpoint support for PCI as well. I would like to have a
single PCI node and
let the device_type attribute decide if we are running in hostbridge or
endpoint mode.
Don't use device_type. Do the same we do for PCI-E (whatever it is, I
don't have the source code at hand
On Monday 03 November 2008, Benjamin Herrenschmidt wrote:
I will try to add endpoint support for PCI as well. I would like to have
a single PCI node and let the device_type attribute decide if we are
running in hostbridge or endpoint mode.
Don't use device_type. Do the same we do for PCI-E
On Tue, 2008-11-04 at 06:19 +0100, Stefan Roese wrote:
On Monday 03 November 2008, Benjamin Herrenschmidt wrote:
I will try to add endpoint support for PCI as well. I would like to have
a single PCI node and let the device_type attribute decide if we are
running in hostbridge or endpoint
Hi,
I need to connect to the PCI command write interrupt on a 440EPx platform.
This is UIC0/int#5.
Where should I add this interrupt in the DT? To the PCI node? In this case it
will collide with the
PCI interrupts.
My application is a 440EPx on a PCI addon card. So the PCI node is disabled
On Thu, 2008-10-30 at 11:58 +0100, Matthias Fuchs wrote:
I need to connect to the PCI command write interrupt on a 440EPx
platform. This is UIC0/int#5.
Where should I add this interrupt in the DT? To the PCI node? In this
case it will collide with the
PCI interrupts.
My application is a
13 matches
Mail list logo