From: Eric Nelson <eric@nelint.com>
To: Henri Roosen <henri.roosen@ginzinger.com>,
fugang.duan@nxp.com,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: commit-3ac72b7b63d5 breaks networking on iMX28
Date: Fri, 21 Oct 2016 06:39:35 -0700 [thread overview]
Message-ID: <fea86fa6-d74a-43ff-cf60-0d375336a5ba@nelint.com> (raw)
In-Reply-To: <bc6aa851-3f52-2274-47dc-4933662648a1@ginzinger.com>
Hi Henri,
On 10/21/2016 02:19 AM, Henri Roosen wrote:
> Hi,
>
> Unfortunately commit-3ac72b7b63d5 "net: fec: align IP header in
> hardware" breaks networking on an iMX28 system.
>
> The commit seems valid for iMX6, where it is tested okay and solves the
> unaligned accesses.
>
> On iMX28 I still see unaligned accesses and networking is broken. Can
> anyone confirm this?
>
Reading the i.MX28 reference manual, it appears that this SoC doesn't
have the RACC bit, and I missed removal of the FEC_QUIRK_HAS_RACC flag.
Can you try with this patch?
diff --git a/drivers/net/ethernet/freescale/fec_main.c
b/drivers/net/ethernet/freescale/fec_main.c
index 692ee24..db5eee9 100644
--- a/drivers/net/ethernet/freescale/fec_main.c
+++ b/drivers/net/ethernet/freescale/fec_main.c
@@ -96,7 +96,7 @@ static struct platform_device_id fec_devtype[] = {
}, {
.name = "imx28-fec",
.driver_data = FEC_QUIRK_ENET_MAC | FEC_QUIRK_SWAP_FRAME |
- FEC_QUIRK_SINGLE_MDIO | FEC_QUIRK_HAS_RACC,
+ FEC_QUIRK_SINGLE_MDIO,
}, {
.name = "imx6q-fec",
.driver_data = FEC_QUIRK_ENET_MAC | FEC_QUIRK_HAS_GBIT |
Please advise,
Eric
next prev parent reply other threads:[~2016-10-21 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 9:19 commit-3ac72b7b63d5 breaks networking on iMX28 Henri Roosen
2016-10-21 10:55 ` Fabio Estevam
2016-10-21 11:09 ` Henri Roosen
2016-10-21 13:39 ` Eric Nelson [this message]
2016-10-21 13:43 ` Fabio Estevam
2016-10-21 13:48 ` Eric Nelson
2016-10-21 13:46 ` Eric Nelson
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=fea86fa6-d74a-43ff-cf60-0d375336a5ba@nelint.com \
--to=eric@nelint.com \
--cc=fugang.duan@nxp.com \
--cc=henri.roosen@ginzinger.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