From: Sylvain Munaut <tnt@246tNt.com>
To: Asier Llano Palacios <a.llano@ziv.es>
Cc: John Rigby <jrigby@freescale.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Stability of MPC5200 FEC
Date: Sat, 11 Feb 2006 16:28:26 +0100 [thread overview]
Message-ID: <43EE029A.5040504@246tNt.com> (raw)
In-Reply-To: <1139592010.14894.22.camel@localhost.localdomain>
Asier Llano Palacios wrote:
> We are working with MPC5200 cpu.
> We've been using it since early 2.6 kernel versions.
> We're currently quite stabilished with the version of the kernel Sylvain
> had before the Platform Device rework. But the problem is that we are
> experiencing that the FEC stops working after a long uptime.
Did you ever observe that behavior on a lite5200 ?
What is 'long uptime' and do you have sustained transfer during that
period ? (To try reproduice the problem).
Also, what are the 'symptoms' ? (anything in dmesg ?)
> So, do you think that the current git version is more stable than the
> one we are using? Do you think that there is anything that could stop us
> upgrading to the latest version?
Doubtfull, I haven't touched the FEC code much except to remove the
aligment code (newer bestcomm microcode doesn't require alignement of
the skb). It should be reworked to use the generic phy code and remove
some "bugs" (like the fact when we down the interface, we stop the task
but not deactivate the MAC IIRC, which cause warning in dmesg).
You can send me the driver/net/fec_mpc52xx and arch/ppc/syslib/bestcomm
you're using, I'll tell you if there was major changes.
> The problem is that we have a custom board, with some custom devices, so
> it is not so easy to upgrade. We need to know that a new version, is
> more stable than the previous one, before we upgrade. As soon as we
> upgrade, we can help if we find any problem.
Sylvain
next prev parent reply other threads:[~2006-02-11 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 17:20 Stability of MPC5200 FEC Asier Llano Palacios
2006-02-10 18:22 ` John Rigby
2006-02-11 15:28 ` Sylvain Munaut [this message]
2006-02-11 16:08 ` Wolfgang Denk
2006-02-13 8:08 ` Asier Llano Palacios
2006-02-14 17:35 ` John Rigby
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=43EE029A.5040504@246tNt.com \
--to=tnt@246tnt.com \
--cc=a.llano@ziv.es \
--cc=jrigby@freescale.com \
--cc=linuxppc-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.