Re: [OpenWrt-Devel] Squashfs breakage lottery with UBI WAS: [PATCH RFC 2/2] amp821xx: use newly added pad-squashfs for Meraki MR24

On Friday, August 30, 2019 11:10:54 PM CEST Russell Senior wrote: > > "Christian" == Christian Lamparter writes: > > Christian> Ok. > > Christian> I did push a patch titled: "build: remove harmful -nopad > Christian> option from mksquashfs" > Christian> >

Re: [OpenWrt-Devel] Squashfs breakage lottery with UBI WAS: [PATCH RFC 2/2] amp821xx: use newly added pad-squashfs for Meraki MR24

> "Christian" == Christian Lamparter writes: Christian> Ok. Christian> I did push a patch titled: "build: remove harmful -nopad Christian> option from mksquashfs" Christian> Christian> so,

[OpenWrt-Devel] [PATCH] ath79: DIR825B1 switch to gpio-keys

Signed-off-by: Dmitry Tunin --- target/linux/ath79/dts/ar7161_dlink_dir-825-b1.dts | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/target/linux/ath79/dts/ar7161_dlink_dir-825-b1.dts b/target/linux/ath79/dts/ar7161_dlink_dir-825-b1.dts index da19921..8e60bb4 100644 --- a/t

Re: [OpenWrt-Devel] Squashfs breakage lottery with UBI WAS: [PATCH RFC 2/2] amp821xx: use newly added pad-squashfs for Meraki MR24

On Thursday, August 29, 2019 1:55:25 PM CEST Russell Senior wrote: > > >> Fwiw, I took a little closer look at the squashfs code. I still don't > >> quite understand it, but I sprinkled some printk()'s and got a better > >> idea of what is happening. > >> > >> With a root.squashfs of 6428672 byte

Re: [OpenWrt-Devel] [PATCH procd] system: reject sysupgrade of broken firmware images

Hi, > [snip] > + blobmsg_parse(validation_policy, __VALIDATION_MAX, validation, > blob_data(b.head), blob_len(b.head)); > + > + valid = validation[VALIDATION_VALID] && > blobmsg_get_bool(validation[VALIDATION_VALID]); > + forceable = validation[VALIDATION_FORCEABLE] && > blobmsg_get

[OpenWrt-Devel] [PATCH procd] system: reject sysupgrade of broken firmware images

From: Rafał Miłecki This uses recently added "validate_firmware_image" to validate passed firmware. If it happens to be invalid and marked as impossible to force then sysupgrade simply exits with an error. This change is needed to avoid bricking devices with some totally broken images. Signed-o

Re: [OpenWrt-Devel] MT7610En bluetooth support

On 30/08/2019 15:29, Enrico Mioso wrote: Hello!! I saw commit 7f9edadf85299cd4fc965a811b40eaa57a368486 and was wondering if we can now use the BT hardware found on this chipset. Thanks!! Enrico its still WIP     John ___ openwrt-devel maili

[OpenWrt-Devel] MT7610En bluetooth support

Hello!! I saw commit 7f9edadf85299cd4fc965a811b40eaa57a368486 and was wondering if we can now use the BT hardware found on this chipset. Thanks!! Enrico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman

Re: [OpenWrt-Devel] [PATCH procd] system: add "validate_firmware_image" ubus method

On 30.08.2019 09:28, Rafał Miłecki wrote: This new method allows validating firmware image (stored on a device) using ubus. It uses new executable helper that provides detailed info about firmware image. The point of this method is to allow user interfaces provide various info before starting ac

[OpenWrt-Devel] [PATCH procd] system: add "validate_firmware_image" ubus method

From: Rafał Miłecki This new method allows validating firmware image (stored on a device) using ubus. It uses new executable helper that provides detailed info about firmware image. The point of this method is to allow user interfaces provide various info before starting actual upgrade process.