On Sat, 15 Dec 2018 at 06:00, Rafał Miłecki wrote:
>
> I've noticed a problem with kmod-phy-bcm-ns-usb2 defined in the
> target/linux/bcm53xx/modules.mk
>
> Steps to reproduce:
> 1) Setup .config with:
> CONFIG_TARGET_bcm53xx
> CONFIG_TARGET_MULTI_PROFILE
> TARGET_ALL_PROFILES
> CONFIG_TARGET_PER_
I've noticed a problem with kmod-phy-bcm-ns-usb2 defined in the
target/linux/bcm53xx/modules.mk
Steps to reproduce:
1) Setup .config with:
CONFIG_TARGET_bcm53xx
CONFIG_TARGET_MULTI_PROFILE
TARGET_ALL_PROFILES
CONFIG_TARGET_PER_DEVICE_ROOTFS
2) make V=s
3) vim build_dir/target-*/linux-*/linux-*/dri
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
The package fails to build on litt
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Don't use cpu_to_be32 outside of a
Tested on cns3xxx, imx6, ar71xx, x86_64 (armv6k/mpcore, armv7, mips r2,
x86_64)
All ok
Tested-by: Koen Vandeputte
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
13/12/2018 17:16, Rafał Miłecki:
From: Rafał Miłecki
It results in calling the right MTD parser directly instead of trying
them one by one.
Signed-off-by: Rafał Miłecki
---
I'm not sure about the AR670W.dts. It seems to be using WRG according to
the image generating code:
IMAGE/factory.bin :=