public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Pierre AUBERT <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FEC problems on MPC5200
Date: Wed, 24 Mar 2004 15:37:42 +0100	[thread overview]
Message-ID: <40619D36.6080601@staubli.com> (raw)
In-Reply-To: <20040319104657.27D23C0655@atlas.denx.de>

Hi everybody,

Wolfgang Denk wrote:

>In message <405AC56F.9020200@staubli.com> you wrote:
>  
>
>>I've got some ethernet problems with a Lite5200.
>>    
>>
>...
>  
>
>>Has somebody experienced same problems on a MPC5200 ?
>>    
>>
>
>Yes, we see the same problem, and "bad length" errors. It  seems  the
>problem  was  introduced  by  one  of  the  patches lately. We're in-
>vestigating.
>
>
>Best regards,
>
>Wolfgang Denk
>
>  
>
I've made a lot of tries with the MPC5200 FEC. It appears that timeouts 
occurs
because some ACK frames aren't sent by the MPC5200 (but all is OK in 
mpc5xxx_fec_send).

The problem disappears if I suppress the full duplex (in 
fec->eth->x_cntrl and in the reg 0 of the LXT971A).
I can submit a patch.

But I have another question: if I suppress all the MII initialization 
sequence in cpu/mpc5xxx/fec.c, the LXT971A
reads its configuration from hardware and network is working fine at 10M 
and 100M on my Lite5200. The
auto-negociation works fine. Then, do we need to keep this (broken ?) 
init sequence ?
Is there something I have missed ?

Best regards

  reply	other threads:[~2004-03-24 14:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19 10:03 [U-Boot-Users] FEC problems on MPC5200 Pierre AUBERT
2004-03-19 10:07 ` Jón Benediktsson
2004-03-19 11:31   ` Pierre AUBERT
2004-03-19 15:27     ` Jón Benediktsson
2004-03-19 10:46 ` Wolfgang Denk
2004-03-24 14:37   ` Pierre AUBERT [this message]
2004-03-19 11:06 ` R: " Figini Enzo

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=40619D36.6080601@staubli.com \
    --to=p.aubert@staubli.com \
    --cc=u-boot@lists.denx.de \
    /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