[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ca521df880b08225cb34214e3ef0fc2c@cheny.fr>
Date: Thu, 05 Sep 2013 08:23:12 +0200
From: yves@...ny.fr
To: Ethan Tuttle <ethan@...antuttle.com>
Cc: Willy Tarreau <w@....eu>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Lior Amsalem <alior@...vell.com>,
Gregory Clement <gregory.clement@...e-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
Jochen De Smet <jochen.armkernel@...hnim.org>,
Peter Sanford <psanford@...rbuy.io>,
Ryan Press <ryan@...sslab.us>,
Simon Guinot <simon.guinot@...uanux.org>, vdonnefort@...ie.com,
stable@...r.kernel.org
Subject: Re: [PATCH] net: mvneta: properly disable HW PHY polling and ensure
adjust_link() works
Hi Willy,
i would be interested too !
thx
Yves
Le 2013-09-05 07:22, Ethan Tuttle a écrit :
> Understood. Ultimately, I'll use this board as a router, and stable
> mac addresses would be better than random. So I would be interested
> to try your atag -> device tree patches. Have they been posted
> somewhere I can find them?
>
> Thanks Willy.
>
> Ethan
>
> On Wed, Sep 4, 2013 at 10:12 PM, Willy Tarreau <w@....eu> wrote:
>> Hi,
>>
>> On Wed, Sep 04, 2013 at 09:14:23PM -0700, Ethan Tuttle wrote:
>>> Just booted with the patch on my Mirabox. Both interfaces work!
>>> Thank you Thomas.
>>>
>>> One remaining issue is that the interface which uBoot didn't
>>> configure
>>> is still getting a random mac address:
>>>
>>> mvneta d0070000.ethernet eth0: Using hardware mac address
>>> f0:ad:4e:01:dc:97
>>> mvneta d0074000.ethernet eth1: Using random mac address
>>> d2:35:dd:c8:99:48
>>>
>>> This is on 3.11 plus Thomas' patch, which includes the previous fix
>>> to
>>> "read MAC address from hardware when available". Perhaps that fix
>>> isn't working with the phylib?
>>
>> No this is unrelated. The MAC isn't configured by the boot loader when
>> the NIC is not used. U-boot only passes it as a non-standard ATAG. I
>> have some patches to reinject the non-standard atags into the device
>> tree if you absolutely need this, but they're not suited for mainline
>> inclusion from what I understood last time I proposed them (they use
>> a marvell-specific atag header).
>>
>> Regards,
>> Willy
>>
--
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