All of lore.kernel.org
 help / color / mirror / Atom feed
From: mlangsdo@redhat.com (Mark Langsdorf)
To: linux-arm-kernel@lists.infradead.org
Subject: Ethernet Briding broken on APM Mustang on v4.0-rc1
Date: Wed, 25 Feb 2015 07:55:44 -0600	[thread overview]
Message-ID: <54EDD460.8080909@redhat.com> (raw)
In-Reply-To: <20150225134534.GE12827@cbox>

On 02/25/2015 07:45 AM, Christoffer Dall wrote:
> Update, apologies for noise,
>
> On Wed, Feb 25, 2015 at 01:41:01PM +0100, Christoffer Dall wrote:
>> Hi,
>>
>> Configuring bridged networking on the APM Mustang platform doesn't work
>> on v4.0-rc1.  It works fine on v3.19-rc1.
>>
>> When adding the interface to the bridge I get this error:
>>
>> can't add eth0 to bridge br0: Invalid argument
>>
>> Has anyone else seen this?
>>
>> Other ARMv8 platforms don't seem to be affected by this.
>>
>
> It seems that on v4.0-rc1 the APM ethernet card no longer gets a mac
> address (or rather, it gets 00:00:00:00:...) so assigning it an
> appropriate address naturally does the trick.
>
> I have no idea which change caused this behavior though.

Did you update your firmware recently? The MAC address is
stored as a UEFI shell variable and pushed into ACPI/DTB
by the firmware. At one point in the development history,
the symbol that held it changed from RGMII_MAC0 to MAC0.

You can reset it by going into the UEFI shell and running:
set MAC0 aa:bb:cc:dd:ee:ff
replacing aa:bb:cc:dd:ee:ff with the MAC address.

--Mark Langsdorf

  reply	other threads:[~2015-02-25 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-25 12:41 Ethernet Briding broken on APM Mustang on v4.0-rc1 Christoffer Dall
2015-02-25 13:45 ` Christoffer Dall
2015-02-25 13:55   ` Mark Langsdorf [this message]
2015-02-25 14:54     ` Christoffer Dall

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=54EDD460.8080909@redhat.com \
    --to=mlangsdo@redhat.com \
    --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 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.