From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, khilman@baylibre.com
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux.amoon@gmail.com,
ottuzzi@gmail.com, narmstrong@baylibre.com,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH 0/1] ARM: dts: meson8b: persistent MAC address for Odroid-C1
Date: Mon, 12 Aug 2019 19:50:03 +0200 [thread overview]
Message-ID: <20190812175004.24943-1-martin.blumenstingl@googlemail.com> (raw)
This series makes Odroid-C1 use the MAC address which is programmed into
the eFuse.
build-time dependencies:
none
runtime dependencies (without these a random MAC address is assigned,
just like before these patches), both are already part of -next:
- "nvmem: meson-mx-efuse: allow reading data smaller than word_size"
from [1]
- "net: stmmac: manage errors returned by of_get_mac_address()" from [1]
Changes since v1 at [2]:
- only add the nvmem cell to meson8b-odroidc1.dts as suggested by Neil.
It turns out that neither MXQ and EC-100 have the MAC address in eFuse
(which means only 1/3 boards has it at the given eFuse offset, so it's
not worth having it the common .dtsi)
Kevin: you already have v1 of this series in your tree. Feel free to
replace the two patches from v1 with this single one.
[0] https://patchwork.kernel.org/patch/11062659/
[1] https://patchwork.kernel.org/patch/11062657/
[2] https://patchwork.kernel.org/cover/11062663/
Martin Blumenstingl (1):
ARM: dts: meson8b: odroidc1: use the MAC address stored in the eFuse
arch/arm/boot/dts/meson8b-odroidc1.dts | 9 +++++++++
1 file changed, 9 insertions(+)
--
2.22.0
WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, khilman@baylibre.com
Cc: narmstrong@baylibre.com, ottuzzi@gmail.com,
linux-kernel@vger.kernel.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] ARM: dts: meson8b: persistent MAC address for Odroid-C1
Date: Mon, 12 Aug 2019 19:50:03 +0200 [thread overview]
Message-ID: <20190812175004.24943-1-martin.blumenstingl@googlemail.com> (raw)
This series makes Odroid-C1 use the MAC address which is programmed into
the eFuse.
build-time dependencies:
none
runtime dependencies (without these a random MAC address is assigned,
just like before these patches), both are already part of -next:
- "nvmem: meson-mx-efuse: allow reading data smaller than word_size"
from [1]
- "net: stmmac: manage errors returned by of_get_mac_address()" from [1]
Changes since v1 at [2]:
- only add the nvmem cell to meson8b-odroidc1.dts as suggested by Neil.
It turns out that neither MXQ and EC-100 have the MAC address in eFuse
(which means only 1/3 boards has it at the given eFuse offset, so it's
not worth having it the common .dtsi)
Kevin: you already have v1 of this series in your tree. Feel free to
replace the two patches from v1 with this single one.
[0] https://patchwork.kernel.org/patch/11062659/
[1] https://patchwork.kernel.org/patch/11062657/
[2] https://patchwork.kernel.org/cover/11062663/
Martin Blumenstingl (1):
ARM: dts: meson8b: odroidc1: use the MAC address stored in the eFuse
arch/arm/boot/dts/meson8b-odroidc1.dts | 9 +++++++++
1 file changed, 9 insertions(+)
--
2.22.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-amlogic@lists.infradead.org, khilman@baylibre.com
Cc: narmstrong@baylibre.com, linux.amoon@gmail.com,
ottuzzi@gmail.com, linux-kernel@vger.kernel.org,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] ARM: dts: meson8b: persistent MAC address for Odroid-C1
Date: Mon, 12 Aug 2019 19:50:03 +0200 [thread overview]
Message-ID: <20190812175004.24943-1-martin.blumenstingl@googlemail.com> (raw)
This series makes Odroid-C1 use the MAC address which is programmed into
the eFuse.
build-time dependencies:
none
runtime dependencies (without these a random MAC address is assigned,
just like before these patches), both are already part of -next:
- "nvmem: meson-mx-efuse: allow reading data smaller than word_size"
from [1]
- "net: stmmac: manage errors returned by of_get_mac_address()" from [1]
Changes since v1 at [2]:
- only add the nvmem cell to meson8b-odroidc1.dts as suggested by Neil.
It turns out that neither MXQ and EC-100 have the MAC address in eFuse
(which means only 1/3 boards has it at the given eFuse offset, so it's
not worth having it the common .dtsi)
Kevin: you already have v1 of this series in your tree. Feel free to
replace the two patches from v1 with this single one.
[0] https://patchwork.kernel.org/patch/11062659/
[1] https://patchwork.kernel.org/patch/11062657/
[2] https://patchwork.kernel.org/cover/11062663/
Martin Blumenstingl (1):
ARM: dts: meson8b: odroidc1: use the MAC address stored in the eFuse
arch/arm/boot/dts/meson8b-odroidc1.dts | 9 +++++++++
1 file changed, 9 insertions(+)
--
2.22.0
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next reply other threads:[~2019-08-12 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 17:50 Martin Blumenstingl [this message]
2019-08-12 17:50 ` [PATCH 0/1] ARM: dts: meson8b: persistent MAC address for Odroid-C1 Martin Blumenstingl
2019-08-12 17:50 ` Martin Blumenstingl
2019-08-12 17:50 ` [PATCH 1/1] ARM: dts: meson8b: odroidc1: use the MAC address stored in the eFuse Martin Blumenstingl
2019-08-12 17:50 ` Martin Blumenstingl
2019-08-12 17:50 ` Martin Blumenstingl
2019-08-12 20:47 ` [PATCH 0/1] ARM: dts: meson8b: persistent MAC address for Odroid-C1 Kevin Hilman
2019-08-12 20:47 ` Kevin Hilman
2019-08-12 20:47 ` Kevin Hilman
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=20190812175004.24943-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=narmstrong@baylibre.com \
--cc=ottuzzi@gmail.com \
/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.