[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8910993f-f5ca-259c-c42b-207781a4ad51@synopsys.com>
Date: Sat, 10 Dec 2016 10:13:57 +0800
From: Jie Deng <Jie.Deng1@...opsys.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>,
Florian Fainelli <f.fainelli@...il.com>
CC: David Miller <davem@...emloft.net>,
Joao Pinto <Joao.Pinto@...opsys.com>,
Giuseppe CAVALLARO <peppe.cavallaro@...com>,
<lars.persson@...s.com>, <rabin.vincent@...s.com>,
netdev <netdev@...r.kernel.org>, <CARLOS.PALMINHA@...opsys.com>
Subject: Re: Synopsys Ethernet QoS
On 2016/12/10 8:16, Andy Shevchenko wrote:
> On Sat, Dec 10, 2016 at 12:52 AM, Florian Fainelli <f.fainelli@...il.com> wrote:
>
>> It's kind of sad that customers of that IP (stmmac, amd-xgbe, sxgbe)
>> did
>> actually pioneer the upstreaming effort, but it is good to see people
>> from Synopsys willing to fix that in the future.
> Wait, you would like to tell that we have more than 2 drivers for the
> same (okay, same vendor) IP?!
> It's better to unify them earlier, than have n+ copies.
>
> P.S. Though, I don't see how sxgbe got in the list. First glance on
> the code doesn't show similarities.
Glance on sxgbe_reg.h the register seems from Synopsys XGMAC IP... Probably,
amd-xgbe and sxgbe targeted the same IP
Powered by blists - more mailing lists