From: Corinna Vinschen <vinschen@redhat.com>
To: Richard Tresidder <rtresidd@electromag.com.au>
Cc: Jakub Kicinski <kuba@kernel.org>, netdev@vger.kernel.org
Subject: Re: STMMAC Ethernet Driver support
Date: Mon, 11 Dec 2023 11:03:29 +0100 [thread overview]
Message-ID: <ZXbecbaUnTwiX3l1@calimero.vinschen.de> (raw)
In-Reply-To: <f47b0230-1513-4a81-9d78-3f092b979c48@electromag.com.au>
On Dec 11 17:23, Richard Tresidder wrote:
>
> > Richard Tresidder
> >
> >
> > On 9/12/2023 3:06 pm, Richard Tresidder wrote:
> > > On 9/12/2023 2:12 am, Jakub Kicinski wrote:
> > > > On Fri, 8 Dec 2023 14:03:25 +0800 Richard Tresidder wrote:
> > > > > I've looked through the diffset 6.3.3 >>> 6.6.3 on the driver
> > > > > drivers\net\ethernet\stmicro\stmmac
> > > > > But nothing is jumping out at me.
> > > > >
> > > > > I could use a pointer as to where to look to start tracing this.
> > > > Bisection is good way to zero in on the bad change if you don't
> > > > have much hard to rebase code in your tree.
> > > >
> > > > Otherwise you can dump the relevant registers and the descriptors
> > > > (descriptors_status file in debugfs) and see if driver is doing
> > > > anything differently on the newer kernel?
> > > >
> > > Thanks Jakub
> > > Yep I think I'll have to start bisecting things on Monday.
> > > Luckily to work through this I shouldn't have to merge very much.
> > > Have a great weekend
> > >
> > > Cheers
> > > Richard Tresidder
> > >
> > Hi Jakub
> > Ok the bad commit is the following:
> > ************************************
> > 6b2c6e4a938fece9b539c8085f21d17c5e6eb9de is the first bad commit
> > commit 6b2c6e4a938fece9b539c8085f21d17c5e6eb9de
> > Author: Corinna Vinschen <vinschen@redhat.com>
> > Date: Mon Apr 17 21:28:45 2023 +0200
> >
> > net: stmmac: propagate feature flags to vlan
> >
> > stmmac_dev_probe doesn't propagate feature flags to VLANs. So
> > features
> > like offloading don't correspond with the general features and it's
> > not
> > possible to manipulate features via ethtool -K to affect VLANs.
> >
> > Propagate feature flags to vlan features. Drop TSO feature because
> > it does not work on VLANs yet.
> >
> > Signed-off-by: Corinna Vinschen <vinschen@redhat.com>
> > Link:
> > https://lore.kernel.org/r/20230417192845.590034-1-vinschen@redhat.com
> > Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> >
> > drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> > ****************************************
> > From back in the work for 6.4-rc1
> >
> > Theres a single line addition approx line 7506
> > drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> >
> > ndev->vlan_features |= ndev->features;
This is missing the 2nd line
ndev->vlan_features &= ~NETIF_F_TSO;
I assume that another flag or two have to be dropped from being
propagated as well. That may depend on the platform, just like the
feature flags depend on STMMAC_VLAN_TAG_USED, for instance.
I'm sorry, but I'm not working on stmmac anymore. Can you perhaps test
removing flags from vlan_features and see what actual flag is breaking
your scenario?
Other than that, maybe reverting the patch is the better option and the
vlan_feature flags should be set explicitely in the various
platform-specific code.
Corinna
next prev parent reply other threads:[~2023-12-11 10:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 6:03 STMMAC Ethernet Driver support Richard Tresidder
2023-12-08 18:12 ` Jakub Kicinski
2023-12-09 7:06 ` Richard Tresidder
2023-12-11 9:13 ` Richard Tresidder
2023-12-11 9:23 ` Richard Tresidder
2023-12-11 10:03 ` Corinna Vinschen [this message]
2023-12-12 4:13 ` Richard Tresidder
2023-12-12 6:49 ` Richard Tresidder
2023-12-11 16:16 ` Andrew Lunn
2023-12-12 3:57 ` Richard Tresidder
2023-12-12 9:27 ` Serge Semin
2023-12-13 4:55 ` Richard Tresidder
2023-12-13 9:17 ` Andrew Lunn
2023-12-13 10:15 ` Richard Tresidder
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=ZXbecbaUnTwiX3l1@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rtresidd@electromag.com.au \
/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).