headers
Bill F | 22 Jun 2012 21:14
Picon

Help with Freescale QE ATM driver (FUA)

Hi,
Have you used the Freescale QUICC Engine (QE) ATM mode with a Linux
based product ?

I am currently using the "fua" driver obtained from Freescale
MPC8360E_PB_K26_20081112-LTIB.iso CDROM image.  The "fua" driver was
written for kernel 2.6.22 (2007) and I have ported it forward to
kernel 3.3 (2012).  My board has an MPC8358 and SUNI PHY.  I am
testing the fua driver with the atm-tools and aburst, and using a
loopback cable.

The ported fua driver is able to open an ATM connection and send and
receive messages.  I can use awrite and aread to send and receive
ascii characters.

Problems:
  * If I open three or more ATM connections, all ATM transfers stop,
and the ethernet driver (ucc_geth) also stops working.  To recover I
have to reboot. Urg.
  * UBR transfers seem to be treated as if they are a 100 Mbps CBR
connection.  I was expecting UBR to fill all of the unused bandwidth.
  * I'm finding and fixing a lot of minor bugs that crash the driver.

My other reference is the mpc8360 SAR driver
(http://mpc8360sar.sourceforge.net) which is even older (patches
against kernel 2.6.11).

If someone on this list is sitting on an updated fua driver or similar
QE ATM driver, could you send me the code.  Better yet, can I help you
push it out to a github or similar repo ?
(Continue reading)

Permalink | Reply |
headers
Michael Steckly | 26 Jun 2012 17:21
Favicon

Help with Freescale DPAA bug

I'm hoping someone here can help me.  Several levels of Freescale
management have assured me that I am authorized to discuss their Linux
code on public lists--and even explicitly suggested the ozlabs
linuxppc-dev list.

I'm using the P4080 processor and the Freescale SDK on a custom board. 
We've had some stability issues so I've turned on some debugging in the
DPAA (CONFIG_FSL_DPA_CHECKING) and when I enable multiple cores, the
system panics with the message:

Parallel attempts to enter bman_released() detected.
Kernel panic - not syncing: only one instance of bman_released/acquired
allowed
Call Trace:
[ede35de0] [c000812c] show_stack+0x44/0x154 (unreliable)
[ede35e20] [c0419e28] panic+0xa4/0x1d0
[ede35e70] [c0301324] bman_release+0x614/0x854
[ede35ed0] [c02e4dbc] dpa_bp_add_8+0xe0/0x1b4
[ede35f40] [c02e6eb0] dpaa_eth_poll+0x8c/0x98
[ede35f60] [c0329fd4] net_rx_action+0xc0/0x178
[ede35fa0] [c0032f78] __do_softirq+0xe8/0x174
[ede35ff0] [c000d7fc] call_do_softirq+0x14/0x24
[e90a9e80] [c00047fc] do_softirq+0x98/0xc4
[e90a9ea0] [c003328c] irq_exit+0x60/0x70
[e90a9eb0] [c00044ec] do_IRQ+0x94/0x188
[e90a9ee0] [c000f29c] ret_from_except+0x0/0x18
Parallel attempts to enter bman_released() detected.
--- Exception: 501 at cpu_idle+0x88/0xd8
    LR = cpu_idle+0x88/0xd8
Kernel panic - not syncing: only one instance of bman_released/acquired
(Continue reading)

Permalink | Reply |

Gmane