From: Roelof Berg <rberg@berg-solutions.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: David Miller <davem@davemloft.net>,
Bryan Whitehead <bryan.whitehead@microchip.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lan743x: Added fixed link and RGMII support / debugging
Date: Wed, 3 Jun 2020 20:31:06 +0200 [thread overview]
Message-ID: <C69EECC3-5701-46FF-84E4-4F0AFDB52809@berg-solutions.de> (raw)
In-Reply-To: <20200603180615.GB971209@lunn.ch>
I’m testing with Microchip Lan7430, which is an integrated circuit that contains MAC and PHY in one package. With the release kernel the hardware works fine, so the overall configuration is ok (jumpers).
I will verify wether the effective RGMII and delay settings, you mention, are equal in both driver versions.
>> Ok, let's proceed :)
> What PHY is being used?
> Is it using RGMII?
>
> If it looks like the PHY and the MAC are happy, just that frames are
> not being transferred between them, it could be RGMII delays.
>
> Andrew
>
next prev parent reply other threads:[~2020-06-03 18:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 19:30 [PATCH] lan743x: Added fixed link and RGMII support Roelof Berg
2020-05-29 21:30 ` Andrew Lunn
2020-06-01 18:51 ` David Miller
2020-06-03 14:52 ` [PATCH] lan743x: Added fixed link and RGMII support / BROKEN PATCH Roelof Berg
2020-06-03 15:59 ` Andrew Lunn
2020-06-03 16:33 ` [PATCH] lan743x: Added fixed link and RGMII support / debugging Roelof Berg
2020-06-03 18:06 ` Andrew Lunn
2020-06-03 18:31 ` Roelof Berg [this message]
2020-06-03 22:02 ` Roelof Berg
2020-06-03 16:36 ` Roelof Berg
2020-06-03 18:02 ` Andrew Lunn
[not found] ` <08FC216E-BBCA-40E6-8251-FA1EB3EF9F99@berg-solutions.de>
2020-06-03 15:10 ` [PATCH] lan743x: Added fixed link and RGMII support / Options for proceeding ? Roelof Berg
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=C69EECC3-5701-46FF-84E4-4F0AFDB52809@berg-solutions.de \
--to=rberg@berg-solutions.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®