|
|
|
|
#
|
|
|
|
|
# Copyright (C) 2015 OpenWrt.org
|
|
|
|
|
#
|
|
|
|
|
# This is free software, licensed under the GNU General Public License v2.
|
|
|
|
|
# See /LICENSE for more information.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
include $(TOPDIR)/rules.mk
|
|
|
|
|
|
|
|
|
|
PKG_NAME:=ath10k-firmware
|
|
|
|
|
PKG_SOURCE_DATE:=2018-10-10
|
|
|
|
|
PKG_SOURCE_VERSION:=d366b80d41309531c0c98b26625f23e318f33e31
|
|
|
|
|
PKG_MIRROR_HASH:=ec06f10e6b1d4f7a28366a893c8a73a000454c2f031fc747381a1fb8aa1e0846
|
|
|
|
|
PKG_RELEASE:=1
|
|
|
|
|
|
|
|
|
|
PKG_SOURCE_PROTO:=git
|
|
|
|
|
PKG_SOURCE_URL:=https://github.com/kvalo/ath10k-firmware.git
|
|
|
|
|
|
|
|
|
|
PKG_MAINTAINER:=Felix Fietkau <nbd@nbd.name>
|
|
|
|
|
|
|
|
|
|
include $(INCLUDE_DIR)/package.mk
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-default
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
URL:=$(PKG_SOURCE_URL)
|
|
|
|
|
DEPENDS:=
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9887
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k firmware for QCA9887 devices
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9888
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k firmware for QCA9888 devices
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9887-ct
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k-CT firmware for QCA9887 devices
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca988x
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k firmware for QCA988x devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
CT_FIRMWARE_FILE = $(1)-$($(1)_FIRMWARE_FILE_CT)
|
|
|
|
|
CT_FIRMWARE_FILE_HTT = $(1)-$($(1)_FIRMWARE_FILE_CT_HTT)
|
|
|
|
|
|
|
|
|
|
define Download/ct-firmware
|
|
|
|
|
URL:=https://www.candelatech.com/downloads/$(2)
|
|
|
|
|
FILE:=$(call CT_FIRMWARE_FILE,$(1))
|
|
|
|
|
URL_FILE:=$($(1)_FIRMWARE_FILE_CT)
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Download/ct-firmware-htt
|
|
|
|
|
URL:=https://www.candelatech.com/downloads/$(2)
|
|
|
|
|
FILE:=$(call CT_FIRMWARE_FILE_HTT,$(1))
|
|
|
|
|
URL_FILE:=$($(1)_FIRMWARE_FILE_CT_HTT)
|
|
|
|
|
endef
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA988X_FIRMWARE_FILE_CT:=firmware-2-ct-full-community-22.bin.lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca988x-ct
|
|
|
|
|
$(call Download/ct-firmware,QCA988X,)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=c2407cbdaaf143c9796e654aed026f0aa70fc93a82dd1244c62e95ede894e829
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca988x-ct))
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA988X_FIRMWARE_FILE_CT_HTT:=firmware-2-ct-full-htt-mgt-community-22.bin.lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca988x-ct-htt
|
|
|
|
|
$(call Download/ct-firmware-htt,QCA988X,)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=789c4d1c8ac5edeb43d507157944102b564cd6970c365a14b50cab08ffa4e3b5
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca988x-ct-htt))
|
|
|
|
|
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA9887_FIRMWARE_FILE_CT:=firmware-2-ct-full-community-22.bin.lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca9887-ct
|
|
|
|
|
$(call Download/ct-firmware,QCA9887,ath10k-9887)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=07692a63ab9d11a65c17cc896aff89ea33b7af4e0e1e51ae100651291afe3a4d
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca9887-ct))
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA9887_FIRMWARE_FILE_CT_HTT:=firmware-2-ct-full-htt-mgt-community-22.bin.lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca9887-ct-htt
|
|
|
|
|
$(call Download/ct-firmware-htt,QCA9887,ath10k-9887)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=ef336462d4a44ab9a0d89e83064124e647a9fb4a8af8be9df5724378611d2e82
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca9887-ct-htt))
|
|
|
|
|
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA99X0_FIRMWARE_FILE_CT:=firmware-5-ct-full-community-12.bin-lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca99x0-ct
|
|
|
|
|
$(call Download/ct-firmware,QCA99X0,ath10k-10-4b)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=3357d7ba739512619ccd14043338cfe8e148d5d8e99343e3ccf7a2ff0d07d05f
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca99x0-ct))
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA99X0_FIRMWARE_FILE_CT_HTT:=firmware-5-ct-full-htt-mgt-community-12.bin-lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca99x0-ct-htt
|
|
|
|
|
$(call Download/ct-firmware-htt,QCA99X0,ath10k-10-4b)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=ce81e1b9b80b30263e9d5010e38fac3f005214fd955dc2cff95e7fe633796212
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca99x0-ct-htt))
|
|
|
|
|
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA9984_FIRMWARE_FILE_CT:=firmware-5-ct-full-community-12.bin-lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca9984-ct
|
|
|
|
|
$(call Download/ct-firmware,QCA9984,ath10k-9984-10-4b)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=e2794ce577ff7942dc5f767a77fa52167f323bc8f50f04570fc5efe92ed761cf
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca9984-ct))
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA9984_FIRMWARE_FILE_CT_HTT:=firmware-5-ct-full-htt-mgt-community-12.bin-lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca9984-ct-htt
|
|
|
|
|
$(call Download/ct-firmware-htt,QCA9984,ath10k-9984-10-4b)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=1f90555963c2e52ac8fc5581b2a0f9c658e3f5205844898bdc48c78d009bb6eb
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca9984-ct-htt))
|
|
|
|
|
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA4019_FIRMWARE_FILE_CT:=firmware-5-ct-full-community-12.bin-lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca4019-ct
|
|
|
|
|
$(call Download/ct-firmware,QCA4019,ath10k-4019-10-4b)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=4e73cf8e24e83df87d6dce2038e350b3f67753ccca37a8c0d1b861818991e6aa
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca4019-ct))
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA4019_FIRMWARE_FILE_CT_HTT:=firmware-5-ct-full-htt-mgt-community-12.bin-lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca4019-ct-htt
|
|
|
|
|
$(call Download/ct-firmware-htt,QCA4019,ath10k-4019-10-4b)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=8f6434856d6f0207bc3f519cf50d2bf45df1bfcbc69b864ed02fcb5cd5ef6f4b
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca4019-ct-htt))
|
|
|
|
|
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA9888_FIRMWARE_FILE_CT:=firmware-5-ct-full-community-12.bin-lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca9888-ct
|
|
|
|
|
$(call Download/ct-firmware,QCA9888,ath10k-9888-10-4b)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=6b627746f88c1bfecb872e72c61d6097192e389592e391630d2661b44f13b10d
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca9888-ct))
|
|
|
|
|
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
QCA9888_FIRMWARE_FILE_CT_HTT:=firmware-5-ct-full-htt-mgt-community-12.bin-lede.008
|
|
|
|
|
define Download/ath10k-firmware-qca9888-ct-htt
|
|
|
|
|
$(call Download/ct-firmware-htt,QCA9888,ath10k-9888-10-4b)
|
ath10k-firmware: update Candela Tech firmware images
Release notes since last time:
Release notes for wave-1:
2019-04-02: Support some get/set API for eeprom rate power tables.
Mostly backported from 10.2
2019-04-02: Support adaptive-CCA, backported from 10.2
2019-04-02: Support adding eeprom configAddr pairs via the
set-special API. These configAddrs can be used to change
the default register settings for up to 12 registers.
2019-05-03: Fix tx-power settings for 2x2, 3x3 rates.
Original logic I put in back in 2016 set 2x2 and 3x3 lower
than the needed to be when using most NICs (very high
powered NICs would not have been affected I think, not sure
any of those exist though.)
This improves throughput for 2x2 and 3x3 devices,
especially when the signal is weaker.
Release notes for wave-2:
2019-04-08: When setting keys, if high bit of high value of
key_rsc_counter is set to 0x1, then the lower 48 bits will
be used as the PN value. By default, PN is set to 1 each
time the key is set.
2019-04-08: Pack PN into un-used 'excretries' aka
'num_pkt_loss_excess_retry' high 16 bits.
This lets us report peer PN, but *only* if driver has
previously set a PN when setting key (or set-special cmd is
used to enable PN reporting).
This is done so that we know the driver is recent
enough to deal with the PN stat reporting.
2019-04-16: Support specifying tx rate on a per-beacon packet.
See ath10k_wmi_op_gen_beacon_dma and
ath10k_convert_hw_rate_to_rate_info for API details.
Driver needs additional work to actually enable this
feature currently.
2019-04-30: Compile out tx-prefetch caching logic.
It is full of tricky bugs that cause tx hangs.
I fixed at least one, but more remain and I have wasted too
much time on this already.
2019-05-08: Start rate-ctrl at mcs-3 instead of mcs-5.
This significantly helps DHCP happen quickly, probably
because the initial rate being too high would take a while
to ramp down, especially since there are few packets sent
by the time DHCP needs to start.
This bug was triggered by me decreasing retries of 0x1e
(upstream default) to 0x4. But, I think it is better to
start with lower initial MCS instead of always having a
very high retry count.
Tested on 8devices Jalapeno dev board(IPQ4019)
Signed-off-by: Robert Marko <robimarko@gmail.com>
Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [neatify]
5 years ago
|
|
|
HASH:=4ef46b2bdd3ddc894f79da2dbf90ee04cb58781f3eb193840bd5fdb8624b447b
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,ath10k-firmware-qca9888-ct-htt))
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca99x0
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k firmware for QCA99x0 devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca988x-ct
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.1 firmware for QCA988x devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca988x
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca988x-ct-htt
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.1 htt-mgt fw for QCA988x
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca988x
|
|
|
|
|
DEPENDS:=+kmod-ath10k-ct
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9887-ct
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.1 firmware for QCA9887 devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca9887
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9887-ct-htt
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.1 htt-mgt fw for QCA9887
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca9887
|
|
|
|
|
DEPENDS:=+kmod-ath10k-ct
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca988x-ct/description
|
|
|
|
|
Alternative ath10k firmware for QCA988X from Candela Technologies.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.1.php
|
|
|
|
|
This firmware will NOT be used unless the standard ath10k-firmware-qca988x
|
|
|
|
|
is un-selected since the driver will try to load firmware-5.bin before
|
|
|
|
|
firmware-2.bin
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca988x-ct-htt/description
|
|
|
|
|
Alternative ath10k firmware for QCA988X from Candela Technologies.
|
|
|
|
|
Uses normal HTT TX data path for management frames, which improves
|
|
|
|
|
stability in busy networks and fixes .11r authentication.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.1.php
|
|
|
|
|
This firmware selects and requires the ath10k-ct driver.
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9887-ct/description
|
|
|
|
|
Alternative ath10k firmware for QCA9887 from Candela Technologies.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.1.php
|
|
|
|
|
This firmware conflicts with the standard 9887 firmware, so select only
|
|
|
|
|
one.
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9887-ct-htt/description
|
|
|
|
|
Alternative ath10k firmware for QCA9887 from Candela Technologies.
|
|
|
|
|
Uses normal HTT TX data path for management frames, which improves
|
|
|
|
|
stability in busy networks and fixes .11r authentication.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.1.php
|
|
|
|
|
This firmware selects and requires the ath10k-ct driver.
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca99x0-ct/description
|
|
|
|
|
Alternative ath10k firmware for QCA99x0 from Candela Technologies.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.4.php
|
|
|
|
|
This firmware conflicts with the standard 99x0 firmware, so select only
|
|
|
|
|
one.
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca99x0-ct-htt/description
|
|
|
|
|
Alternative ath10k firmware for QCA99x0 from Candela Technologies.
|
|
|
|
|
Uses normal HTT TX data path for management frames, which improves
|
|
|
|
|
stability in busy networks and may be required for .11r authentication.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.4.php
|
|
|
|
|
This firmware selects and requires the ath10k-ct driver.
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9984-ct/description
|
|
|
|
|
Alternative ath10k firmware for QCA9984 from Candela Technologies.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.4.php
|
|
|
|
|
This firmware conflicts with the standard 9984 firmware, so select only
|
|
|
|
|
one.
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9984-ct-htt/description
|
|
|
|
|
Alternative ath10k firmware for QCA9984 from Candela Technologies.
|
|
|
|
|
Uses normal HTT TX data path for management frames, which improves
|
|
|
|
|
stability in busy networks and may be required for .11r authentication.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.4.php
|
|
|
|
|
This firmware selects and requires the ath10k-ct driver.
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca4019-ct/description
|
|
|
|
|
Alternative ath10k firmware for IPQ4019 radio from Candela Technologies.
|
|
|
|
|
Enables IBSS and other features. Works with standard or ath10k-ct driver.
|
|
|
|
|
See: http://www.candelatech.com/ath10k-10.4.php
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca4019-ct-htt/description
|
|
|
|
|
Alternative ath10k firmware for IPQ4019 radio from Candela Technologies.
|
|
|
|
|
Uses normal HTT TX data path for management frames, which improves
|
|
|
|
|
stability in busy networks and may be required for .11r authentication.
|
|
|
|
|
Enables IBSS and other features.
|
|
|
|
|
See: http://www.candelatech.com/ath10k-10.4.php
|
|
|
|
|
This firmware selects and requires the ath10k-ct driver.
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9888-ct/description
|
|
|
|
|
Alternative ath10k firmware for QCA9886 and QCA9888 from Candela Technologies.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.4.php
|
|
|
|
|
This firmware conflicts with the standard 9886 and 9888 firmware, so select only
|
|
|
|
|
one.
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9888-ct-htt/description
|
|
|
|
|
Alternative ath10k firmware for QCA9886 and QCA9888 from Candela Technologies.
|
|
|
|
|
Uses normal HTT TX data path for management frames, which improves
|
|
|
|
|
stability in busy networks and may be required for .11r authentication.
|
|
|
|
|
Enables IBSS and other features. See:
|
|
|
|
|
http://www.candelatech.com/ath10k-10.4.php
|
|
|
|
|
This firmware selects and requires the ath10k-ct driver.
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca99x0/description
|
|
|
|
|
Standard ath10k firmware for QCA99x0 from QCA
|
|
|
|
|
This firmware conflicts with the CT 99x0 firmware, so select only
|
|
|
|
|
one.
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca99x0-ct
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.4 firmware for QCA99x0 devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca99x0
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca99x0-ct-htt
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.4 htt-mgt fw for QCA99x0
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca99x0
|
|
|
|
|
DEPENDS:=+kmod-ath10k-ct
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9984-ct
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.4 firmware for QCA9984 devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca9984
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9984-ct-htt
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.4 htt-mgt fw for QCA9984
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca9984
|
|
|
|
|
DEPENDS:=+kmod-ath10k-ct
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca4019-ct
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.4 firmware for QCA4018/9
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca4019
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca4019-ct-htt
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.4 htt-mgt for QCA4018/9
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca4019
|
|
|
|
|
DEPENDS:=+kmod-ath10k-ct
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9888-ct
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.4 fw for QCA9886/8 devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca9888
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9888-ct-htt
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k CT 10.4 htt-mgt fw for QCA9886/8
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
PROVIDES:=ath10k-firmware-qca9888
|
|
|
|
|
DEPENDS:=+kmod-ath10k-ct
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9984
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k firmware for QCA9984 devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca4019
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k firmware for IPQ/QCA4019 devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca6174
|
|
|
|
|
$(Package/ath10k-firmware-default)
|
|
|
|
|
TITLE:=ath10k firmware for QCA6174 devices
|
|
|
|
|
SECTION:=firmware
|
|
|
|
|
CATEGORY:=Firmware
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
QCA99X0_BOARD_REV:=ddcec9efd245da9365c474f513a855a55f3ac7fe
|
|
|
|
|
QCA99X0_BOARD_FILE:=board-2.bin.$(QCA99X0_BOARD_REV)
|
|
|
|
|
|
|
|
|
|
define Download/qca99x0-board
|
|
|
|
|
URL:=https://source.codeaurora.org/quic/qsdk/oss/firmware/ath10k-firmware/plain/ath10k/QCA99X0/hw2.0
|
|
|
|
|
URL_FILE:=board-2.bin?id=$(QCA99X0_BOARD_REV)
|
|
|
|
|
FILE:=$(QCA99X0_BOARD_FILE)
|
|
|
|
|
HASH:=03711ac21e60ef59d3815e235eb721c0c22851b5410299411085aa6f2af45401
|
|
|
|
|
endef
|
|
|
|
|
$(eval $(call Download,qca99x0-board))
|
|
|
|
|
|
|
|
|
|
define Build/Compile
|
|
|
|
|
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca4019/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA4019/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA4019/hw1.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA4019/hw1.0/
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA4019/hw1.0/3.5.3/firmware-5.bin_10.4-3.5.3-00057 \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA4019/hw1.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9887/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9887/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9887/hw1.0/10.2.4-1.0/firmware-5.bin_10.2.4-1.0-00033 \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9887/hw1.0/firmware-5.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9887/hw1.0/board.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9887/hw1.0/board.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9888/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9888/hw2.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9888/hw2.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9888/hw2.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9888/hw2.0/3.5.3/firmware-5.bin_10.4-3.5.3-00053 \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9888/hw2.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca988x/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA988X/hw2.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA988X/hw2.0/board.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA988X/hw2.0/
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA988X/hw2.0/10.2.4-1.0/firmware-5.bin_10.2.4-1.0-00037 \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA988X/hw2.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca6174/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA6174/hw2.1
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA6174/hw2.1/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA6174/hw2.1/
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA6174/hw2.1/firmware-5.bin_SW_RM.1.1.1-00157-QCARMSWPZ-1 \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA6174/hw2.1/firmware-5.bin
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA6174/hw3.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA6174/hw3.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA6174/hw3.0/
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA6174/hw3.0/4.4.1.c1/firmware-6.bin_RM.4.4.1.c1-00042-QCARMSWP-1 \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca99x0/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA99X0/hw2.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(QCA99X0_BOARD_FILE) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA99X0/hw2.0/boardData_AR900B_CUS239_5G_v2_001.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/board.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA99X0/hw2.0/firmware-5.bin_10.4.1.00030-1 \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9984/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9984/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9984/hw1.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9984/hw1.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9984/hw1.0/3.5.3/firmware-5.bin_10.4-3.5.3-00053 \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9984/hw1.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# CT related firmware
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9887-ct/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9887/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE,QCA9887) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9887/hw1.0/firmware-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9887/hw1.0/board.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9887/hw1.0/board.bin
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9887-ct-htt/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9887/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE_HTT,QCA9887) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9887/hw1.0/ct-firmware-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9887/hw1.0/board.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9887/hw1.0/board.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca988x-ct/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA988X/hw2.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA988X/hw2.0/board.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA988X/hw2.0/
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE,QCA988X) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA988X/hw2.0/firmware-2.bin
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca988x-ct-htt/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA988X/hw2.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA988X/hw2.0/board.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA988X/hw2.0/
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE_HTT,QCA988X) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA988X/hw2.0/ct-firmware-2.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca99x0-ct/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA99X0/hw2.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(QCA99X0_BOARD_FILE) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA99X0/hw2.0/boardData_AR900B_CUS239_5G_v2_001.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/board.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE,QCA99X0) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca99x0-ct-htt/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA99X0/hw2.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(QCA99X0_BOARD_FILE) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA99X0/hw2.0/boardData_AR900B_CUS239_5G_v2_001.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/board.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE_HTT,QCA99X0) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA99X0/hw2.0/ct-firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9984-ct/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9984/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9984/hw1.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9984/hw1.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE,QCA9984) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9984/hw1.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9984-ct-htt/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9984/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9984/hw1.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9984/hw1.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE_HTT,QCA9984) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9984/hw1.0/ct-firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca4019-ct/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA4019/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA4019/hw1.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA4019/hw1.0/
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE,QCA4019) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA4019/hw1.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca4019-ct-htt/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA4019/hw1.0
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA4019/hw1.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA4019/hw1.0/
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE_HTT,QCA4019) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA4019/hw1.0/ct-firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
define Package/ath10k-firmware-qca9888-ct/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9888/hw2.0
|
|
|
|
|
ln -s \
|
|
|
|
|
../../cal-pci-0000:01:00.0.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9888/hw2.0/board.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9888/hw2.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9888/hw2.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE,QCA9888) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9888/hw2.0/firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
define Package/ath10k-firmware-qca9888-ct-htt/install
|
|
|
|
|
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA9888/hw2.0
|
|
|
|
|
ln -s \
|
|
|
|
|
../../cal-pci-0000:01:00.0.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9888/hw2.0/board.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(PKG_BUILD_DIR)/QCA9888/hw2.0/board-2.bin \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9888/hw2.0/board-2.bin
|
|
|
|
|
$(INSTALL_DATA) \
|
|
|
|
|
$(DL_DIR)/$(call CT_FIRMWARE_FILE_HTT,QCA9888) \
|
|
|
|
|
$(1)/lib/firmware/ath10k/QCA9888/hw2.0/ct-firmware-5.bin
|
|
|
|
|
endef
|
|
|
|
|
|
|
|
|
|
#$(eval $(call BuildPackage,ath10k-firmware-qca9887))
|
|
|
|
|
#$(eval $(call BuildPackage,ath10k-firmware-qca9888))
|
|
|
|
|
#$(eval $(call BuildPackage,ath10k-firmware-qca988x))
|
|
|
|
|
#$(eval $(call BuildPackage,ath10k-firmware-qca99x0))
|
|
|
|
|
#$(eval $(call BuildPackage,ath10k-firmware-qca6174))
|
|
|
|
|
#$(eval $(call BuildPackage,ath10k-firmware-qca9984))
|
|
|
|
|
#$(eval $(call BuildPackage,ath10k-firmware-qca4019))
|
|
|
|
|
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca9887-ct))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca9887-ct-htt))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca988x-ct))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca988x-ct-htt))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca99x0-ct))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca99x0-ct-htt))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca9984-ct))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca9984-ct-htt))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca4019-ct))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca4019-ct-htt))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca9888-ct))
|
|
|
|
|
$(eval $(call BuildPackage,ath10k-firmware-qca9888-ct-htt))
|
