From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
grant.likely@linaro.org, devicetree@vger.kernel.org,
sandeep_n@ti.com
Subject: Re: [PATCH v2 2/3] net: Add Keystone NetCP ethernet driver
Date: Fri, 22 Aug 2014 15:50:25 -0400 [thread overview]
Message-ID: <53F79F01.6090804@ti.com> (raw)
In-Reply-To: <20140821194838.32f2c3f1@uryu.home.lan>
On Thursday 21 August 2014 10:48 PM, Stephen Hemminger wrote:
> On Fri, 15 Aug 2014 11:12:41 -0400
> Santosh Shilimkar <santosh.shilimkar@ti.com> wrote:
>
>> NetCP driver has a plug-in module architecture where each of the NetCP
>> sub-modules exist as a loadable kernel module which plug in to the netcp
>> core. These sub-modules are represented as "netcp-devices" in the dts
>> bindings. It is mandatory to have the ethernet switch sub-module for
>> the ethernet interface to be operational. Any other sub-module like the
>> PA is optional.
>
> What are you doing to prevent/discourage proprietary binary only
> sub-modules?
>
Not sure if you mistook this infrastructure as a replacement for the
kernel module. The sub modules are traditional kernel modules that
just registers into the NetCP framework. Kernel module infrastructure
already discourages the proprietary binary only sub-modules.
Regards,
Santosh
next prev parent reply other threads:[~2014-08-22 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 15:12 [PATCH v2 0/3] net: Add Keystone NetCP ethernet driver support Santosh Shilimkar
2014-08-15 15:12 ` [PATCH v2 1/3] Documentation: dt: net: Add binding doc for Keystone NetCP ethernet driver Santosh Shilimkar
2014-08-15 15:12 ` [PATCH v2 2/3] net: Add " Santosh Shilimkar
2014-08-19 11:38 ` Jamal Hadi Salim
[not found] ` <1408115562-22487-3-git-send-email-santosh.shilimkar-l0cyMroinI0@public.gmane.org>
2014-08-22 2:48 ` Stephen Hemminger
2014-08-22 19:50 ` Santosh Shilimkar [this message]
2014-08-15 15:12 ` [PATCH v2 3/3] MAINTAINER: net: Add TI NETCP Ethernet driver entry Santosh Shilimkar
2014-08-21 23:36 ` [PATCH v2 0/3] net: Add Keystone NetCP ethernet driver support David Miller
[not found] ` <20140821.163612.282672926741753926.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2014-08-22 19:45 ` Santosh Shilimkar
[not found] ` <53F79DC5.8030003-l0cyMroinI0@public.gmane.org>
2014-09-08 14:41 ` Santosh Shilimkar
[not found] ` <540DC00F.1080103-l0cyMroinI0@public.gmane.org>
2014-09-09 11:44 ` Jamal Hadi Salim
2014-09-09 15:19 ` Santosh Shilimkar
[not found] ` <540F1A9A.1020309-l0cyMroinI0@public.gmane.org>
2014-09-10 11:33 ` Jamal Hadi Salim
[not found] ` <541036F0.2030001-jkUAjuhPggJWk0Htik3J/w@public.gmane.org>
2014-09-11 15:30 ` Santosh Shilimkar
2014-09-11 15:56 ` Santosh Shilimkar
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=53F79F01.6090804@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sandeep_n@ti.com \
--cc=stephen@networkplumber.org \
/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).