lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 19 Jul 2013 20:07:00 +0200
From:	Markus Brunner <systemprogrammierung.brunner@...il.com>
To:	Mugunthan V N <mugunthanvnm@...com>
Cc:	Mark Jackson <mpfj-list@...flow.co.uk>, netdev@...r.kernel.org,
	davem@...emloft.net, linux-arm-kernel@...ts.infradead.org,
	linux-omap@...r.kernel.org
Subject: Re: [PATCH] remove vlan tags in CPSW dual emac mode

On Mon, Jul 15, 2013 at 7:02 PM, Mugunthan V N <mugunthanvnm@...com> wrote:
> On 7/15/2013 9:20 PM, Mark Jackson wrote:
>> 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.

I can confirm that. Windows won't strip away the vlan header like linux does.

[snip]
>>>> Markus, are you still using this patch ?

yes.

>>>>
>>> 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

I tested it and it has the same problem as with 3.9 - 3.11-rc1.

>> 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 ?

I', using a Micrel ksz8895mq, which is actually a switch, however one
phy is connected directly, so bootstrapping can work and even if I
don't enable the switch I have the same issue on that port. I doubt
the phy will change anything.

Regards,
Markus
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists