From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: byungho an <bh74an@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
peppe.cavallaro@st.com, deepak.silki@st.com,
francesco.virlinzi@st.com, eilong@broadcom.com,
alexander.h.duyck@intel.com, bhutchings@solarflare.com,
linville@tuxdriver.com, wey-ty.w.guy@intel.com, coelho@ti.com,
e.wahlig@samsung.com, aditya.ps@samsung.com, ihlee215@gmail.com
Subject: Re: Regarding ethernet directory between IP and SoC chip vendor.
Date: Thu, 20 Sep 2012 01:35:57 -0700 [thread overview]
Message-ID: <1348130157.2006.87.camel@jtkirshe-mobl> (raw)
In-Reply-To: <CAG4h5ywgCS0n8t70uUNmSOVhKBPkOLeVLaO+D4tYfUT2qN7qTg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]
On Wed, 2012-09-19 at 21:39 +0900, byungho an wrote:
> 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
A lot of thought went into how to organize all the Ethernet drivers, and
after much discussion, it seemed best to organize the drivers by the
manufacturer rather than by who was supporting/writing the driver. The
reason being is that the manufacturer of the silicon was not going to
change as frequently as the driver supporters. We did not want to have
to change the location of a driver every time a company was bought.
I personally am open to suggestions on improving the directory structure
so if have an idea on how to improve the directory structure please
provide a patch. Keep in mind, that drivers can not keep moving because
some company bought another company.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-09-20 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 12:39 Regarding ethernet directory between IP and SoC chip vendor byungho an
2012-09-20 8:35 ` Jeff Kirsher [this message]
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=1348130157.2006.87.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=aditya.ps@samsung.com \
--cc=alexander.h.duyck@intel.com \
--cc=bh74an@gmail.com \
--cc=bhutchings@solarflare.com \
--cc=coelho@ti.com \
--cc=davem@davemloft.net \
--cc=deepak.silki@st.com \
--cc=e.wahlig@samsung.com \
--cc=eilong@broadcom.com \
--cc=francesco.virlinzi@st.com \
--cc=ihlee215@gmail.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
--cc=wey-ty.w.guy@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).