From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Dinh Nguyen <dinh.linux@gmail.com>, <netdev@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>, <clabbe@baylibre.com>,
<Jose.Abreu@synopsys.com>, Dinh Nguyen <dinguyen@kernel.org>,
Marek Vasut <marex@denx.de>
Subject: Re: [BUG] net: stmmac: socfpga ethernet no longer working on linux-next
Date: Thu, 14 Jun 2018 08:38:58 +0100 [thread overview]
Message-ID: <63bfbeb4-ca90-cc8e-3b06-ea257a34a261@synopsys.com> (raw)
In-Reply-To: <CADhT+wewQKmqXDqBj4fk_zhJbQdSSK5LTneJGJ9je3tP2eVMDw@mail.gmail.com>
Hello,
On 13-06-2018 21:46, Dinh Nguyen wrote:
> Hi,
>
> The stmmac ethernet has stopped working in linux-next and linus/master
> branch(v4.17-11782-gbe779f03d563)
>
> It appears that the stmmac ethernet has stopped working after these 2 commits:
>
> 4dbbe8dde848 net: stmmac: Add support for U32 TC filter using Flexible RX Parser
> 5f0456b43140 net: stmmac: Implement logic to automatically select HW Interface
>
> If I move to this commit "565020aaeebf net: stmmac: Disable ACS
> Feature for GMAC >= 4", then the stmmac works again on SoCFPGA.
>
> I was following this thread:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.spinics.net_lists_netdev_msg502858.html&d=DwIBaQ&c=DPL6_X_6JkXFx7AXWqB0tg&r=yaVFU4TjGY0gVF8El1uKcisy6TPsyCl9uN7Wsis-qhY&m=fvPkLp2xlWolmIYwoFLmALhxlycg1w0UmxiYdT7qojc&s=aC4a2U3X_siDxSNz3c5OeadhEJWll31yP-oi5nNar94&e=
>
> Was wondering if there was a patch to fix dwmac-sun8i that the socfpga
> platform needs as well?
Probably. I will check and get back to you ASAP.
Thanks and Best Regards,
Jose Miguel Abreu
>
> Thanks,
> Dinh
next prev parent reply other threads:[~2018-06-14 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 20:46 [BUG] net: stmmac: socfpga ethernet no longer working on linux-next Dinh Nguyen
2018-06-14 7:38 ` Jose Abreu [this message]
2018-06-14 8:18 ` Jose Abreu
2018-06-14 10:59 ` Marek Vasut
2018-06-14 14:21 ` Dinh Nguyen
2018-06-14 15:23 ` Jose Abreu
2018-06-14 16:18 ` Dinh Nguyen
2018-06-15 14:58 ` Jose Abreu
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=63bfbeb4-ca90-cc8e-3b06-ea257a34a261@synopsys.com \
--to=jose.abreu@synopsys.com \
--cc=clabbe@baylibre.com \
--cc=davem@davemloft.net \
--cc=dinguyen@kernel.org \
--cc=dinh.linux@gmail.com \
--cc=marex@denx.de \
--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;
as well as URLs for NNTP newsgroup(s).