Netdev List
 help / color / mirror / Atom feed
From: Ron Eggler <ron.eggler@mistywest.com>
To: netdev@vger.kernel.org
Subject: Unable to TX data on VSC8531
Date: Sun, 30 Apr 2023 07:08:21 -0700	[thread overview]
Message-ID: <b0cdace8-5aa2-ce78-7cbf-4edf87dbc3a6@mistywest.com> (raw)

Hi,

I've posted here previously about the bring up of two network interfaces 
on an embedded platform that is using two the Microsemi VSC8531 PHYs. 
(previous thread: issues to bring up two VSC8531 PHYs, Thanks to Heiner 
Kallweit & Andrew Lunn).
I'm able to seemingly fully access & operate the network interfaces 
through ifconfig (and the ip commands) and I set the ip address to match 
my /24 network. However, while it looks like I can receive & see traffic 
on the line with tcpdump, it appears like none of my frames can go out 
in TX direction and hence entries in my arp table mostly remain 
incomplete (and if there actually happens to be a complete entry, 
sending anything to it doesn't seem to work and the TX counters in 
ifconfig stay at 0. How can I further troubleshoot this? I have set the 
phy-mode to rgmii-id in the device tree and have experimented with all 
the TX_CLK delay register settings in the PHY but have failed to make 
any progress.

Thank you,
Ron

             reply	other threads:[~2023-04-30 14:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30 14:08 Ron Eggler [this message]
2023-04-30 14:23 ` Unable to TX data on VSC8531 Andrew Lunn
2023-05-01 19:57   ` Ron Eggler
2023-05-01 20:12     ` Andrew Lunn
2023-05-01 20:23       ` Ron Eggler
2023-05-01  6:46 ` Horatiu Vultur
2023-05-01 20:34   ` Ron Eggler
2023-05-02  7:11     ` Horatiu Vultur
2023-05-02 20:16       ` Ron Eggler
2023-05-02 20:50         ` Horatiu Vultur
2023-05-04 19:25           ` Ron Eggler

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=b0cdace8-5aa2-ce78-7cbf-4edf87dbc3a6@mistywest.com \
    --to=ron.eggler@mistywest.com \
    --cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox