netdev - Regarding ethernet directory between IP and SoC chip vendor.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAG4h5ywgCS0n8t70uUNmSOVhKBPkOLeVLaO+D4tYfUT2qN7qTg@mail.gmail.com>
Date:	Wed, 19 Sep 2012 21:39:47 +0900
From:	byungho an <bh74an@...il.com>
To:	netdev@...r.kernel.org
Cc:	davem@...emloft.net, peppe.cavallaro@...com, deepak.silki@...com,
	francesco.virlinzi@...com, jeffrey.t.kirsher@...el.com,
	eilong@...adcom.com, alexander.h.duyck@...el.com,
	bhutchings@...arflare.com, linville@...driver.com,
	wey-ty.w.guy@...el.com, coelho@...com, e.wahlig@...sung.com,
	aditya.ps@...sung.com, ihlee215@...il.com
Subject: Regarding ethernet directory between IP and SoC chip vendor.

Hi all,

I have one suggestion for ethernet dir.
Currently It is well-defined and good for management.

But if IP vendor is different from SoC vender, It is a bit confusing
to guess dir name.
For example, stmmac is using Synopsys dwmac.
In this case, if another SoC vendors try to use Synopsys IP, they
sould make their own dir under the their name? Even the IP is same...

If there is common dir of IP vendor, It would be more clear.
If that, other SoC vendors that try to use the IP can make their own
directory and drivers intuitionally.

What do you think about it?
I want to exchange opinion and find a resonable and rational way.

Thank you.
Andy
--
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