[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4881796E12491D4BB15146FE0209CE643F5C8E99@DE02WEMBXB.internal.synopsys.com>
Date: Fri, 7 Jun 2013 12:37:24 +0000
From: Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To: Arnd Bergmann <arnd@...db.de>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Vineet Gupta <Vineet.Gupta1@...opsys.com>,
Mischa Jonker <Mischa.Jonker@...opsys.com>,
Grant Likely <grant.likely@...aro.org>,
Rob Herring <rob.herring@...xeda.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
"David S. Miller" <davem@...emloft.net>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>
Subject: Re: [PATCH] ethernet/arc/arc_emac - Add new driver
On 06/07/2013 04:13 PM, Arnd Bergmann wrote:
>>> I wonder if it would be better to name the directory "synopsys" or
>>> "designware" rather than "arc" now. Is there a chance that the same
>>> controller is used on non-arc CPUs?
>>
>> The thing is - "arc_emac" is a custom ARC's (that was implemented before
>> acquisition of ARC by Synopsys) IP (it's not an IC - just a part of CPU)
>> Ethernet controller that only exists in some legacy FPGA boards we
>> (ex-ARC and our customers) still use a lot in development process.
>>
>> Synopsys itself doesn't actively sell this device so there's no point in
>> putting ARC EMAC into Synopsys folder.
>>
>> And indeed we don't expect this device to be used with non-ARC CPU's.
I'm wondering if my clarification above makes sense and I may leave this
driver in "ethernet/arc" or you still prefer it to be under
"ethernet/synopsys"?
-Alexey
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists