From: Kumar Gala <kumar.gala@motorola.com>
To: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
Cc: <linuxppc-embedded@lists.linuxppc.org>,
Jason McMullan <jason.mcmullan@timesys.com>,
Dan Malek <dan@embeddededge.com>
Subject: Re: MPC8560ADS issues
Date: Thu, 11 Mar 2004 16:52:23 -0600 [thread overview]
Message-ID: <C27D4FB6-73AE-11D8-A4B4-000393DBC2E8@motorola.com> (raw)
In-Reply-To: <1079025268.29565.51.camel@chuck.arlut.utexas.edu>
I'm confused the gianfar driver is for the MPC8540 FEC. I believe the
initial question was regarding the FCC (on CPM / MPC8560).
As to why your having poor performance on the MPC8540 FEC, that seems
odd -- possibly some issue with the Intel PHY. I do not believe we are
seeing anything similar on the ADS.
- kumar
On Mar 11, 2004, at 11:14 AM, Matthew S. McClintock wrote:
>
> On Thu, 2004-03-11 at 10:16, Dan Malek wrote:
>
>> Do you keep up to date with the linuxppc trees? Some of us have been
>> pushing lots of CPM updates lately. We recently updated all of the
>> common code for 82xx and 85xx. If this doesn't work there must be
>> some I/O or board configuration that is amiss.
>
> I'm running the latest linuxppc-2.4 branch. I'm not using the
> MPC8540ADS
> board, the board I am using has an Intel LXT971A PHY attached to the
> FCC. I've added support for that physical layer to
> drivers/gianfar_phys.c. I'm guessing something is wrong with that code
> that is making it go so slow, but I have been unable to pinpoint what
> might be wrong.
>
> I've noticed that the interrupts for the FCC come in at a very very
> slow
> pace, that is the only thing I have really noticed that is odd. I've
> also tried changing the priority of the interrupt via the IIVPR
> register
> for the FCC with no results. I can't think of anything else I can
> investigate, unless you have any ideas?
>
> Thanks,
> Matthew
>
> --
> Matthew S. McClintock <mattsm@arlut.utexas.edu>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-03-11 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 19:04 MPC8560ADS issues Jason McMullan
2004-03-11 15:43 ` Matthew S. McClintock
2004-03-11 16:16 ` Dan Malek
2004-03-11 17:14 ` Matthew S. McClintock
2004-03-11 22:52 ` Kumar Gala [this message]
2004-03-11 23:53 ` Matthew S. McClintock
2004-03-11 18:42 ` Jason McMullan
2004-03-11 19:30 ` Dan Malek
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=C27D4FB6-73AE-11D8-A4B4-000393DBC2E8@motorola.com \
--to=kumar.gala@motorola.com \
--cc=dan@embeddededge.com \
--cc=jason.mcmullan@timesys.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mattsm@arlut.utexas.edu \
/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).