From: Andrew Lunn <andrew@lunn.ch>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: Willy Tarreau <w@1wt.eu>,
linux-kernel@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antoine Tenart <antoine.tenart@bootlin.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>,
Yelena Krivosheev <yelena@marvell.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
netdev@vger.kernel.org
Subject: Re: CRC errors between mvneta and macb
Date: Mon, 22 Oct 2018 20:19:18 +0200 [thread overview]
Message-ID: <20181022181918.GF24112@lunn.ch> (raw)
In-Reply-To: <31385a3b-2196-94d0-7f4f-52e37ee07a28@sorico.fr>
> I dug more on the subject, and I think I found what Marvell's PHY/MAC
> doesn't like.
Hi Richard
What PHY is being used?
> After analyzing the ethernet frame on the Davicom PHY's output (pin
> TX+), I find out that the FCS errors occurs when the ethernet preamble
> is longer than 56bits. (something like 58 or 60 bits)
Some Marvell PHYs have a register bit which might be of interest: Page
2, register 16, bit 6.
0 = Pad odd nibble preambles in copper receive packets.
1 = Pass as is and do not pad odd nibble preambles in
Andrew
next prev parent reply other threads:[~2018-10-22 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 15:15 CRC errors between mvneta and macb Richard Genoud
2018-10-19 15:44 ` Willy Tarreau
2018-10-22 6:51 ` Richard Genoud
2018-10-22 15:15 ` Richard Genoud
2018-10-22 16:34 ` Willy Tarreau
2018-10-23 6:56 ` Richard Genoud
2018-10-22 18:19 ` Andrew Lunn [this message]
2018-10-23 6:58 ` Richard Genoud
2018-10-23 12:37 ` Richard Genoud
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=20181022181918.GF24112@lunn.ch \
--to=andrew@lunn.ch \
--cc=antoine.tenart@bootlin.com \
--cc=gregory.clement@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=richard.genoud@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=w@1wt.eu \
--cc=yelena@marvell.com \
/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;
as well as URLs for NNTP newsgroup(s).