From: jhs@mojatatu.com (Jamal Hadi Salim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] net: Add Keystone NetCP ethernet driver support
Date: Tue, 09 Sep 2014 07:44:09 -0400 [thread overview]
Message-ID: <540EE809.9020901@mojatatu.com> (raw)
In-Reply-To: <540DC00F.1080103@ti.com>
On 09/08/14 10:41, Santosh Shilimkar wrote:
>> The NetCP plugin module infrastructure use all the standard kernel
>> infrastructure and its very tiny.
So i found this manual here:
http://www.silica.com/fileadmin/02_Products/Productdetails/Texas_Instruments/SILICA_TI_66AK2E05-ds.pdf
Glad there is an open document!
There are a couple of ethernet switch chips I can spot there.
Can i control those with "bridge" or say "brctl" utilities?
I can see the bridge ports are exposed and i should be able to
control them via ifconfig or ip link. Thats what "standard
kernel infrastructure" means. Magic hidden in a driver is
not.
Take a look at recent netconf discussion (as well as earlier
referenced discussions):
http://vger.kernel.org/netconf-nf-offload.pdf
Maybe we can help providing you some direction?
The problem is it doesnt seem that the offload specs for
those other pieces are open? e.g how do i add an entry
to the L2 switch?
cheers,
jamal
WARNING: multiple messages have this Message-ID (diff)
From: Jamal Hadi Salim <jhs-jkUAjuhPggJWk0Htik3J/w@public.gmane.org>
To: Santosh Shilimkar
<santosh.shilimkar-l0cyMroinI0@public.gmane.org>,
David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
sandeep_n-l0cyMroinI0@public.gmane.org,
Benjamin LaHaise <bcrl-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
shrijeet Mukherjee
<shm-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR@public.gmane.org>
Subject: Re: [PATCH v2 0/3] net: Add Keystone NetCP ethernet driver support
Date: Tue, 09 Sep 2014 07:44:09 -0400 [thread overview]
Message-ID: <540EE809.9020901@mojatatu.com> (raw)
In-Reply-To: <540DC00F.1080103-l0cyMroinI0@public.gmane.org>
On 09/08/14 10:41, Santosh Shilimkar wrote:
>> The NetCP plugin module infrastructure use all the standard kernel
>> infrastructure and its very tiny.
So i found this manual here:
http://www.silica.com/fileadmin/02_Products/Productdetails/Texas_Instruments/SILICA_TI_66AK2E05-ds.pdf
Glad there is an open document!
There are a couple of ethernet switch chips I can spot there.
Can i control those with "bridge" or say "brctl" utilities?
I can see the bridge ports are exposed and i should be able to
control them via ifconfig or ip link. Thats what "standard
kernel infrastructure" means. Magic hidden in a driver is
not.
Take a look at recent netconf discussion (as well as earlier
referenced discussions):
http://vger.kernel.org/netconf-nf-offload.pdf
Maybe we can help providing you some direction?
The problem is it doesnt seem that the offload specs for
those other pieces are open? e.g how do i add an entry
to the L2 switch?
cheers,
jamal
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>,
David Miller <davem@davemloft.net>
Cc: 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, Benjamin LaHaise <bcrl@kvack.org>,
shrijeet Mukherjee <shm@cumulusnetworks.com>
Subject: Re: [PATCH v2 0/3] net: Add Keystone NetCP ethernet driver support
Date: Tue, 09 Sep 2014 07:44:09 -0400 [thread overview]
Message-ID: <540EE809.9020901@mojatatu.com> (raw)
In-Reply-To: <540DC00F.1080103@ti.com>
On 09/08/14 10:41, Santosh Shilimkar wrote:
>> The NetCP plugin module infrastructure use all the standard kernel
>> infrastructure and its very tiny.
So i found this manual here:
http://www.silica.com/fileadmin/02_Products/Productdetails/Texas_Instruments/SILICA_TI_66AK2E05-ds.pdf
Glad there is an open document!
There are a couple of ethernet switch chips I can spot there.
Can i control those with "bridge" or say "brctl" utilities?
I can see the bridge ports are exposed and i should be able to
control them via ifconfig or ip link. Thats what "standard
kernel infrastructure" means. Magic hidden in a driver is
not.
Take a look at recent netconf discussion (as well as earlier
referenced discussions):
http://vger.kernel.org/netconf-nf-offload.pdf
Maybe we can help providing you some direction?
The problem is it doesnt seem that the offload specs for
those other pieces are open? e.g how do i add an entry
to the L2 switch?
cheers,
jamal
next prev parent reply other threads:[~2014-09-09 11:44 UTC|newest]
Thread overview: 48+ 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 ` Santosh Shilimkar
2014-08-15 15:12 ` Santosh Shilimkar
2014-08-15 15:12 ` 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 ` Santosh Shilimkar
2014-08-15 15:12 ` Santosh Shilimkar
2014-08-15 15:12 ` Santosh Shilimkar
2014-08-15 15:12 ` [PATCH v2 2/3] net: Add " Santosh Shilimkar
2014-08-15 15:12 ` Santosh Shilimkar
2014-08-19 11:38 ` Jamal Hadi Salim
2014-08-19 11:38 ` Jamal Hadi Salim
2014-08-22 2:48 ` Stephen Hemminger
2014-08-22 2:48 ` Stephen Hemminger
2014-08-22 2:48 ` Stephen Hemminger
2014-08-22 2:48 ` Stephen Hemminger
2014-08-22 19:50 ` Santosh Shilimkar
2014-08-22 19:50 ` Santosh Shilimkar
2014-08-22 19:50 ` Santosh Shilimkar
2014-08-15 15:12 ` [PATCH v2 3/3] MAINTAINER: net: Add TI NETCP Ethernet driver entry Santosh Shilimkar
2014-08-15 15:12 ` Santosh Shilimkar
2014-08-15 15:12 ` Santosh Shilimkar
2014-08-21 23:36 ` [PATCH v2 0/3] net: Add Keystone NetCP ethernet driver support David Miller
2014-08-21 23:36 ` David Miller
2014-08-22 19:45 ` Santosh Shilimkar
2014-08-22 19:45 ` Santosh Shilimkar
2014-08-22 19:45 ` Santosh Shilimkar
2014-08-22 19:45 ` Santosh Shilimkar
2014-09-08 14:41 ` Santosh Shilimkar
2014-09-08 14:41 ` Santosh Shilimkar
2014-09-08 14:41 ` Santosh Shilimkar
2014-09-08 14:41 ` Santosh Shilimkar
2014-09-09 11:44 ` Jamal Hadi Salim [this message]
2014-09-09 11:44 ` Jamal Hadi Salim
2014-09-09 11:44 ` Jamal Hadi Salim
2014-09-09 15:19 ` Santosh Shilimkar
2014-09-09 15:19 ` Santosh Shilimkar
2014-09-09 15:19 ` Santosh Shilimkar
2014-09-10 11:33 ` Jamal Hadi Salim
2014-09-10 11:33 ` Jamal Hadi Salim
2014-09-10 11:33 ` Jamal Hadi Salim
2014-09-11 15:30 ` Santosh Shilimkar
2014-09-11 15:30 ` Santosh Shilimkar
2014-09-11 15:30 ` Santosh Shilimkar
2014-09-11 15:30 ` Santosh Shilimkar
2014-09-11 15:56 ` Santosh Shilimkar
2014-09-11 15:56 ` 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=540EE809.9020901@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.