On 15/07/13 13:45, Mugunthan V N wrote: > On 7/13/2013 12:55 AM, Mark Jackson wrote: >> On 12/07/13 19:35, Mugunthan V N wrote: >>> On 7/12/2013 7:27 PM, Mark Jackson wrote: >> [snip] >> >>>> Just to update this (old) thread ... >>>> >>>> I can still confirm that *without* the above patch, I am *unable* to use both network >>>> ports on our AM335x board. >>>> >> [snip] >> >>>> So I'm not sure what's wrong, but it's *definitely* not correct. >>>> >>>> >>> I am sure that current code in mainline works for Dual EMAC. I can test it >>> again and share the images with you if are interested. But had tested with DHCP >>> on both the interfaces. >> Hmmm ... well it's not working for me. What hardware are you testing it on ? >> >> I tried DHCP to start with, and switched to static IP when that failed. >> Then I recalled this patch and re-applied it ... hey presto !! >> >> Markus, are you still using this patch ? >> > Today I have tested the Dual EMAC on my am335x-evmsk and its working fine with > net/master branch. > I had 3 patches additional to net/master in which two for basic boot of EVMsk > and one for enabling Dual EMAC. I had pushed the branch in the below repo > repo: > git://git.ti.com/~mugunthanvnm/ti-linux-kernel/mugunth-connectivity-linux-feature-tree.git > branch: dual-emac Okay ... I can't test that at the moment as I can only boot from MMC as there's currently no support for MMC booting in the mainline kernel. So ... the code works for you, but not for me. I guess the other difference is that I'm not using the same PHY (we use a 10/100 SMSC 8710A, not the GbE Atheros part). Could that make any difference ? Markus, are you still seeing the same issue ? What PHY are you using ? Cheers Mark J. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html