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=-5.1 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 3E378C43461 for ; Thu, 17 Sep 2020 07:03:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C1F8C21D1B for ; Thu, 17 Sep 2020 07:03:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=nucleusys.com header.i=@nucleusys.com header.b="Und5kiPl" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726183AbgIQHDd (ORCPT ); Thu, 17 Sep 2020 03:03:33 -0400 Received: from lan.nucleusys.com ([92.247.61.126]:56520 "EHLO zztop.nucleusys.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726310AbgIQHCo (ORCPT ); Thu, 17 Sep 2020 03:02:44 -0400 X-Greylist: delayed 1198 seconds by postgrey-1.27 at vger.kernel.org; Thu, 17 Sep 2020 03:02:43 EDT DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=nucleusys.com; s=x; h=In-Reply-To:Content-Type:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=s/zX2WJfzeffLweLiV/sKRa73szTthE7Wojt7KGvJvU=; b=Und5kiPlLrhyocqNNJRZRUkA9c mFeRIkY4CoqHI267/+CGIrvervkM6JlPf4SVnTSshfS3uujtudWl/JD/txPrXTWV+WqNxEJIm0hMd XK64SaGsdt65TUOWgY63D69vlpq+KU81V4o3nMVi2pa5B15fFSel11h4o8W8gNeZYJH0=; Received: from 78-83-68-78.spectrumnet.bg ([78.83.68.78] helo=p310) by zztop.nucleusys.com with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kIncs-0006zN-Q0; Thu, 17 Sep 2020 09:42:39 +0300 Date: Thu, 17 Sep 2020 09:42:39 +0300 From: Petko Manolov To: David Bilsby Cc: Thor Thayer , netdev@vger.kernel.org Subject: Re: Re: Altera TSE driver not working in 100mbps mode Message-ID: <20200917064239.GA40050@p310> Mail-Followup-To: David Bilsby , Thor Thayer , netdev@vger.kernel.org References: <20191127135419.7r53qw6vtp747x62@p310> <20191203092918.52x3dfuvnryr5kpx@carbon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On 20-09-16 22:32:03, David Bilsby wrote: > Hi > > Would you consider making the PhyLink modifications to the Altera TSE driver > public as this would be very useful for a board we have which uses an SFP PHY > connected to the TSE core via I2C. Currently we are using a fibre SFP and > fixing the speed to 1G but would really like to be able to use a copper SFP > which needs to do negotiation. Well, definitely yes. The driver isn't 100% finished, but it mostly works. One significant downside is the kernel version i had to port it to: 4.19. IIRC there is API change so my current patches can't be applied to 5.x kernels. Also, i could not finish the upstreaming as the customer device i worked on had to be returned. However, given access to Altera TSE capable device (which i don't have atm), running a recent kernel, i'll gladly finish the upstreaming. cheers, Petko