I may have come across a similar problem, but I've never worked card-to-card
without at least one switch in the way.
The problems I have encountered have been hang-ups during memory-mapped
maintenance reads to devices that the switch reports as "up".
A workaround for the hang-up is to use a DMA
IRQ assignments for MPC8641D are "virtual", meaning "made up" and quite
difficult to determine by looking through code.
But I believe the plan goes something like this:
IRQ
-
0 No interrupt
1 - 15External interrupts (only 1..12 would be used)
16 - 127 Inte
> -Original Message-
> From: Bounine, Alexandre [mailto:alexandre.boun...@idt.com]
> Sent: Wednesday, September 15, 2010 11:53 AM
> To: Anderson, Trevor; Andrew Morton
> Cc: linux-ker...@vger.kernel.org; Thomas Moll; linuxppc-dev@lists.ozlabs.org
> Subject: RE: [PATCH
Keep it in please. We lurkers in the embedded community do use the per-port
routing tables.
One of the problems with SRIO switch tables is that access to routes is not
atomic; we can use
restricted access to per-port routing tables to reduce the risk of
interference. And we still use
the Global
With regards to your Oops: we sometimes find that, although a switch may
report a port being active, whenever
we try to discover what lies behind it, transfer errors occur that are
non-recoverable.
As a solution, on Freescale MPC8641D, we use a DMA transfer to perform a
simple MAINT read on a new
