> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Adrian Schmutzler
> Sent: Freitag, 6. September 2019 16:54
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH 2/2] ath79: refactor ath9k/ath10k caldata
>
The UniFi AC LED mapping is currently off. The blue/white LED are used
as WiFi indicators, while the vendor firmware does not feature WiFI
LEDs.
Instead, the LEDs are used to indicate the devices status. Align the LED
mapping to match the vendor firmware as good as possible.
Signed-off-by: David
Previous commit 0cc87b3 "ath79: image: disable sysupgrade images for
routerstations and ja76pf2" doesn't remedy completely the posibility of
bricking the device, since user could try to downgrade with an older
image. Therefore disable sysupgrade code for these boards with a small
note.
Now that the md5 check is fixed and metadata present, sysupgrade on
ar71xx will complain about device not being supported by the image.
Since the cause is not matching strings for supported devices add them
accordingly.
Signed-off-by: Tomasz Maciej Nowak
(cherry picked from commit
There is md5 sum of whole image embedded in combined-image header which
is checked on sysupgrade. The check will fail for ath79 images which
may have embedded metadata. This is because metadata are appended after
the combined image is created. To allow smooth transition from ar71xx to
ath79, strip
The frequency was filled acording the information from datasheet for
particular chip (Winbond 25Q128BVFG). Unfortunately this led to
coruption and introduced bad blocks on the chip. Reducing the frequency
to commonly used in ath79, made the board more stable and no new bad
blocks were spoted.
This target enforces metadata check so add the necessary information. It
was previously removed because md5 sum check. When using these sysupgrade
images on ar71xx target the check would complain about them not matching.
Signed-off-by: Tomasz Maciej Nowak
(cherry picked from commit
Both ath9k and ath10k caldata extraction use similar functions,
which in several cases only differ by their name.
This patch moves functions to a shared library script and merges
ath9k and ath10k variants there.
MAC address patch functions are moved, but not merged, as they
are considerably
The xor() function is defined in each of the caldata extraction
scripts for several targets. Move it to functions.sh to reduce
duplicate code.
Signed-off-by: Adrian Schmutzler
---
package/base-files/files/lib/functions.sh | 16
.../etc/hotplug.d/firmware/10-ath9k-eeprom
The actual retrieval of the MAC address in mtd_get_mac_binary_ubi()
is the same as in get_mac_binary(). Thus, use the latter function
in the former to reduce duplicate code.
This will also allow to benefit from the enhanced path check there
and bring mtd_get_mac_binary_ubi() more in line with the
> -Original Message-
> From: Rafał Miłecki [mailto:ra...@milecki.pl]
> Sent: Freitag, 6. September 2019 15:13
> To: Adrian Schmutzler
> Cc: 'Rafał Miłecki' ; openwrt-devel@lists.openwrt.org;
> 'Jonas Gorski' ; 'Jo-Philipp Wich'
> ; 'John Crispin'
> Subject: Re: [OpenWrt-Devel] [PATCH
On 2019-09-06 15:05, Adrian Schmutzler wrote:
diff --git a/target/linux/ipq40xx/base-files/lib/upgrade/openmesh.sh
b/target/linux/ipq40xx/base-files/lib/upgrade/openmesh.sh
index e313562017..8e02186eb8 100644
--- a/target/linux/ipq40xx/base-files/lib/upgrade/openmesh.sh
+++
Hi,
just a nitpick:
> diff --git a/target/linux/ipq40xx/base-files/lib/upgrade/openmesh.sh
> b/target/linux/ipq40xx/base-files/lib/upgrade/openmesh.sh
> index e313562017..8e02186eb8 100644
> --- a/target/linux/ipq40xx/base-files/lib/upgrade/openmesh.sh
> +++
Enable by default mtk_efuse driver since it needed by mtk_thermal driver
to read sensor calibration data
Signed-off-by: Lorenzo Bianconi
---
target/linux/mediatek/mt7622/config-4.19 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/linux/mediatek/mt7622/config-4.19
Jo-Philipp Wich writes:
>> Buildbot is already crunching the images and packages, and pretty much
>> all targets are green. So there are no obvious build related issues
>> preventing the release. I have also not noticed any franctic discussion
>> about specific major bugs blocking the release,
15 matches
Mail list logo
