From: Mark Jackson <mpfj-list@mimc.co.uk>
To: David Miller <davem@davemloft.net>
Cc: mugunthanvnm@ti.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 0/3] Dual EMAC mode implementation of CPSW
Date: Fri, 12 Apr 2013 10:14:49 +0100 [thread overview]
Message-ID: <5167D089.3000105@mimc.co.uk> (raw)
In-Reply-To: <20130212.161538.1899836892271837177.davem@davemloft.net>
On 12/02/13 21:15, David Miller wrote:
> From: Mugunthan V N <mugunthanvnm@ti.com>
> Date: Tue, 12 Feb 2013 01:22:17 +0530
>
>> This patch series implements Dual EMAC mode implementation of CPSW
>> which acts as two standalone EMAC by segregating the switch using VIDs
>> and port VLAN
>>
>> Mugunthan V N (3):
>> driver: net: ethernet: davinci_cpdma: add support for directed packet
>> and source port detection
>> driver: net: ethernet: cpsw: make cpts as pointer
>> driver: net: ethernet: cpsw: dual emac interface implementation
>
> Series applied.
I can see that this series is now in the mainline kernel, but can anyone
give me some pointers on how to use it ?
First, I'd like to check that it's achieving what I think it does ...
namely to be able to access both eth0 and eth1 as separate Ethernet ports ?
If this assumption is correct, can anyone guide me as to how to setup my
dts file to allow the kernel to see both ports ?
If have been trying to get it going (see my posting [1]), but to no avail.
Any help would be greatly appreciated !!
[1] http://www.spinics.net/lists/linux-omap/msg89920.html
Regards
Mark JACKSON
WARNING: multiple messages have this Message-ID (diff)
From: mpfj-list@mimc.co.uk (Mark Jackson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Dual EMAC mode implementation of CPSW
Date: Fri, 12 Apr 2013 10:14:49 +0100 [thread overview]
Message-ID: <5167D089.3000105@mimc.co.uk> (raw)
In-Reply-To: <20130212.161538.1899836892271837177.davem@davemloft.net>
On 12/02/13 21:15, David Miller wrote:
> From: Mugunthan V N <mugunthanvnm@ti.com>
> Date: Tue, 12 Feb 2013 01:22:17 +0530
>
>> This patch series implements Dual EMAC mode implementation of CPSW
>> which acts as two standalone EMAC by segregating the switch using VIDs
>> and port VLAN
>>
>> Mugunthan V N (3):
>> driver: net: ethernet: davinci_cpdma: add support for directed packet
>> and source port detection
>> driver: net: ethernet: cpsw: make cpts as pointer
>> driver: net: ethernet: cpsw: dual emac interface implementation
>
> Series applied.
I can see that this series is now in the mainline kernel, but can anyone
give me some pointers on how to use it ?
First, I'd like to check that it's achieving what I think it does ...
namely to be able to access both eth0 and eth1 as separate Ethernet ports ?
If this assumption is correct, can anyone guide me as to how to setup my
dts file to allow the kernel to see both ports ?
If have been trying to get it going (see my posting [1]), but to no avail.
Any help would be greatly appreciated !!
[1] http://www.spinics.net/lists/linux-omap/msg89920.html
Regards
Mark JACKSON
next prev parent reply other threads:[~2013-04-12 9:14 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 19:52 [PATCH 0/3] Dual EMAC mode implementation of CPSW Mugunthan V N
2013-02-11 19:52 ` Mugunthan V N
2013-02-11 19:52 ` Mugunthan V N
2013-02-11 19:52 ` [PATCH 1/3] driver: net: ethernet: davinci_cpdma: add support for directed packet and source port detection Mugunthan V N
2013-02-11 19:52 ` Mugunthan V N
2013-02-11 19:52 ` Mugunthan V N
2013-02-11 19:52 ` [PATCH 2/3] driver: net: ethernet: cpsw: make cpts as pointer Mugunthan V N
2013-02-11 19:52 ` Mugunthan V N
2013-02-11 19:52 ` Mugunthan V N
2013-02-11 19:52 ` [PATCH 3/3] driver: net: ethernet: cpsw: dual emac interface implementation Mugunthan V N
2013-02-11 19:52 ` Mugunthan V N
2013-02-11 19:52 ` Mugunthan V N
[not found] ` <1360612340-9266-4-git-send-email-mugunthanvnm-l0cyMroinI0@public.gmane.org>
2013-02-18 13:36 ` Peter Korsgaard
2013-02-18 13:36 ` Peter Korsgaard
[not found] ` <87mwv1kaln.fsf-D6SC8u56vOOJDPpyT6T3/w@public.gmane.org>
2013-02-18 15:10 ` Mugunthan V N
2013-02-18 15:10 ` Mugunthan V N
2013-04-14 19:20 ` Mark Jackson
2013-04-14 19:20 ` Mark Jackson
2013-04-15 17:04 ` Mugunthan V N
2013-04-15 17:04 ` Mugunthan V N
2013-04-15 17:04 ` Mugunthan V N
2013-02-12 21:15 ` [PATCH 0/3] Dual EMAC mode implementation of CPSW David Miller
2013-02-12 21:15 ` David Miller
2013-04-12 9:14 ` Mark Jackson [this message]
2013-04-12 9:14 ` Mark Jackson
2013-04-14 19:16 ` Mark Jackson
2013-04-14 19:16 ` Mark Jackson
2013-04-15 17:07 ` Mugunthan V N
2013-04-15 17:07 ` Mugunthan V N
2013-04-15 17:07 ` Mugunthan V N
2013-04-15 17:28 ` Mark Jackson
2013-04-15 17:28 ` Mark Jackson
2013-04-15 17:34 ` Mugunthan V N
2013-04-15 17:34 ` Mugunthan V N
2013-04-15 17:34 ` Mugunthan V N
2013-04-15 18:00 ` Mark Jackson
2013-04-15 18:00 ` Mark Jackson
2013-04-16 11:09 ` Mark Jackson
2013-04-16 11:09 ` Mark Jackson
2013-04-18 16:01 ` Mark Jackson
2013-04-18 16:01 ` Mark Jackson
2013-04-22 14:07 ` Mark Jackson
2013-04-22 14:07 ` Mark Jackson
2013-04-22 17:01 ` Mugunthan V N
2013-04-22 17:01 ` Mugunthan V N
2013-04-22 17:01 ` Mugunthan V N
2013-04-23 5:11 ` Mark Jackson
2013-04-23 5:11 ` Mark Jackson
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=5167D089.3000105@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.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.