Hi all,
I'm trying to bring up a RapidIO on my p2020 on v2.6.36-rc7. I'm
running into an issue when the host tries to enumerate the agent
devices, and fails miserably. The rio driver does a
fsl_rio_config_read with a destid of 255, after which it hangs, until
I get a timeout exception (Handled n
s via the alternate device id register I could
finally get doorbell messages across with the jtag.
Thanks
On Fri, Oct 29, 2010 at 2:21 AM, Micha Nelissen wrote:
> Thomas Taranowski wrote:
>>
>> use my trusty jtag to issue a Port Link Maintenance Request and
>> request status
Going through the code, it looks like the rapidio driver assumes
there's only going to be a single Port implemented.
Snapshot of code assumes a single port atmu configuration block, which
is wrong for the p2020, and probably other QorIQ processors.
priv->atmu_regs = (struct rio_atmu_regs *)(priv
linux
patchset for the p2020 do nothing to resolve this issue.
On Mon, Nov 1, 2010 at 8:58 AM, Bounine, Alexandre
wrote:
> Thomas Taranowski wrote:
>> Yes, I tried pretty much all combinations of boot order, but I believe
>> the preferred approach is to boot the agents first, th
Is there an official maintainer's repository for RapidIO related
changes to I should be tracking? I've been tracking Kumar's git
repository (off kernel.org), but I'm not clear on who the keeper of
this stuff is.
Thanks!
Thomas Taranowski
Certified netburner consul
ructures. I think I want to create a new set
that's p2020 specific, but has potential to be shared with the other
QorIQ series, so dumping the pseries-specific code into
platforms/pseries seems like a reasonable way to go. Thoughts?
Thanks!
Thomas Taranowski
Certified netburner c
>
>> There is some divergance in respect to the memory map that is non-trivial
>> that
>> I'm not sure how to handle, since it totally hoses the common fsl_rio.c
>> structures.
>> I think I want to create a new set that's p2020 specific, but has potential
>> to be
>> shared with the other QorIQ
I actually take most of this back, it looks like there is a path
available so as not to fork the driver for the pseries.
Thomas Taranowski
Certified netburner consultant
baringforge.com
On Wed, Dec 15, 2010 at 12:40 PM, Thomas Taranowski
wrote:
>>
>>> There is some diverganc
fix is to just fall through and read out current doorbell entries.
Tested against 2.6.26-rc8 on a p2020
Signed-off-by: Thomas Taranowski
---
arch/powerpc/sysdev/fsl_rio.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/sysdev/fsl_rio.c b/arch/powerpc/sysdev
added attrs, err=0
returning 0
RIO: rionet_init rio_register_driver: rc=0
Any ideas on why rionet isn't being probed? Is rionet currently working?
I'm running a 2.6.36-rc8 baseline.
Thanks,
Thomas Taranowski
___
Linuxppc-dev mailing list
Linuxppc-
10 matches
Mail list logo