Chromium devices (like Google WiFi) have ramoops memory reserved by the
bootloader. Let's enable the ramoops kernel module by default, so we get
better crash logging.
Signed-off-by: Brian Norris <computersforpe...@gmail.com>
---
target/linux/ipq40xx/image/chromium.mk | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/target/linux/ipq40xx/image/chromium.mk
b/target/linux/ipq40xx/image/chromium.mk
index 2abd2df02ae4..f6ac69ecf143 100644
--- a/target/linux/ipq40xx/image/chromium.mk
+++ b/target/linux/ipq40xx/image/chromium.mk
@@ -30,7 +30,11 @@ define Device/google_wifi
KERNEL_NAME := zImage
IMAGES += factory.bin
IMAGE/factory.bin := cros-gpt | append-kernel-part | append-rootfs
+ # Note: Chromium/Depthcharge-based bootloaders insert a reserved-memory
+ # ramoops node into the Device Tree automatically, so we can use
+ # kmod-ramoops.
DEVICE_PACKAGES := partx-utils mkf2fs e2fsprogs \
- kmod-fs-ext4 kmod-fs-f2fs kmod-google-firmware
+ kmod-fs-ext4 kmod-fs-f2fs kmod-google-firmware \
+ kmod-ramoops
endef
TARGET_DEVICES += google_wifi
--
2.39.1
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
