From: Simon Yang <bestwish.simon@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 83xx TSEC
Date: Fri, 2 Dec 2005 13:56:10 +0800 [thread overview]
Message-ID: <1c3e00040512012156v91f28d8l@mail.gmail.com> (raw)
In-Reply-To: <4328B603.8020002@cray.com>
Hi David,
Have you resolved this now? Now I am also working with 83xx TSEC, but
we also meet the problem,in MDIO and MDC there isn't any signal, I
wonder if you meet the same problem in your board and whether you can
give me some comment on this!
Best Regards,
Simon
2005/9/15, David Updegraff <dave@cray.com>:
> Hi.
>
> Anyone know of any registers to look at in the TSEC stuff that might
> tell a guy why a frame is not moving?
>
> Our PHY looks fine; 'mii dump' is fine, link up, etc. but in tsec_send()
> the buffer of a ping is loaded up, and simply never goes anywhere.
> ->tstat remains clear (no halt bit), but rtx.txbd[txIdx].status never
> changes from assigned value.
>
> Stats claim no frames; which is correct. I need some help in
> understanding why TSEC feels it cannot feed anything out the inerface.
>
> Thanx.
>
> -dbu.
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server. Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
next prev parent reply other threads:[~2005-12-02 5:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 23:45 [U-Boot-Users] 83xx TSEC David Updegraff
2005-12-02 5:56 ` Simon Yang [this message]
2005-12-02 15:42 ` [U-Boot-Users] " David Updegraff
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=1c3e00040512012156v91f28d8l@mail.gmail.com \
--to=bestwish.simon@gmail.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 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.