From: Sylvain Munaut <tnt@246tNt.com>
To: Andrea Galbusera <andrea.galbusera@teamware.it>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Ethernet fails on MPC5200 based target
Date: Tue, 16 Jan 2007 13:00:37 +0100 [thread overview]
Message-ID: <45ACBE65.6050602@246tNt.com> (raw)
In-Reply-To: <1168935615.22089.31.camel@localhost.localdomain>
Andrea Galbusera wrote:
>> Maybe some things (like xlb pipelining, cache snooping, ...) is not properly
>> setup in you platform support code ?
>>
>
> Following your suggestion, I started from here... Comparing the
> unaffected kernel (from DENX) with yours I tryed commenting out the
> following in mpc52xx_setup_cpu() :
>
> /* Disable XLB pipelining */
> /* (cfr errate 292. We could do this only just before ATA PIO
> transaction and re-enable it after ...) */
> out_be32(&xlb->config, in_be32(&xlb->config) | MPC52xx_XLB_CFG_PLDIS);
>
> In fact this gives much better results, but does not completely solve
> the problem. Network packets corruption seems to be gone, but, after
> massive pinging (about 1k ping packets) it comes back with about the
> same frequency as before the change.
>
And does the problem also appears on the denx kernel after 1k ping packets ?
Are the fec driver the same ?
Are the fec task code the same ? (in bestcomm/fec.c )
> I can't figure out what is the impact of keeping XLB pipelining enabled
> on the eth behavior. I'm sharing this results in the hope someone have
> any other valuable suggestion
>
Well me neither, it should only affect performance, not create
corruption ...
AFAI understand it anyway.
Sylvain
next prev parent reply other threads:[~2007-01-16 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 14:26 Ethernet fails on MPC5200 based target Andrea Galbusera
2007-01-10 14:52 ` Sylvain Munaut
2007-01-10 15:41 ` Andrea Galbusera
2007-01-16 8:20 ` Andrea Galbusera
2007-01-16 12:00 ` Sylvain Munaut [this message]
2007-01-16 14:46 ` Andrea Galbusera
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=45ACBE65.6050602@246tNt.com \
--to=tnt@246tnt.com \
--cc=andrea.galbusera@teamware.it \
--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.