From: Scott Wood <scottwood@freescale.com>
To: James Black <jblack547@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: mpc8270 and fs_enet
Date: Thu, 29 Jan 2009 17:05:43 -0600 [thread overview]
Message-ID: <49823647.2010701@freescale.com> (raw)
In-Reply-To: <b77025b40901291441j7790f85ewd70ee81dc09ed55b@mail.gmail.com>
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
next prev parent reply other threads:[~2009-01-29 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:41 mpc8270 and fs_enet James Black
2009-01-29 23:05 ` Scott Wood [this message]
2009-01-29 23:27 ` James Black
2009-02-19 16:18 ` James Black
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49823647.2010701@freescale.com \
--to=scottwood@freescale.com \
--cc=jblack547@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).