I thought the same thing. So I verified the memory map. We did have a conflict with the SPI stomping the FCC temp so we moved that. An interesting note is that we drop packets from time to time on the MCC as well due to a similar ready bit problem. The CPM never clears the bit.
------------------------------------------------------------------ IMMR memory map ------------------------------------------------------------------ > FCC1 Parameters 0x8400 256 > FCC1 Temp buffer 0x9000 128 > SCC1 Parameters 0x8000 256 > SCC2 Parameters 0x8100 256 > SCC4 Parameters 0x8300 256 > SMC1 Parameters 0x0000 64 > SMC2 Parameters 0x0040 64 > SCC1 Buff Desc 0x0080 64 > SCC2 Buff Desc 0x00C0 64 > SCC4 Buff Desc 0x0100 64 > SPI Param Pointer 0x89FC 2 > SPI Parameters 0x9000 76 > MCC2 Global Param 0x8800 128 > MCC2 HDLC Param 0x2000 8192 > MCC2 Extra Param 0xB000 1024 On Thu, Jan 29, 2009 at 4:05 PM, Scott Wood <scottw...@freescale.com> wrote: > James Black wrote: >> >> I've got an mpc8270 running the fs_enet v1.0 driver and we are having >> problems with randomly corrupted tx buffer descriptor ready bits. The >> CPM never clears the bit. This is a 2.6.19.2 kernel. We have the same >> kernel with the 8260_io driver (kernel is from the denx ELDK4.2) >> running on the mpc8250 that works perfect. > > Is it possible that some other CPM block is configured to use the same DPRAM > area that the descriptors are in? > > -Scott > -- Jim Black Senior Software Engineer Aztek Networks, Inc. 2477 55th Street, Suite 202 Boulder, CO 80301 www.azteknetworks.com _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
