From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 66D37A00C5; Fri, 11 Feb 2022 15:44:47 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DACFB41144; Fri, 11 Feb 2022 15:44:46 +0100 (CET) Received: from mail-pj1-f52.google.com (mail-pj1-f52.google.com [209.85.216.52]) by mails.dpdk.org (Postfix) with ESMTP id 899C6410E5 for ; Fri, 11 Feb 2022 15:44:45 +0100 (CET) Received: by mail-pj1-f52.google.com with SMTP id v4so8303613pjh.2 for ; Fri, 11 Feb 2022 06:44:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=LNqBi0Yv+PZNlt8Rjt6FA/JgvosusB/IPemJLtXEeAw=; b=U5kgSawnXJCn3/+Mvy6+3BTys4ubZyUpbFPYP7laIW/RN+WTJWqNh1UhkkGmutDg/d M0XwPfAzCN2KMv/DW1LlaIkPcuB0Rly1VDgTatyEyPd8EcaUIv5JBXqRLtC3iemslzH8 y3ms68khyiUQF1Y3a+UepQ/JKRhytvYNAS+4aDAUhvGpsT5SR471eor3VTNipF2q1QvL so6ImccOzGZOMuQ619fb4TFxdnLVOkrOOcGATghMpj1DZ/HmrPncL8pJpMqiB9mOY55v aP3D+DdUhYXZmQTiqxpz5aXIGmGo7HWPeJmUABZ6UGKTTjtl0bR2w+7IXmEVZjAEmOaw GD8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=LNqBi0Yv+PZNlt8Rjt6FA/JgvosusB/IPemJLtXEeAw=; b=BD0Gzxn9TsxRwuykIVnIe0xwdQw9K+FT4uVtK65DNN+sckwlbYjpr55tNnmMjRTgm4 3SrisFZ1IVXsjyoTMJ3SUPiBbVrlvZrFciZ0ibuOah2is8JzslJKc6G9l/CDgpoecWuK Jmt6veyLgqsl8pDjTnJEeXmukOVaCfXzPU0Ibp4iKmzmueZHA0+zCcMWpKLXMVLY9gAd vbR+AmVaEZ8hYm6Ry1kOxB4BnOvvYq9vynqSLTxYg7mNdl+Xynbn6gStd1cQXfQtQH2s rs5KuNowvWMX37aZd2zv93zQp4EwCIMRCSej69WFbqY4xJnGL0c/+YAWh0L9tymtndUG XOTw== X-Gm-Message-State: AOAM533yJBQsz04LvZ0jo/zrobzOxfhHX2QaG6RBNVnnqqAoCEas2FyS xrPCI+z2D2VuX5jNnKEKV2kwKO7Ab+HiAtVa X-Google-Smtp-Source: ABdhPJzlnzeXDQg707C0kr7nnFRuIDHj4BsdFxuBodaQwSlbWR4hp3dzyBWc9CCkRK1F5obyOUZkTQ== X-Received: by 2002:a17:903:124c:: with SMTP id u12mr1940545plh.13.1644590684701; Fri, 11 Feb 2022 06:44:44 -0800 (PST) Received: from hermes.local (204-195-112-199.wavecable.com. [204.195.112.199]) by smtp.gmail.com with ESMTPSA id s19sm26666873pfu.34.2022.02.11.06.44.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Feb 2022 06:44:44 -0800 (PST) Date: Fri, 11 Feb 2022 06:44:41 -0800 From: Stephen Hemminger To: Morten =?UTF-8?B?QnLDuHJ1cA==?= Cc: "Bly, Mike" , Subject: Re: e1000 forced 1G support? Message-ID: <20220211064441.7cd12699@hermes.local> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D86E87@smartserver.smartshare.dk> References: <98CBD80474FA8B44BF855DF32C47DC35D86E87@smartserver.smartshare.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Fri, 11 Feb 2022 09:57:31 +0100 Morten Br=C3=B8rup wrote: > > From: Bly, Mike [mailto:mbly@ciena.com]=20 > > Sent: Friday, 11 February 2022 02.30 > >=20 > > Hello, > > > > This is in regards to the DPDK E1000 driver used for the i350 [8086:152= 1] NIC. > > > > I am looking to see if we can get forced speed =3D=3D 1000Mb (1Gb) supp= ort working on this NIC. The current DPDK driver does not appear to have su= pport for forcing the NIC to 1G (1000M) speed. It only supports setting 100= M and 10M. Is there a reason for this? Refer to:=C2=A0e1000_phy_force_speed= _duplex_setup() in drivers/net/e1000/base/e1000_phy.c. > > > > Based on my reading=C2=A0of ethernet-controller-i350-datasheet.pdf it w= ould seem we should be able to force the speed to 1G. However, even after "= updating" the above mentioned function to try and support a 1G forced speed= , the only way we can get two of these NICs to link up to each other at 1G,= is to set the port to auto-neg. We can certainly force speed on one link t= o 100M or 10M and the other NIC will link up, but no luck for 1G, regardles= s of whether we have one or both sides in a forced speed vs. auto-neg mode. > > > > Is there a limitation I missed in the PDF perhaps? =20 >=20 > Hi Mike, >=20 > Auto-negotiation is a *requirement* for 1 Gbps according to the IEEE 802.= 3 Ethernet standard, so the way to force 1 Gbps is: Enable auto-negotiation= and only advertise 1 Gbps. >=20 > In other words: You cannot establish a 1 Gbps link without auto-neg. >=20 >=20 > Med venlig hilsen / Kind regards, > -Morten Br=C3=B8rup >=20 Also, check your cable. 1G requires all 4 wire pairs to be connected. But 1= 00M can get by with 2 pairs