From: Jeff Kletsky
Targets that use nand_do_platform_check() can't use SUPPORTED_DEVICES
as the check requires ./sysupgrade-legacy_boardname/CONTROL to be
non-zero length as extracted from the tar file. Previously, only
./sysupgrade-new_boardname/CONTROL was present.
This prevents upgrade withou
This submission is part of a series of commits that prepares for
use of SPI-NAND with the upstream Linux MTD framework for the ath79
target. The entire series of pending changes may be seen on GitHub[1].
The series also addresses upgrade issues associated with tar-style
files and metadata, allow
From: Jeff Kletsky
Improve NAND-based sysupgrade for current and future upgrades
nand_upgrade_tar():
* Use the CONTROL file specific to the running board
to determine asset directory name in the tar file
* Check for string `BOARD=board_name` directly rather than
source-ing to al
From: Jeff Kletsky
Remove the sole board on the legacy ath79 NAND target
to clarify patches that will reintroduce support
on the MTD SPI-NAND framework present in Linux 4.19
Cc: Marty E. Plummer
Signed-off-by: Jeff Kletsky
---
package/boot/uboot-envtools/files/ath79 | 1 -
.../ath79/b
From: Jeff Kletsky
Linux 4.19 supplies the upstream spi-nand framework,
permitting porting and support of boards with SPI NAND.
* Adjusted nand/target.mk to provide FEATURES += squashfs nand
* Updated config-default to provide current MTD and UBI support
Defaults selected for:
CONFIG_MT
This submission is part of a series of commits that prepares for
use of SPI-NAND with the upstream Linux MTD framework for the ath79
target. The entire series of pending changes may be seen on GitHub[1].
The series also addresses upgrade issues associated with tar-style
files and metadata, allow
On 24/10/2019 15:13, David Bauer wrote:
++ // Disable RX delay
Hi,
please use /* comments */
John
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Hi, all. Thank you. I'll incorporate this and test as soon as i can.
On 10/24/2019 10:46 AM, John Crispin wrote:
On 24/10/2019 14:18, Daniel Golle wrote:
On Thu, Oct 24, 2019 at 01:21:56PM +0200, Jo-Philipp Wich wrote:
Hi,
On the Luci GUI, the current behaviour of Save&Apply of changes to th
On 24/10/2019 14:18, Daniel Golle wrote:
On Thu, Oct 24, 2019 at 01:21:56PM +0200, Jo-Philipp Wich wrote:
Hi,
On the Luci GUI, the current behaviour of Save&Apply of changes to the
items in wifi.lua and wireless_modefreq.htm is to invoke a network
restart. I would like to to change this behavi
From: Jeff Kletsky
generic: Add/rename patches for upstream consistency
ipq40xx: generic-level patch replaces same-source patches-4.19/
082-v4.20-mtd-spinand-winbond-Add-support-for-W25N01GV.patch
The SPI-NAND framework from Linux uses common driver code that is then
"tuned" by a tiny
Until upstream commit 6d4cd041f0af("net: phy: at803x: disable delay
only for RGMII mode"), delays were not disabled on driver probe
for the Atheros AR803x PHYs, although the RX delay is enabled on
soft and hard reset.
In addition, the TX delay setting is retained on soft-reset.
This patch disable
On Thu, Oct 24, 2019 at 01:21:56PM +0200, Jo-Philipp Wich wrote:
> Hi,
>
> > On the Luci GUI, the current behaviour of Save&Apply of changes to the
> > items in wifi.lua and wireless_modefreq.htm is to invoke a network
> > restart. I would like to to change this behavior to invoke wifi restart
> >
ZyXEL NWA1123-NI is a dual band 802.11n access point.
The factory firmware partition table is using a small kernel partition
after the rootfs partition. Since it has to be flashed using UART I also
merged 3 partitions (rootfs, uImage, reserve) to one firmware partition
and changed the default load
Hi,
> On the Luci GUI, the current behaviour of Save&Apply of changes to the
> items in wifi.lua and wireless_modefreq.htm is to invoke a network
> restart. I would like to to change this behavior to invoke wifi restart
> directly from wifi.lua.
This is not supported and will confuse the netifd w
Hi,
you need to extend the netifd wireless handler to recognize your
proprietary options.
LuCI does not perform any wireless or network restarting by itself, it
relies on netifd doing the reloading of changed values.
If you introduce new options not yet known to netifd, it will do nothing
when y
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 ---
Please open a bug report/issue on
16 matches
Mail list logo
