Rosen Penev [2019-08-13 15:27:38]:
Hi,
> Can this be backported to 18.06? It fails there as well:
> https://downloads.openwrt.org/releases/faillogs-18.06/arc_arc700/base/libbsd/compile.txt
done, can you please prepare PR/patches next time? Thanks.
-- ynezz
Hi!
On Wed, Aug 14, 2019 at 4:59 PM Michal Cieslakiewicz
wrote:
> /etc/hotplug.d/firmware/10-ath9k-eeprom for these routers just extracts
> 4k of calibration data from ART to bin file in /lib/firmware. I
> compared bin file to mtd area and they are identical. Why ath9k cannot
> use this data
check for sama5d4_xplained device while copying at91bootstrap binary
to sdcard image.
Signed-off-by: Sandeep Sheriker M
---
target/linux/at91/image/sama5.mk | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/target/linux/at91/image/sama5.mk
remove at91-sdcard build command from Makefile as this is moved to
respective subtarget Makefile.
Signed-off-by: Sandeep Sheriker M
---
target/linux/at91/image/Makefile | 35 ---
1 file changed, 35 deletions(-)
diff --git a/target/linux/at91/image/Makefile
This device has not been supported in ar71xx, so there is no need
for an explicit SUPPORTED_DEVICES entry.
Signed-off-by: Adrian Schmutzler
---
target/linux/ath79/image/generic-tp-link.mk | 1 -
1 file changed, 1 deletion(-)
diff --git a/target/linux/ath79/image/generic-tp-link.mk
The driver commit is: 9e5ab25027e0971fa24ccf93373324c08c4e992d
This should fix a problem with 1560 MTU, 160Mhz on DFS channels,
some other small issues on < 5.2 kernels, and for 5.2 driver,
it pulls in some upstream stable fixes.
wave-1 firmware changes since last update:
* June 24, 2019:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Adrian,
Thanks for helping me with WNR patchset, one question came to my mind
in the process of developing it and after reading one of your emails.
Sorry if it has been answered elsewhere...
/etc/hotplug.d/firmware/10-ath9k-eeprom for these
> /etc/hotplug.d/firmware/10-ath9k-eeprom for these routers just extracts
> 4k of calibration data from ART to bin file in /lib/firmware. I
> compared bin file to mtd area and they are identical. Why ath9k cannot
> use this data directly accessing /dev/mtd6? Is that 'mtd-cal-data' dts
> option
