nasbdh9
nasbdh9
> I'd expect such breakage to be rather caused by the [b595670](https://github.com/openwrt/openwrt/commit/b5956700702b5649ec70bfa0d115af5b439ce6d1) ("kernel: backport nvmem v6.6 fixes and v6.7 changes"). I compiled e46559215573c58fb35ccaceee5fcc961c0813b2 which can read the mac address correctly...
> Can you test if changing the nvmem definition in the eeprom DTS node to an [nvmem layout](https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/nvmem/layouts/fixed-layout.yaml) fixes this? Current: > > https://github.com/openwrt/openwrt/blob/cffd3ad8d7cad2214d44695ad4f2405ea53a26c7/target/linux/ipq40xx/files-6.6/arch/arm/boot/dts/qcom/qcom-ipq4029-insect-common.dtsi#L126-L139 > > Example layout: > >...
Still cannot read mac address after conversion ``` &blsp1_i2c3 { pinctrl-0 = ; pinctrl-names = "default"; status = "okay"; eeprom@50 { compatible = "atmel,24c64"; pagesize = ; reg = ;...
sysfs can read the correct mac address ``` root@OpenWrt:~# hexdump -C /sys/bus/nvmem/devices/*/cells/mac-address@66 00000000 e0 cb bc 48 50 f3 |...HP.| 00000006 ``` dmesg root@OpenWrt:~# dmesg [ 0.000000] Booting Linux on...
is this because ipqess doesn't use the mac_address defined in the device tree?
Patch does not work, still uses random mac address. ``` root@OpenWrt:~# dmesg | grep ipqess [ 1.425929] ipqess-edma c080000.ethernet: using random MAC address 32:f9:4f:59:9b:67 [ 1.540704] ipqess-edma c080000.ethernet eth0: entered...
``` BusyBox v1.36.1 (2024-07-05 08:05:58 UTC) built-in shell (ash) _______ ________ __ | |.-----.-----.-----.| | | |.----.| |_ | - || _ | -__| || | | || _|| _|...
Wow, all 32-bit CPU target has failed
现在的扩展名重命名是有问题的（应该是说这个问题一直都有），就修这个，以前后台压缩非原图都是jpg所以大家都不太发现这个问题？如果不修这个问题的话现在下原图的扩展名也是全部变webp的 
> I don't see these changes in linux-next, so claiming this is a backport seems wrong. > > `backport-*` is only for patches already accepted for upstream linux, and this...