From: Jiri Pirko <jpirko@redhat.com>
To: "Sebastian Pöhn" <sebastian.belden@googlemail.com>
Cc: Linux Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] gianfar: fix bug caused by 87c288c6e9aa31720b72e2bc2d665e24e1653c3e
Date: Tue, 26 Jul 2011 12:46:00 +0200 [thread overview]
Message-ID: <20110726104559.GA2078@minipsycho.brq.redhat.com> (raw)
In-Reply-To: <1311674593.17190.7.camel@DENEC1DT0191>
Tue, Jul 26, 2011 at 12:03:13PM CEST, sebastian.belden@googlemail.com wrote:
>commit 87c288c6e9aa31720b72e2bc2d665e24e1653c3e "gianfar: do vlan cleanup" has two issues:
># permutation of rx and tx flags
># enabling vlan tag insertion by default (this leads to unusable connections on some configurations)
How so? What's causing that?
>
>If VLAN insertion is requested (via ethtool) it will be set at an other point ...
>
>Signed-off-by: Sebastian Poehn <sebastian.poehn@belden.com>
>---
>
> drivers/net/gianfar.c | 6 +-----
> 1 files changed, 1 insertions(+), 5 deletions(-)
>
>diff --git a/drivers/net/gianfar.c b/drivers/net/gianfar.c
>index 835cd25..2659daa 100644
>--- a/drivers/net/gianfar.c
>+++ b/drivers/net/gianfar.c
>@@ -388,12 +388,8 @@ static void gfar_init_mac(struct net_device *ndev)
> if (priv->hwts_rx_en)
> rctrl |= RCTRL_PRSDEP_INIT | RCTRL_TS_ENABLE;
>
>- /* keep vlan related bits if it's enabled */
>- if (ndev->features & NETIF_F_HW_VLAN_TX)
>- rctrl |= RCTRL_VLEX | RCTRL_PRSDEP_INIT;
>-
> if (ndev->features & NETIF_F_HW_VLAN_RX)
>- tctrl |= TCTRL_VLINS;
>+ rctrl |= RCTRL_VLEX | RCTRL_PRSDEP_INIT;
>
> /* Init rctrl based on our settings */
> gfar_write(®s->rctrl, rctrl);
>
>
If you really need that to be done, you should remove NETIF_F_HW_VLAN_TX
from features (not hw_features) (never add it).
next prev parent reply other threads:[~2011-07-26 10:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 10:03 [PATCH] gianfar: fix bug caused by 87c288c6e9aa31720b72e2bc2d665e24e1653c3e Sebastian Pöhn
2011-07-26 10:46 ` Jiri Pirko [this message]
2011-07-26 11:13 ` Sebastian Pöhn
2011-07-26 12:04 ` Jiri Pirko
2011-07-26 12:21 ` Sebastian Pöhn
2011-07-28 5:43 ` David Miller
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=20110726104559.GA2078@minipsycho.brq.redhat.com \
--to=jpirko@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sebastian.belden@googlemail.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).