out why...
Regards,
Sumedh
On Mon, Feb 23, 2009 at 11:03 PM, sjoy...@wanadoo.fr sjoy...@wanadoo.fr
wrote:
Hi Sumedh,
You may check the context in which your CPU in running the C code from
interrupt context (ie stack pointer (r1), kernel locks disabling
rescheduling etc..) and double
Hi Sumedh,
You may check the context in which your CPU in running the C code from
interrupt context (ie stack pointer (r1), kernel locks disabling
rescheduling etc..) and double check the IRQ originator (the decrementer) is
acknowlegded somewhere your handler before enabling back interrupts, else
Hi Scott,
Your issue may come from data setup (or corruption) instead of code path:
babbling error may occurs when a TSEC TX descriptor hasn't its last frame
bit set or when the data length is greated than max frame length.
--
sj
2009/2/19 Scott Coulter scott.coul...@cyclone.com
Kumar,
Hi Wael,
1. The DMA engine source and destination registers are based on
physical memory addresses, whatever is the bus connected on, thus you
need to provide it physical addresses.
It looks like you are a bit confused about the terminology DMA
buffer: a DMA buffer is either the source and/or