Brian Norris a94c020f38 chromium: Add #{address,size}-cells to /firmware ... Commit b4d7263bc3 ("kernel: of: avoid some unnecessary bad cell count warnings") backported Linux commit 6e5773d52f4a ("of/address: Fix WARN when attempting translating non-translatable addresses"), which started requiring #address-cells for a device's parent if we want to use the reg resource in a device node. Many Chromium devices use a /firmware/coreboot device node that is patched in by the boot firmware. These structures look something like: # find /sys/firmware/devicetree/base/firmware/ /sys/firmware/devicetree/base/firmware/ /sys/firmware/devicetree/base/firmware/scm /sys/firmware/devicetree/base/firmware/scm/compatible /sys/firmware/devicetree/base/firmware/scm/name /sys/firmware/devicetree/base/firmware/ranges /sys/firmware/devicetree/base/firmware/chromeos /sys/firmware/devicetree/base/firmware/chromeos/fmap-offset /sys/firmware/devicetree/base/firmware/chromeos/compatible /sys/firmware/devicetree/base/firmware/chromeos/readonly-firmware-version /sys/firmware/devicetree/base/firmware/chromeos/nonvolatile-context-storage /sys/firmware/devicetree/base/firmware/chromeos/hardware-id /sys/firmware/devicetree/base/firmware/chromeos/firmware-type /sys/firmware/devicetree/base/firmware/chromeos/vboot-shared-data /sys/firmware/devicetree/base/firmware/chromeos/nonvolatile-context-offset /sys/firmware/devicetree/base/firmware/chromeos/firmware-version /sys/firmware/devicetree/base/firmware/chromeos/nonvolatile-context-size /sys/firmware/devicetree/base/firmware/chromeos/name /sys/firmware/devicetree/base/firmware/coreboot /sys/firmware/devicetree/base/firmware/coreboot/compatible /sys/firmware/devicetree/base/firmware/coreboot/board-id /sys/firmware/devicetree/base/firmware/coreboot/reg /sys/firmware/devicetree/base/firmware/coreboot/name /sys/firmware/devicetree/base/firmware/name Notably, there is no #{address,size}-cells in /firmware. This breaks any driver relying on a device under /firmware, such as the coreboot_table driver. This is technically an ill-formatted FDT, and so we might as well just add the properties ourselves. Signed-off-by: Brian Norris <computersforpeace@gmail.com> Link: https://github.com/openwrt/openwrt/pull/22951 Signed-off-by: Robert Marko <robimarko@gmail.com>		2026-04-16 14:18:45 +02:00
..
qcom-ipq8062-wg2600hp3.dts
qcom-ipq8064-ad7200-c2600.dtsi
qcom-ipq8064-ad7200.dts
qcom-ipq8064-ap148.dts
qcom-ipq8064-ap161.dts
qcom-ipq8064-asus-onhub.dts
qcom-ipq8064-c2600.dts
qcom-ipq8064-d7800.dts
qcom-ipq8064-db149.dts
qcom-ipq8064-e8350-v1.dts	ipq806x: e8350: use nvmem for MAC address	2026-03-10 13:38:32 +01:00
qcom-ipq8064-ea7500-v1.dts
qcom-ipq8064-ea8500.dts
qcom-ipq8064-eax500.dtsi	treewide: linksys: remove unnecessary properties	2026-03-30 19:35:41 +02:00
qcom-ipq8064-fap-421e.dts
qcom-ipq8064-g10.dts	ipq806x: use nvmem for calibration	2026-03-10 13:38:33 +01:00
qcom-ipq8064-onhub.dtsi	chromium: Add #{address,size}-cells to /firmware	2026-04-16 14:18:45 +02:00
qcom-ipq8064-r7500.dts
qcom-ipq8064-r7500v2.dts
qcom-ipq8064-tplink-onhub.dts
qcom-ipq8064-unifi-ac-hd.dts
qcom-ipq8064-vr2600v.dts
qcom-ipq8064-wg2600hp.dts
qcom-ipq8064-wpq864.dts
qcom-ipq8064-wxr-2533dhp.dts
qcom-ipq8065-ac400i.dts
qcom-ipq8065-nbg6817.dts	ipq806x: nbg6817: use nvmem for MAC addresses	2026-02-23 10:54:08 +01:00
qcom-ipq8065-nighthawk.dtsi
qcom-ipq8065-r7800.dts
qcom-ipq8065-rt4230w-rev6.dts
qcom-ipq8065-tr4400-v2.dts
qcom-ipq8065-xr450.dts
qcom-ipq8065-xr500.dts
qcom-ipq8068-ap3935.dts	ipq806x: ap3935: fix uboot nvmem	2026-03-10 13:38:33 +01:00
qcom-ipq8068-cryptid-common.dtsi	ipq806x: mr42/mr52: use nvmem for caldata	2026-03-10 13:38:33 +01:00
qcom-ipq8068-ecw5410.dts	ipq806x: use nvmem for calibration	2026-03-10 13:38:33 +01:00
qcom-ipq8068-mr42.dts	ipq806x: mr42/mr52: use nvmem for caldata	2026-03-10 13:38:33 +01:00
qcom-ipq8068-mr52.dts	ipq806x: mr42/mr52: use nvmem for caldata	2026-03-10 13:38:33 +01:00
qcom-ipq8068-ss-w2-ac2600.dts