aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Kohlschütter <christian@kohlschutter.com>2022-09-27 15:05:21 +0000
committerKever Yang <kever.yang@rock-chips.com>2023-05-06 17:28:18 +0800
commitc2d5edff916379abd2da4590e8171c965d9a3e1d (patch)
treef08c1aaf9db973b75c47835eb39b44026dd81e3c
parent53c5093b2ec08c69b48183e23c5ada3c385053e1 (diff)
downloadu-boot-c2d5edff916379abd2da4590e8171c965d9a3e1d.zip
u-boot-c2d5edff916379abd2da4590e8171c965d9a3e1d.tar.gz
u-boot-c2d5edff916379abd2da4590e8171c965d9a3e1d.tar.bz2
rk3399: r4s: Derive local MAC address if EEPROM is missing
Some RK3399 boards, such as newer revisions of NanoPi R4S, do not provide an EEPROM chip containing a globally unique MAC address. Currently, this means that a randomly generated temporary MAC address may be generated each time the device is rebooted, leading to ARP cache issues and other confusing bugs. Since RK3399 CPUs provide a built-in unique serial number, we can reliably derive a locally MAC address from it by reading the corresponding bits from the non-secure efuse block. Enable configuration options that allow deriving a local MAC address from the CPU serial number.
-rw-r--r--configs/nanopi-r4s-rk3399_defconfig4
1 files changed, 4 insertions, 0 deletions
diff --git a/configs/nanopi-r4s-rk3399_defconfig b/configs/nanopi-r4s-rk3399_defconfig
index a41e774..ad36f7c 100644
--- a/configs/nanopi-r4s-rk3399_defconfig
+++ b/configs/nanopi-r4s-rk3399_defconfig
@@ -78,3 +78,7 @@ CONFIG_VIDEO_ROCKCHIP=y
CONFIG_DISPLAY_ROCKCHIP_HDMI=y
CONFIG_SPL_TINY_MEMSET=y
CONFIG_ERRNO_STR=y
+CONFIG_MISC=y
+CONFIG_MISC_INIT_R=y
+CONFIG_ROCKCHIP_EFUSE=y
+CONFIG_ROCKCHIP_OTP=y