netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petko Manolov <petkan@nucleusys.com>
To: David Bilsby <d.bilsby@virgin.net>
Cc: Thor Thayer <thor.thayer@linux.intel.com>, netdev@vger.kernel.org
Subject: Re: Re: Altera TSE driver not working in 100mbps mode
Date: Thu, 17 Sep 2020 09:42:39 +0300	[thread overview]
Message-ID: <20200917064239.GA40050@p310> (raw)
In-Reply-To: <c8e4fc3a-0f40-45b6-d9c8-f292c3fdec9d@virgin.net>

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

  reply	other threads:[~2020-09-17  7:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 13:54 Altera TSE driver not working in 100mbps mode Petko Manolov
2019-12-03  9:29 ` Petko Manolov
2020-09-16 21:32   ` David Bilsby
2020-09-17  6:42     ` Petko Manolov [this message]
     [not found]       ` <9f312748-1069-4a30-ba3f-d1de6d84e920@virgin.net>
2020-09-18 17:14         ` Petko Manolov
2020-09-30 20:43           ` David Bilsby
2020-09-30 23:59             ` Andrew Lunn
2020-10-01  6:42               ` Petko Manolov
2020-10-01  6:39             ` Petko Manolov
2020-10-01  8:29               ` David Laight

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=20200917064239.GA40050@p310 \
    --to=petkan@nucleusys.com \
    --cc=d.bilsby@virgin.net \
    --cc=netdev@vger.kernel.org \
    --cc=thor.thayer@linux.intel.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).