From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AA5DFC64E7A for ; Tue, 1 Dec 2020 13:59:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 66C46217A0 for ; Tue, 1 Dec 2020 13:59:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391275AbgLAN7G (ORCPT ); Tue, 1 Dec 2020 08:59:06 -0500 Received: from vps0.lunn.ch ([185.16.172.187]:59784 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388079AbgLAN7F (ORCPT ); Tue, 1 Dec 2020 08:59:05 -0500 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1kk6Ag-009hEx-LW; Tue, 01 Dec 2020 14:58:22 +0100 Date: Tue, 1 Dec 2020 14:58:22 +0100 From: Andrew Lunn To: Peter Vollmer Cc: Tobias Waldekranz , Network Development Subject: Re: dsa/mv88e6xxx: leaking packets on MV88E6341 switch Message-ID: <20201201135822.GB2290587@lunn.ch> References: <20200930191956.GV3996795@lunn.ch> <20201001062107.GA2592@fido.de.innominate.com> <87y2in94o7.fsf@waldekranz.com> <20201126222359.GO2075216@lunn.ch> <20201201090041.GB6059@unassigned-hostname.unassigned-domain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201201090041.GB6059@unassigned-hostname.unassigned-domain> Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hi Peter > Maybe I can get some information from our support if > DSA_TAG_PROTO_EDSA is supported for the port config (0x4) register > on the 6341 switch after all or if it should be omitted. It would be nice to hear what Marvell says about this. It does seem an odd thing to remove, so it could be a documentation issue. Andrew