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: Mon, 15 Apr 2013 18:28:25 +0100 [thread overview]
Message-ID: <516C38B9.50904@mimc.co.uk> (raw)
In-Reply-To: <516C33D2.4050105@ti.com>
On 15/04/13 18:07, Mugunthan V N wrote:
> On 4/15/2013 12:46 AM, Mark Jackson wrote:
<snip>
>>
>> Notice that at the end, the nfs link appears to come back "ok", but
>> the "ps" command never completes.
>>
>> Any ideas of what's going on ?
>
> I have tried ping on both the interface fine. Will verify with ps again
> later in this week.
> Can you provide below details details
> - Are you using EVMsk or custom build EVM?
This is a custom board (based on the BeagleBone design) with dual
Ethernet, NAND, NOR and FRAM.
The dual emac thing is (one of) the last things to get signed off, so
I'm willing to assist in tracking this down.
Regards
Mark J.
next prev parent reply other threads:[~2013-04-15 17:28 UTC|newest]
Thread overview: 20+ 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 ` [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 ` [PATCH 2/3] driver: net: ethernet: cpsw: make cpts as pointer Mugunthan V N
2013-02-11 19:52 ` [PATCH 3/3] driver: net: ethernet: cpsw: dual emac interface implementation Mugunthan V N
2013-02-18 13:36 ` Peter Korsgaard
2013-02-18 15:10 ` Mugunthan V N
2013-04-14 19:20 ` Mark Jackson
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-04-12 9:14 ` Mark Jackson
2013-04-14 19:16 ` Mark Jackson
2013-04-15 17:07 ` Mugunthan V N
2013-04-15 17:28 ` Mark Jackson [this message]
2013-04-15 17:34 ` Mugunthan V N
2013-04-15 18:00 ` Mark Jackson
2013-04-16 11:09 ` Mark Jackson
2013-04-18 16:01 ` Mark Jackson
2013-04-22 14:07 ` Mark Jackson
2013-04-22 17:01 ` Mugunthan V N
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=516C38B9.50904@mimc.co.uk \
--to=mpfj-list@mimc.co.uk \
--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 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).