dumalogiya
/
openwrt
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
v19.07.3_mercusys_ac12_duma
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b3770eaca3'
${ noResults }
openwrt/package/firmware/ipq-wifi/Makefile

107 lines
3.4 KiB
Makefile
Raw Normal View History Unescape Escape

firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
include $(TOPDIR)/rules.mk
include $(INCLUDE_DIR)/version.mk
ipq-wifi: fix missing define of PKG_NAME Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
7 years ago
PKG_NAME:=ipq-wifi
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
PKG_RELEASE:=1
firmware: ipq-wifi: mark packages as nonshared The board-files are specific to the target and device. Hence they need to be set as nonshared. Otherwise they do not show up on the package repository. This causes problems for imagebuilder, if it needs to build a image for a specific device that hasn't had the time to have get its boardfile upstream. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
5 years ago
PKG_FLAGS:=nonshared
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
include $(INCLUDE_DIR)/package.mk
define Build/Prepare
mkdir -p $(PKG_BUILD_DIR)
endef
define Build/Compile
endef
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
#
# This is intended to be used on an interim basis until device-specific
# board data for new devices is available through the upstream compilation
#
ipq-wifi: add a note / reminder about upstreaming new board files |Please send a mail with your device-specific board files upstream. |You can find instructions and examples on the linux-wireless wiki: |<https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
6 years ago
# Please send a mail with your device-specific board files upstream.
# You can find instructions and examples on the linux-wireless wiki:
# <https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles>
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
#
ALLWIFIBOARDS:= \
alfa-network_ap120c-ac \
asus_map-ac2200 \
avm_fritzbox-7530 \
avm_fritzrepeater-3000 \
engenius_eap1300 \
engenius_ens620ext \
linksys_ea6350v3 \
qxwlan_e2600ac
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
ALLWIFIPACKAGES:=$(foreach BOARD,$(ALLWIFIBOARDS),ipq-wifi-$(BOARD))
define Package/ipq-wifi-default
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
SUBMENU:=ath10k Board-Specific Overrides
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
SECTION:=firmware
CATEGORY:=Firmware
ipq40xx: unbundle firmware and board file Don't select the firmware with the board file, it prevents an easy use of the -ct ath10k firmware. Select the firmware within the default packages instead. Remove the per device selection of the firmware now that it the firmware is selected by default. Signed-off-by: Mathias Kresin <dev@kresin.me>
6 years ago
DEPENDS:=@TARGET_ipq40xx
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
TITLE:=Custom Board
endef
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
define ipq-wifi-install-one-to
$(INSTALL_DIR) $(2)/lib/firmware/ath10k/$(3)/
$(INSTALL_DATA) $(1) $(2)/lib/firmware/ath10k/$(3)/board-2.bin
endef
# Note: .bin deprecated; supports existing boards
define ipq-wifi-install-one
$(if $(filter $(suffix $(1)),.QCA4019 .qca4019 .bin),\
$(call ipq-wifi-install-one-to,$(1),$(2),QCA4019/hw1.0),\
$(if $(filter $(suffix $(1)),.QCA9888 .qca9888),\
$(call ipq-wifi-install-one-to,$(1),$(2),QCA9888/hw2.0),\
$(if $(filter $(suffix $(1)),.QCA9984 .qca9984),\
$(call ipq-wifi-install-one-to,$(1),$(2),QCA9984/hw1.0),\
$(error Unrecognized board-file suffix '$(suffix $(1))' for '$(1)')\
)))
endef
# Blank line required at end of above define due to foreach context
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
define generate-ipq-wifi-package
define Package/ipq-wifi-$(1)
$(call Package/ipq-wifi-default)
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
TITLE:=board-2.bin Overrides for $(2)
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
CONFLICTS:=$(PREV_BOARD)
endef
define Package/ipq-wifi-$(1)/description
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
The $(2) requires board-specific, reference ("cal") data
that is not yet present in the upstream wireless firmware distribution.
This package supplies board-2.bin file(s) that, in the interim,
overwrite those supplied by the ath10k-firmware-* packages.
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
This is package is only necessary for the $(2).
Do not install it for any other device!
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
endef
define Package/ipq-wifi-$(1)/install-overlay
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
$$$$(foreach IPQ_WIFI_BOARD_FILE,$$$$(wildcard board-$(1).*),\
$$$$(call ipq-wifi-install-one,$$$$(IPQ_WIFI_BOARD_FILE),$$(1)))
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
endef
PREV_BOARD+=ipq-wifi-$(1)
endef
firmware/ipq-wifi: Extend for multi-chip boards This package provides board-specific reference ("cal") data on an interim basis until included in the upstream distros While originally conceived for IPQ4019-based boards, similar needs are appearing with three-radio devices. For some of these devices, both a board-2.bin file needs to be supplied both for the IPQ4019 as well as for the other radio on the board. This patch allows new or multiple overrides to be specified by: * Adding board name to ALLWIFIBOARDS * Placing file(s) in this directory named as board-<devicename>.<qca4019|qca9888|qca9984> * Adding $(eval $(call generate-ipq-wifi-package,<device>,<display name>)) (along with suitable package selection for the board) At this time, QCA4019, QCA9888, and QCA9984 are supported. Extension to other chips should be straightforward. The existing files, board-*.bin, are "grandfathered" as QCA4019. The package name has been retained for compatability reasons. At this time it DEPENDS:=@TARGET_ipq40xx, limiting its visibility. Build-tested-on: asus_map-ac2200, alfa-network_ap120c-ac, avm_fritzbox-7530, avm_fritzrepeater-3000, engenius_eap1300, engenius_ens620ext, linksys_ea6350v3, qxwlan-e2600ac-c1/-c2 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
5 years ago
# Add board name to ALLWIFIBOARDS
# Place files in this directory as board-<devicename>.<qca4019|qca9888|qca9984>
# Add $(eval $(call generate-ipq-wifi-package,<devicename>,<display name>))
$(eval $(call generate-ipq-wifi-package,alfa-network_ap120c-ac,ALFA Network AP120C-AC))
$(eval $(call generate-ipq-wifi-package,asus_map-ac2200,ASUS MAP-AC2200))
$(eval $(call generate-ipq-wifi-package,avm_fritzbox-7530,AVM FRITZ!Box 7530))
$(eval $(call generate-ipq-wifi-package,avm_fritzrepeater-3000,AVM FRITZ!Repeater 3000))
$(eval $(call generate-ipq-wifi-package,engenius_eap1300,EnGenius EAP1300))
$(eval $(call generate-ipq-wifi-package,engenius_ens620ext,EnGenius ENS620EXT))
$(eval $(call generate-ipq-wifi-package,linksys_ea6350v3,Linksys EA6350v3))
$(eval $(call generate-ipq-wifi-package,qxwlan_e2600ac,Qxwlan E2600AC))
firmware: add custom IPQ wifi board definitions On the ath10k-devel ML Michael Kazior stated: "board-2 is a key-value store of actual board files. Some devices, notably qca61x4 hw3+ and qca4019 need distinct board files to be uploaded. Otherwise they fail in various ways." [0]. Later on Rajkumar Manoharan explained: "In QCA4019 platform, only radio specific calibration (pre-cal-data) is stored in flash. Board specific contents are read from board-2.bin. For each radio appropriate board data should be loaded. To fetch correct board data from board-2.bin bundle, pre-cal/radio specific caldata should be loaded first to get proper board id. |My understanding until now was that: | | * pre-cal data + board-2.bin info == actual calibration data Correct." [1]. The standard board-2.bin from the ath10k-firmware-qca4019 barely works on the RT-AC58U. Especially 5GHz clients fail to connect at all and if they do, they have very low throughput even right next to the router. Currently, the solution for this problem is to supply a custom board-2.bin for every device. To implement this feature, this method makes use of: Rafał Miłecki's "base-files: add support for overlaying rootfs content". This comes with a few limitations: 1. Since there can only be one board-2.bin at the right location, there can only one board overwrite installed at any time. (All packages CONFLICT with each other. It's also not possible to "builtin" multiple package.) 2. updating ath10k-firmware-qca4019 will also replace the board-2.bin. For this cases the user needs to manually reinstall the wifi-board package once the ath10k-firmware-qca4019 is updated. To create the individual board-2.bin: Use the ath10k-bdencoder utility from the qca-swiss-army-knife repository: <https://github.com/qca/qca-swiss-army-knife> The raw board.bin files have to be extracted from the vendor's source GPL.tar archieves. Signed-off-by: Alexis Green <agreen@cococorp.com> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
7 years ago
$(foreach PACKAGE,$(ALLWIFIPACKAGES),$(eval $(call BuildPackage,$(PACKAGE))))