Re: Linux kernel 6.1 or 6.6 for OpenWrt 24.x release?
sob., 3 lut 2024 o 13:08 Hauke Mehrtens napisał(a): > > Hi, > > I track the status of the Linux kernel 6.1 migration in this github > issue: https://github.com/openwrt/openwrt/issues/14546 > > There are still many targets on kernel 5.15 without testing support for > kernel 6.1 in OpenWrt master. I assume that we need at least 4 months to > get everything to 6.1 and more or less stable. Kernel 6.1 support is > also missing for some important targets like lantiq, realtek and ramips. > > > Which kernel should we use for the next major OpenWrt release? > We have two options and I would like to get some feedback on these: > > 1. Do the OpenWrt 24.X release with kernel 6.1. Branch off when all or > most of the targets are on kernel 6.1 by default. > 2. Do the OpenWrt 24.X release with kernel 6.6. Branch off when all or > most of the targets are on kernel 6.6 by default. Do not do any stable > OpenWrt release which supports kernel 6.1. > > Doing a OpenWrt release with multiple kernels cases too much maintenance > effort from my point of view based on previews experience. > > > I think with kernel 6.1 we can branch off at around May 2024. With > kernel 6.6 we could probably branch off around September 2024. The final > release will be out about 2 to 4 months later. > > Currently OpenWrt releases are about 1.5 years behind the Linux LTS > releases. When we use kernel 6.1 for the next release we will continue > to stay 1.5 years behind. When we switch to kernel 6.6 and do not do any > release with kernel 6.1 we will probably only stay 10 months behind > Linux LTS kernels. > > There is already a PR requiring kernel 6.6: > https://github.com/openwrt/openwrt/pull/14357 > > > Currently I would prefer to use kernel 6.6 to get closer to the recent > Linux LTS releases. > 6.6 for sure if possible. Just curious - any reason to not support both or even 5.15? And target could decide about it in mk? Eg. newest ATH/QCA that base a lot on newest kernel and backports just could choose it? For older one we already have work done - so just change generic patches directory into generic-kernel_ver? Or this is more work and problems? BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] firmware: add Intel BE200 firmware
Signed-off-by: Janusz Dziedzic --- package/firmware/linux-firmware/intel.mk | 8 1 file changed, 8 insertions(+) diff --git a/package/firmware/linux-firmware/intel.mk b/package/firmware/linux-firmware/intel.mk index 27b0d8ce64..19a96b2c85 100644 --- a/package/firmware/linux-firmware/intel.mk +++ b/package/firmware/linux-firmware/intel.mk @@ -192,6 +192,14 @@ define Package/iwlwifi-firmware-ax210/install endef $(eval $(call BuildPackage,iwlwifi-firmware-ax210)) +Package/iwlwifi-firmware-be200 = $(call Package/firmware-default,Intel BE200 firmware) +define Package/iwlwifi-firmware-be200/install + $(INSTALL_DIR) $(1)/lib/firmware + $(INSTALL_DATA) $(PKG_BUILD_DIR)/iwlwifi-gl-c0-fm-c0-83.ucode $(1)/lib/firmware + $(INSTALL_DATA) $(PKG_BUILD_DIR)/iwlwifi-gl-c0-fm-c0.pnvm $(1)/lib/firmware +endef +$(eval $(call BuildPackage,iwlwifi-firmware-be200)) + Package/e100-firmware = $(call Package/firmware-default,Intel e100) define Package/e100-firmware/install $(INSTALL_DIR) $(1)/lib/firmware/e100 -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH 1/2] ath12k: enable compilation
Signed-off-by: Janusz Dziedzic --- package/kernel/mac80211/Makefile | 2 ++ package/kernel/mac80211/ath.mk| 22 +-- ...2k-fix-compilation-with-older-kernel.patch | 28 +++ 3 files changed, 50 insertions(+), 2 deletions(-) create mode 100644 package/kernel/mac80211/patches/ath12k/0001-wifi-ath12k-fix-compilation-with-older-kernel.patch diff --git a/package/kernel/mac80211/Makefile b/package/kernel/mac80211/Makefile index 17e0d9451e..f980d1deb6 100644 --- a/package/kernel/mac80211/Makefile +++ b/package/kernel/mac80211/Makefile @@ -341,6 +341,7 @@ define Build/Patch $(call PatchDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/ath9k,ath9k/) $(call PatchDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/ath10k,ath10k/) $(call PatchDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/ath11k,ath11k/) + $(call PatchDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/ath12k,ath12k/) $(call PatchDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/rt2x00,rt2x00/) $(call PatchDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/mt7601u,mt7601u/) $(call PatchDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/mwl,mwl/) @@ -357,6 +358,7 @@ define Quilt/Refresh/Package $(call Quilt/RefreshDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/ath9k,ath9k/) $(call Quilt/RefreshDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/ath10k,ath10k/) $(call Quilt/RefreshDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/ath11k,ath11k/) + $(call Quilt/RefreshDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/ath12k,ath12k/) $(call Quilt/RefreshDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/rt2x00,rt2x00/) $(call Quilt/RefreshDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/mt7601u,mt7601u/) $(call Quilt/RefreshDir,$(PKG_BUILD_DIR),$(PATCH_DIR)/mwl,mwl/) diff --git a/package/kernel/mac80211/ath.mk b/package/kernel/mac80211/ath.mk index 881c89db25..beb1b2ae4f 100644 --- a/package/kernel/mac80211/ath.mk +++ b/package/kernel/mac80211/ath.mk @@ -1,6 +1,6 @@ PKG_DRIVERS += \ ath ath5k ath6kl ath6kl-sdio ath6kl-usb ath9k ath9k-common ath9k-htc ath10k ath10k-smallbuffers \ - ath11k ath11k-ahb ath11k-pci carl9170 owl-loader ar5523 wil6210 + ath11k ath11k-ahb ath11k-pci ath12k carl9170 owl-loader ar5523 wil6210 PKG_CONFIG_DEPENDS += \ CONFIG_PACKAGE_ATH_DEBUG \ @@ -21,6 +21,7 @@ ifdef CONFIG_PACKAGE_MAC80211_DEBUGFS ATH9K_HTC_DEBUGFS \ ATH10K_DEBUGFS \ ATH11K_DEBUGFS \ + ATH12K_DEBUGFS \ CARL9170_DEBUGFS \ ATH5K_DEBUG \ ATH6KL_DEBUG \ @@ -31,6 +32,7 @@ ifdef CONFIG_PACKAGE_MAC80211_TRACING config-y += \ ATH10K_TRACING \ ATH11K_TRACING \ + ATH12K_TRACING \ ATH6KL_TRACING \ ATH_TRACEPOINTS \ ATH5K_TRACER \ @@ -38,7 +40,7 @@ ifdef CONFIG_PACKAGE_MAC80211_TRACING endif config-$(call config_package,ath) += ATH_CARDS ATH_COMMON -config-$(CONFIG_PACKAGE_ATH_DEBUG) += ATH_DEBUG ATH10K_DEBUG ATH11K_DEBUG ATH9K_STATION_STATISTICS +config-$(CONFIG_PACKAGE_ATH_DEBUG) += ATH_DEBUG ATH10K_DEBUG ATH11K_DEBUG ATH12K_DEBUG ATH9K_STATION_STATISTICS config-$(CONFIG_PACKAGE_ATH_DFS) += ATH9K_DFS_CERTIFIED ATH10K_DFS_CERTIFIED config-$(CONFIG_PACKAGE_ATH_SPECTRAL) += ATH9K_COMMON_SPECTRAL ATH10K_SPECTRAL ATH11K_SPECTRAL config-$(CONFIG_PACKAGE_ATH_DYNACK) += ATH9K_DYNACK @@ -63,6 +65,7 @@ config-$(call config_package,ath10k-smallbuffers) += ATH10K ATH10K_PCI ATH10K_SM config-$(call config_package,ath11k) += ATH11K config-$(call config_package,ath11k-ahb) += ATH11K_AHB config-$(call config_package,ath11k-pci) += ATH11K_PCI +config-$(call config_package,ath12k) += ATH12K config-$(call config_package,ath5k) += ATH5K ifdef CONFIG_TARGET_ath25 @@ -349,6 +352,21 @@ This module adds support for Qualcomm Technologies 802.11ax family of chipsets with PCI bus. endef +define KernelPackage/ath12k + $(call KernelPackage/mac80211/Default) + TITLE:=Qualcomm 802.11be wireless chipset support + URL:=https://wireless.wiki.kernel.org/en/users/drivers/ath12k + DEPENDS+= +kmod-ath +@DRIVER_11AC_SUPPORT +@DRIVER_11AX_SUPPORT \ + +@DRIVER_11BE_SUPPORT +kmod-crypto-michael-mic +kmod-qrtr-mhi + FILES:=$(PKG_BUILD_DIR)/drivers/soc/qcom/qmi_helpers.ko \ + $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath12k/ath12k.ko +endef + +define KernelPackage/ath12k/description +This module adds support for Qualcomm Technologies 802.11be family of +chipsets with PCI bus. +endef + define KernelPackage/carl9170 $(call KernelPackage/mac80211/Default) TITLE:=Driver for Atheros AR9170 USB sticks diff --git a/package/kernel/mac80211/patches/ath12k/0001-wifi-ath12k-fix-compilation-with-older-kernel.patch b/package/kernel/mac80211/patches/ath12k/0001-wifi-ath12k-fix-compilation-with-older-kernel.patch new file mode 100644 index 00..d51e5f8e9c --- /dev/null +++ b/package/kernel/mac80211/patches/ath12k/0001-wifi-ath12k-fix-compilation-with-older-kernel.patch @@ -0,0 +1,28 @@ +--- a/drivers/net/wireless/ath/ath12k/core.c b/drivers/net/wireless/ath/ath12k/core.c +@@ -886,7
[PATCH 2/2] ath11k/ath12k: fix when build together
Signed-off-by: Janusz Dziedzic --- package/kernel/mac80211/ath.mk | 22 +++--- 1 file changed, 15 insertions(+), 7 deletions(-) diff --git a/package/kernel/mac80211/ath.mk b/package/kernel/mac80211/ath.mk index beb1b2ae4f..b66049b18a 100644 --- a/package/kernel/mac80211/ath.mk +++ b/package/kernel/mac80211/ath.mk @@ -1,6 +1,6 @@ PKG_DRIVERS += \ ath ath5k ath6kl ath6kl-sdio ath6kl-usb ath9k ath9k-common ath9k-htc ath10k ath10k-smallbuffers \ - ath11k ath11k-ahb ath11k-pci ath12k carl9170 owl-loader ar5523 wil6210 + ath11k ath11k-ahb ath11k-pci ath12k carl9170 owl-loader ar5523 wil6210 qcom-qmi-helpers PKG_CONFIG_DEPENDS += \ CONFIG_PACKAGE_ATH_DEBUG \ @@ -59,6 +59,7 @@ config-$(CONFIG_ATH10K_LEDS) += ATH10K_LEDS config-$(CONFIG_ATH10K_THERMAL) += ATH10K_THERMAL config-$(CONFIG_ATH11K_THERMAL) += ATH11K_THERMAL +config-$(call config_package,qcom-qmi-helpers) += QCOM_QMI_HELPERS config-$(call config_package,ath9k-htc) += ATH9K_HTC config-$(call config_package,ath10k) += ATH10K ATH10K_PCI config-$(call config_package,ath10k-smallbuffers) += ATH10K ATH10K_PCI ATH10K_SMALLBUFFERS @@ -300,14 +301,21 @@ define KernelPackage/ath10k-smallbuffers VARIANT:=smallbuffers endef +define KernelPackage/qcom-qmi-helpers + $(call KernelPackage/mac80211/Default) + TITLE:=Qualcomm QMI backports helpers + FILES:=$(PKG_BUILD_DIR)/drivers/soc/qcom/qmi_helpers.ko + AUTOLOAD:=$(call AutoProbe,qmi_helpers) +endef + define KernelPackage/ath11k $(call KernelPackage/mac80211/Default) TITLE:=Qualcomm 802.11ax wireless chipset support (common code) URL:=https://wireless.wiki.kernel.org/en/users/drivers/ath11k DEPENDS+= +kmod-ath +@DRIVER_11AC_SUPPORT +@DRIVER_11AX_SUPPORT \ - +kmod-crypto-michael-mic +ATH11K_THERMAL:kmod-hwmon-core +ATH11K_THERMAL:kmod-thermal - FILES:=$(PKG_BUILD_DIR)/drivers/soc/qcom/qmi_helpers.ko \ - $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath11k/ath11k.ko + +kmod-crypto-michael-mic +ATH11K_THERMAL:kmod-hwmon-core +ATH11K_THERMAL:kmod-thermal \ + +kmod-qcom-qmi-helpers + FILES:=$(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath11k/ath11k.ko endef define KernelPackage/ath11k/description @@ -357,9 +365,9 @@ define KernelPackage/ath12k TITLE:=Qualcomm 802.11be wireless chipset support URL:=https://wireless.wiki.kernel.org/en/users/drivers/ath12k DEPENDS+= +kmod-ath +@DRIVER_11AC_SUPPORT +@DRIVER_11AX_SUPPORT \ - +@DRIVER_11BE_SUPPORT +kmod-crypto-michael-mic +kmod-qrtr-mhi - FILES:=$(PKG_BUILD_DIR)/drivers/soc/qcom/qmi_helpers.ko \ - $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath12k/ath12k.ko + +@DRIVER_11BE_SUPPORT +kmod-crypto-michael-mic +kmod-qrtr-mhi \ + +kmod-qcom-qmi-helpers + FILES:=$(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath12k/ath12k.ko endef define KernelPackage/ath12k/description -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: ath11k (QCA6390) on master in bpi-r64 - some issues
Sorry for the noise, it was physical connection issue. Now I see it works correctly: [8.360566] mhi mhi0: Wait for device to enter SBL or Mission mode [8.475137] kmodloader: done loading kernel modules from /etc/modules.d/* [8.482058] ath11k_pci :01:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [8.490929] ath11k_pci :01:00.0: fw_version 0x10121492 fw_build_timestamp 2021-11-04 11:23 fw_build_id [8.586184] ath11k_pci :01:00.0: leaving PCI ASPM disabled to avoid MHI M2 problems BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ath11k (QCA6390) on master in bpi-r64 - some issues
Hello, Any idea what is wrong? [7.574630] NET: Registered PF_PPPOX protocol family [7.588974] ath11k_pci :01:00.0: assign IRQ: got 0 [7.594475] ath11k_pci :01:00.0: BAR 0: assigned [mem 0x2000-0x20ff 64bit] [7.602644] ath11k_pci :01:00.0: enabling device ( -> 0002) [7.609007] ath11k_pci :01:00.0: enabling bus mastering [7.614928] mtk-pcie 1a143000.pcie: msi#0 address_hi 0x0 address_lo 0x44ed50c0 [7.617849] mt7622-wmac 1800.wmac: N9 Firmware Version: _reserved_, Build Time: 20220630094834 [7.622289] ath11k_pci :01:00.0: MSI vectors: 1 [7.636070] ath11k_pci :01:00.0: qca6390 hw2.0 [7.640890] ath11k_pci :01:00.0: FW memory mode: 0 [7.803924] mhi mhi0: Requested to power ON [7.808149] mhi mhi0: Power on setup success [8.370999] mhi mhi0: Wait for device to enter SBL or Mission mode root@OpenWrt:/# lspci 00:00.0 PCI bridge: MEDIATEK Corp. Device 3258 01:00.0 Unassigned class [ff00]: Qualcomm QCA6390 Wireless Network Adapter root@OpenWrt:/# uname -a Linux OpenWrt 6.1.74 #0 SMP Mon Jan 22 20:06:53 2024 aarch64 GNU/Linux root@OpenWrt:/# lsmod |grep ath ath11k450560 1 ath11k_pci ath11k_pci 20480 0 cfg80211 303104 8 iwlmvm,iwldvm,ath11k,mt7615_common,mt76_connac_lib,mt76,mac80211,iwlwifi compat 16384 6 iwlmvm,iwldvm,ath11k_pci,mac80211,iwlwifi,cfg80211 mac80211 589824 7 iwlmvm,iwldvm,ath11k,mt7615e,mt7615_common,mt76_connac_lib,mt76 mhi73728 2 ath11k_pci,qrtr_mhi qmi_helpers20480 1 ath11k BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt One - celebrating 20 years of OpenWrt
śr., 17 sty 2024 o 18:15 Daniel Golle napisał(a): > > On Wed, Jan 17, 2024 at 05:47:26PM +0100, John Crispin wrote: > > > > On 17.01.24 17:46, Janusz Dziedzic wrote: > > > Do you think I can use m.2 A->M converter here and use wifi mt7916 A+E > > > (6GHz) instead of NVMe? > > > Eg.https://kamami.pl/akcesoria-do-raspberry-pi/587051-m2-m-key-to-m2-a-key-adapter-m2-m-key-do-m2-a-key.html > > > Will that work? > > > > so the theory but we wont know until we try. > > I've tried that on BPi-R3 with MT7921K module, and that worked > fine. I don't see a reason why it wouldn't work on a very similar > MediaTek SoC -- we just need to make sure the power budget of the > M.2 slot is enough for even WiFi modules more power hungry than > MT7921K (I assume MT7916E wants quite a bit more juice). Also did test today - bpi-r3 + m2 M -> A adapter + intel ax200. Seems works fine - hope will be same here, so could extend it and have AX/BE. root@bpi-r3-os-0014555f4dd7:/# lspci 00:00.0 PCI bridge: MEDIATEK Corp. Device 1f32 (rev 01) 01:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) root@bpi-r3-os-0014555f4dd7:/# root@bpi-r3-os-0014555f4dd7:/# dmesg|grep iwl [ 15.693504] iwlwifi :01:00.0: assign IRQ: got 144 [ 15.698560] iwlwifi :01:00.0: enabling device ( -> 0002) [ 15.704665] iwlwifi :01:00.0: enabling bus mastering [ 16.335900] iwlwifi :01:00.0: api flags index 2 larger than supported by driver [ 16.343604] iwlwifi :01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 16.428220] iwlwifi :01:00.0: loaded firmware version 72.daa05125.0 cc-a0-72.ucode op_mode iwlmvm [ 16.445463] iwlwifi :01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 [ 16.587848] iwlwifi :01:00.0: Detected RF HR B3, rfid=0x10a100 [ 16.657202] iwlwifi :01:00.0: base HW address: 5c:80:b6:fe:0c:b8 root@bpi-r3-os-0014555f4dd7:/# root@bpi-r3-os-0014555f4dd7:/# ls /sys/class/ieee80211/ phy0 phy1 phy2 root@bpi-r3-os-0014555f4dd7:/ BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt One - celebrating 20 years of OpenWrt
śr., 17 sty 2024 o 16:27 John Crispin napisał(a): > > Additional FAQ for OpenWrt One > > This is a summary of some further questions regarding the OpenWrt One > project gathered so far. After OpenWrt voted to move forward, it will be > converted into a page within the OpenWrt wiki as a place for collecting > the latest information. > > Q: Will the various hardware buttons and switches be fully exposed on > the outside? > A: The latest iteration of the design will fully expose all buttons and > switches. > > Q: Will there be an option to purchase preassembled kits? > A: We're considering that option but still need to explore possibilities > with the manufacturer. > > Q: When do you expect general availability? > A: Once we vote to move forward, it will take around 45 days until the > first PCBA engineering samples get shipped. These will be passed on to > developers for testing. Once they are verified it will probably take > another 30-45 days until they can be ordered. So we are looking at April > timeframe. > > Q: What kind of power supply is needed? > A: While the initial announcement imprecisely referred to the power > supply as "USB-PD 12V" the PCB will draw its required power from a USB-C > PD 3.0/2.0 source. > > Q: Why does the current design not feature any USB 3.0 connectivity? > A: USB 3.0 always has the risk of interference with 2.4 GHz Wi-Fi. We > would like to reduce risk as much as possible. Interference proofing the > board would add considerable complexity and costs. > > Q: Why did you implement a M.2 slot? > A: After careful consideration we came to the conclusion that directly > exposing a PCIe 1x lane in the form of an M.2 slot provides the most > flexibility for potential expansions. It can be used for NVMe storage > (up to 2242 when using an enclosure), e.g. to host containers or media > files. It also enables the simple use of other, non-OpenWrt > distributions with larger storage footprints. > Do you think I can use m.2 A->M converter here and use wifi mt7916 A+E (6GHz) instead of NVMe? Eg. https://kamami.pl/akcesoria-do-raspberry-pi/587051-m2-m-key-to-m2-a-key-adapter-m2-m-key-do-m2-a-key.html Will that work? > Q: Why is there no consideration for Wi-Fi 6E/7 (6GHz / Tri-Band)? > A: Neither is the mac80211 upstream support for Wi-Fi 7 complete, nor is > there a fully integrated tri-band SoC solution available right now, let > alone fully or partially supported upstream. Supporting Wi-Fi 7 would > drastically increase the overall costs and make it impossible to deliver > sufficient software support in the foreseeable future. > > Q: Why are there only two ethernet ports? > A: We didn't want to impose additional complexity and costs by including > an external managed switch IC. One port is 1GBit/s capable, while the > other features a speed up to 2.5GBit/s. This is a limitation of the > chosen SoC. > > Q: Why should I get the One? There are more capable, more featured > devices available! > A: The OpenWrt One is intended to serve as a robust and simple > educational platform for OpenWrt enthusiasts, it is neither intended to > be a competitor to off the shelf SOHO routers nor do we aim for the > largest possible amount of features. It also serves as a donation > vehicle for the OpenWrt project. > > Q: Does that mean that OpenWrt will stop supporting other hardware? > A: There is no intention at all to change the way OpenWrt operates or > how it implements and supports current and future hardware. The OpenWrt > One device will be supported as one device among many others and receive > the same level of support. > > Q: Doesn't this draw attention away from properly supporting existing > devices? > A: The OpenWrt One project is a privately led initiative by a few > enthusiasts, there is no intent to change the focus of the OpenWrt > project in any way. > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Janusz Dziedzic ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
23.05.2 - Xiaomi Redmi AX6000 - strange wifi msgs
Hello, See this: [986954.422624] ieee80211 phy0: WA: free done event [986954.422624] 10225940 [986954.422624] len = 36 [986954.422624] DW0 : 24 00 06 30 [986954.422624] DW1 : 03 e0 34 4f [986954.422624] DW2 : 00 40 01 89 [986954.422624] DW3 : 06 50 00 41 [986954.422624] DW4 : 3c 80 1e 00 [986954.422624] DW5 : 04 30 00 41 [986954.422624] DW6 : 3e 80 1f 00 [986954.422624] DW7 : 02 10 00 41 [986954.422624] DW8 : 00 80 0b 00 [995116.578072] ieee80211 phy0: WA: free done event [995116.578072] 10229180 [995116.578072] len = 24 [995116.578072] DW0 : 18 00 03 30 [995116.578072] DW1 : 01 cb c4 1d [995116.578072] DW2 : 00 40 01 90 [995116.578072] DW3 : 02 58 23 41 [995116.578072] DW4 : 01 00 01 00 [995116.578072] DW5 : d7 88 ff 3f [1149271.247080] ieee80211 phy0: WA: free done event [1149271.247080] 10228500 [1149271.247080] len = 24 [1149271.247080] DW0 : 18 00 03 30 [1149271.247080] DW1 : 01 0a c4 0b [1149271.247080] DW2 : 00 40 01 90 [1149271.247080] DW3 : 02 48 1f 41 [1149271.247080] DW4 : 01 00 01 00 [1149271.247080] DW5 : d0 87 ff 3f root@ax6000:~# lsmod |grep mt cfg80211 290816 4 mt7915e,mt76_connac_lib,mt76,mac80211 mac80211 573440 3 mt7915e,mt76_connac_lib,mt76 mt76 69632 2 mt7915e,mt76_connac_lib mt76_connac_lib53248 1 mt7915e mt7915e 139264 0 root@ax6000:~# [8.752037] mt798x-wmac 1800.wifi: HW/SW Version: 0x8a108a10, Build Time: 20221012174648a [9.086738] mt798x-wmac 1800.wifi: WM Firmware Version: 00, Build Time: 20221012174725 [9.238900] mt798x-wmac 1800.wifi: WA Firmware Version: DEV_00, Build Time: 20221012174937 BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: hostapd crash
sob., 13 sty 2024 o 11:37 e9hack napisał(a):
>
> Hi,
>
> I did add one more AP to my wifi config for testing. This results in hostapd
> not starting for this device:
>
> Thu Jan 11 13:59:12 2024 daemon.notice hostapd: Exception in ubus function:
> left-hand side expression is null In __iface_pending_next(), file
> /usr/share/hostap/hostapd.uc, line 165, byte 73: called from function
> iface_pending_next (/usr/share/hostap/hostapd.uc:181:73) called from
> function iface_pending_init (/usr/share/hostap/hostapd.uc:222:15) called
> from function iface_restart (/usr/share/hostap/hostapd.uc:249:35) called
> from function iface_set_config (/usr/share/hostap/hostapd.uc:620:52) called
> from function [anonymous function] (/usr/share/hostap/hostapd.uc:827:32)
> called from anonymous function (/usr/share/hostap/hostapd.uc:710:22) `
> hostapd.printf(`hostapd.add_iface failed for phy ${phy}
> ifname=${bss.ifname}`);` Near here
> ---^
> Thu Jan 11 13:59:12 2024 daemon.notice netifd: radio1 (405): Command failed:
> ubus call hostapd config_set { "phy": "phy1",
> "config":"/var/run/hostapd-phy1.conf", "prev_config":
> "/var/run/hostapd-phy1.conf.prev"} (Unknown error)
>
> My hostapd.uc is modified. The affected line number does have an offset by 1
> related to the original file:
>
> diff --git a/package/network/services/hostapd/files/hostapd.uc
> b/package/network/services/hostapd/files/hostapd.uc
> index 0c89cd71cc..66e4e2353e 100644
> --- a/package/network/services/hostapd/files/hostapd.uc
> +++ b/package/network/services/hostapd/files/hostapd.uc
> @@ -20,6 +20,7 @@ hostapd.data.file_fields = {
> private_key2: true,
> dh_file: true,
> eap_sim_db: true,
> + crl_file: true,
> };
>
> function iface_remove(cfg)
>
>
> The error doesn't appear when I remove a AP. It doesn't matter which one I
> remove.
>
> Is there somewhere a buffer to small?
>
I don't see it on 23.05.2 and banana pi r3:
root@bpi-r3-os-0014555f4dd7:~# iw dev
phy#1
Interface wlan1-1
ifindex 17
wdev 0x10003
addr 06:14:55:5f:4d:d9
ssid MAP-0014555F4DD7-BH-5GHz
type AP
channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
txpower 23.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
Interface wlan1
ifindex 14
wdev 0x10002
addr 04:14:55:5f:4d:d9
ssid OpenWrt-0014555F4DD7
type AP
channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz
txpower 23.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 20 0 0 0 0 1320 20
phy#0
Interface wlan0-1.sta1
ifindex 18
wdev 0x4
addr 02:14:55:5f:4d:d9
type AP/VLAN
channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
txpower 20.00 dBm
4addr: on
Interface wlan0-1
ifindex 16
wdev 0x3
addr 02:14:55:5f:4d:d9
ssid MAP-0014555F4DD7-BH-2.4GHz
type AP
channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
txpower 20.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
Interface wlan0
ifindex 15
wdev 0x2
addr 00:14:55:5f:4d:d9
ssid OpenWrt-0014555F4DD7
type AP
channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
txpower 20.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 154 0 0 0 5 11892 154
root@bpi-r3-os-0014555f4dd7:~# ubus list |grep hostapd
hostapd
hostapd.wlan0
hostapd.wlan0-1
hostapd.wlan1
hostapd.wlan1-1
root@bpi-r3-os-0014555f4dd7:~#
BR
Janusz
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt One - celebrating 20 years of OpenWrt
wt., 9 sty 2024 o 18:59 Daniel Golle napisał(a): > > On Tue, Jan 09, 2024 at 06:49:04PM +0100, Janusz Dziedzic wrote: > > wt., 9 sty 2024 o 18:02 Robert Marko napisał(a): > > > > > > On Tue, 9 Jan 2024 at 17:53, Rafał Miłecki wrote: > > > > > > > > On 9.01.2024 13:29, John Crispin wrote: > > > > > On 09.01.24 12:56, Robert Marko wrote: > > > > >> ---SNIP--- > > > > >> > > > > >>> Why not 6GHz? > > > > >> 6GHz requires an external card, and I doubt you can fit that in the > > > > >> target price. > > > > >> > > > > >> Regards, > > > > >> Robert > > > > > > > > > > correct. as mentioned in the email, we wanted to start out small. > > > > > also upstream mac80211 is still missing a bunch of 11be related > > > > > features. > > > > > > > > 6 GHz doesn't imply 802.11be, does it? I'm really not sure. > > > > > > > > Does MediaTek have any 802.11ax solutions that cover both: 5 GHz and > > > > 6 GHz? Maybe it'd be worth checking if that's an option and then use > > > > voting to see if people care? > > > > > > You can use 6GHz as part of 802.11ax as well, but you need an external > > > card or > > > you need to sacrifice the built-in 5GHz for 6GHz and that isn't really > > > a good idea > > > in my opinion. > > > > > Even will be 150$ it is still good price for router with 2.4/5/6GHz > > (MTK base ACER predator W6 is about 200$). > > Or at least add extra m2 AE Key slot - then we can put there mt7916 > > card, as possible extension (eg. > > https://asiarf.com/product/wi-fi-6e-m-2-ae-key-module-mt7916-aw7916-aed/). > > What will be price in case of this extra m2 AE Key slot? > > You can use M.2 key adapters for that > https://www.delock.com/produkt/63343/merkmale.html > > An additional slot is *not* an option as we got only a single PCIe lane. > > Hopefully there are also going to be single-band (6 GHz only) 4T4R or > even 4T5R modules based on MT7916E available at some point... Seems bpi-r4 will use two miniPCIe slots for that: https://wiki.banana-pi.org/Getting_Started_with_BPI-R4#4.29_Wi-Fi7_NIC If we don't have two PCIe then probably no option for 6ghz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt One - celebrating 20 years of OpenWrt
wt., 9 sty 2024 o 18:02 Robert Marko napisał(a): > > On Tue, 9 Jan 2024 at 17:53, Rafał Miłecki wrote: > > > > On 9.01.2024 13:29, John Crispin wrote: > > > On 09.01.24 12:56, Robert Marko wrote: > > >> ---SNIP--- > > >> > > >>> Why not 6GHz? > > >> 6GHz requires an external card, and I doubt you can fit that in the > > >> target price. > > >> > > >> Regards, > > >> Robert > > > > > > correct. as mentioned in the email, we wanted to start out small. also > > > upstream mac80211 is still missing a bunch of 11be related features. > > > > 6 GHz doesn't imply 802.11be, does it? I'm really not sure. > > > > Does MediaTek have any 802.11ax solutions that cover both: 5 GHz and > > 6 GHz? Maybe it'd be worth checking if that's an option and then use > > voting to see if people care? > > You can use 6GHz as part of 802.11ax as well, but you need an external card or > you need to sacrifice the built-in 5GHz for 6GHz and that isn't really > a good idea > in my opinion. > Even will be 150$ it is still good price for router with 2.4/5/6GHz (MTK base ACER predator W6 is about 200$). Or at least add extra m2 AE Key slot - then we can put there mt7916 card, as possible extension (eg. https://asiarf.com/product/wi-fi-6e-m-2-ae-key-module-mt7916-aw7916-aed/). What will be price in case of this extra m2 AE Key slot? BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt One - celebrating 20 years of OpenWrt
wt., 9 sty 2024 o 13:21 Daniel Golle napisał(a): > > On Tue, Jan 09, 2024 at 12:56:55PM +0100, Robert Marko wrote: > > ---SNIP--- > > > > > Why not 6GHz? > > > > 6GHz requires an external card, and I doubt you can fit that in the > > target price. > > Afaik we could use MT7976A as DBDC front-end supporting 2.4 GHz + 5/6 GHz > instead of MT7976C which only supports 2.4 GHz + 5 GHz. > However, that would still cover only two bands and most people will want > 6 GHz *in addition* to the 5 GHz band and not instead. Exactly, I think HW without 6GHz is useless this days. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: OpenWrt One - celebrating 20 years of OpenWrt
wt., 9 sty 2024 o 11:54 John Crispin napisał(a): > > tl;dr > > In 2024 the OpenWrt project turns 20 years! Let's celebrate this > anniversary by launching our own first and fully upstream supported > hardware design. > > If the community likes the idea outlined below in greater details, we > would like to start a vote. > > --- > > The idea > > It is not new. We first spoke about this during the OpenWrt Summits in > 2017 and also 2018. It became clear start of December 2023 while > tinkering with Banana Pi style devices that they are already pretty > close to what we wanted to achieve in ’17/‘18. Banana PIs have grown in > popularity within the community. They boot using a self compiled Trusted > Firmware-A (TF-A)and upstream U-Boot (thx MTK/Daniel) and some of the > boards are already fully supported by the upstream Linux kernel. The > only nonopen sourcecomponents are the 2.5 GbE PHYandWi-Fi firmware > blobsrunning on separate cores that areindependent of the main SoC > running Linuxand the DRAM calibration routines which are executed early > during boot. > > I contacted three project members (pepe2k, dangole, nbd) on December 6th > to outline the overall idea. We went over several design proposals, At > the beginning we focused on the most powerful (and expensive) > configurations possible but finally ended up with something rather > simple and above all,feasible. We would like to propose the following as > our "first" community driven HW platform called "OpenWrt One/AP-24.XY". > > Together with pepe2k (thx a lot) I discussed this for many hours and we > worked out the following project proposal. Instead of going insane with > specifications, we decided to include some nice features we believe all > OpenWrt supported platforms should have (e.g. being almost > unbrickablewith multiple recovery options, hassle-free system console > access, on-board RTC with battery backup etc.). > > This is our first design, so let's KiSS! > > > Hardwarespecifications: > > * SOC: MediaTek MT7981B > * Wi-Fi: MediaTek MT7976C (2x2 2.4 GHz + 3x3/2x2 + zero-wait DFS 5Ghz) Why not 6GHz? BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Wifi MLO UCI config
Hello, Do you have some ideas how UCI wifi config should look like for MLO config. In such case we could see smth like: root@test:/# iw dev phy#0 Interface wlan0 ifindex 21 wdev 0x5 addr 00:03:7f:12:19:19 ssid TEST-MLO type AP link 0: addr 00:03:7f:12:19:19 channel 11 (2462 MHz), width: 20 MHz, center1: 2462 MHz txpower 29.00 dBm link 1: addr 00:03:7f:12:1a:1a channel 36 (5180 MHz), width: 80 MHz, center1: 5210 MHz txpower 28.00 dBm link 2: addr 00:03:7f:12:1b:1b channel 49 (6195 MHz), width: 320 MHz, center1: 6265 MHz txpower 22.00 dBm root@test:/# Seems for MLO single wiphy (multiband wiphy) will be used and single netdev wlan0 per ssid with multiple band also. Curious if someone already work on that and have some ideas how the wifi UCI config should looks like? Stay with current wifi-device/wifi-interface sections and add some additional options? Or introduce smth new - that will be closer to real iw tree? I just think about: conifg wifi-device 'radio0' option type 'mac80211' option path 'some_path' config wifi-interface 'iface0' option device 'radio0' option ifname 'wlan0' config wifi-link option band '2g' option interface 'iface0' option channel '11' option mode 'EHT20' config wifi-link option band '5g' option interface 'iface0' option channel '36' option mode 'EHT80' config wifi-link option band '6g' option interface 'iface0' option channel '49' option mode 'EHT320' If no config wifi-link - then wifi-device config should be used for interface (band/channel/htmode). Any idea what is best/better approach here? BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Ethernet switch with linux/openwrt and DSA
pt., 23 gru 2022 o 17:51 Michael Richardson napisał(a): > > > > Finally buy: D-LINK DGS-1210-48 G1. > Also - HP 1920-24G JG924A works correctly. But what about future? Is there any new device we can buy and use openwrt there? Or even 2.5Gbps/5Gbps? So far just buy used/older devices. > Is this a device that is still for sale? > I have some control plane things that I'd like to test on a variety of > switches. I using the Zyxel GS1900 now. > ZyXEL GS1900-48-EU0102F (new one) will be also fine? BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: two mt7915e cards and irq 149: nobody cared dump
czw., 5 sty 2023 o 20:24 Janusz Dziedzic napisał(a): > > czw., 5 sty 2023 o 16:41 Janusz Dziedzic > napisał(a): > > > > Hello, > > > > Have two mt7915e cards in my banana PI R64 (latest master). > > After do ifconfig wlan1 up - dump. > > While ifconfig wlan2 up works correctly. > > > > [7.093206] mt7915e :01:00.0: assign IRQ: got 148 > > [7.098405] mt7915e :01:00.0: enabling device ( -> 0002) > > [7.104537] mt7915e :01:00.0: enabling bus mastering > > [7.181837] mt7622-wmac 1800.wmac: N9 Firmware Version: > > _reserved_, Build Time: 20220630094834 > > [7.193914] Bluetooth: hci0: Device setup in 243529 usecs > > [7.233531] mtk-pcie 1a143000.pcie: msi#0 address_hi 0x0 address_lo > > 0x44e050c0 > > [7.291849] mt7915e :01:00.0: HW/SW Version: 0x8a108a10, Build > > Time: 20220929104113a > > [7.291849] > > [7.435118] mt7915e :01:00.0: WM Firmware Version: 00, > > Build Time: 20220929104145 > > [7.492309] mt7915e :01:00.0: WA Firmware Version: DEV_00, > > Build Time: 20220929104205 > > [7.655412] mt7915e 0001:01:00.0: assign IRQ: got 149 > > [7.660552] mt7915e 0001:01:00.0: enabling device ( -> 0002) > > [7.666722] mt7915e 0001:01:00.0: enabling bus mastering > > [7.783768] mtk-pcie 1a145000.pcie: msi#0 address_hi 0x0 address_lo > > 0x44e150c0 > > [7.803991] mt7915e 0001:01:00.0: HW/SW Version: 0x8a108a10, Build > > Time: 20220929104113a > > [7.803991] > > [7.822350] mt7915e 0001:01:00.0: WM Firmware Version: 00, > > Build Time: 20220929104145 > > [7.846429] mt7915e 0001:01:00.0: WA Firmware Version: DEV_00, > > Build Time: 20220929104205 > > > > > > > > # ifconfig wlan1 up > > > > Creating netns for phy2 on port 2302 > > [ 379.207067] irq 149: nobody cared (try booting with the "irqpoll" option) > > [ 379.213884] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G S > > 5.15.86 #0 > > [ 379.221291] Hardware name: Bananapi BPI-R64 (DT) > > [ 379.225909] Call trace: > > [ 379.228352] dump_backtrace+0x0/0x15c > > [ 379.232035] show_stack+0x14/0x30 > > [ 379.235359] dump_stack_lvl+0x64/0x7c > > [ 379.239030] dump_stack+0x14/0x2c > > [ 379.242351] __report_bad_irq+0x48/0x128 > > [ 379.246280] note_interrupt+0x2e4/0x340 > > [ 379.250124] handle_irq_event+0xb8/0xe0 > > [ 379.253965] handle_simple_irq+0xb0/0x10c > > [ 379.257980] generic_handle_domain_irq+0x28/0x3c > > [ 379.262610] mtk_pcie_intr_handler+0x144/0x19c > > [ 379.267064] handle_domain_irq+0x5c/0x8c > > [ 379.270999] gic_handle_irq+0x64/0x8c > > [ 379.274668] do_interrupt_handler+0x30/0x54 > > [ 379.278859] el1_interrupt+0x2c/0x4c > > [ 379.282446] el1h_64_irq_handler+0x14/0x20 > > [ 379.286547] el1h_64_irq+0x74/0x78 > > [ 379.289953] _stext+0xa0/0x294 > > [ 379.293012] __irq_exit_rcu+0xdc/0xfc > > [ 379.296680] irq_exit+0xc/0x1c > > [ 379.299738] handle_domain_irq+0x60/0x8c > > [ 379.303673] gic_handle_irq+0x64/0x8c > > [ 379.307340] call_on_irq_stack+0x28/0x44 > > [ 379.311269] do_interrupt_handler+0x4c/0x54 > > [ 379.315460] el1_interrupt+0x2c/0x4c > > [ 379.319045] el1h_64_irq_handler+0x14/0x20 > > [ 379.323145] el1h_64_irq+0x74/0x78 > > [ 379.326550] arch_cpu_idle+0x14/0x20 > > [ 379.330131] do_idle+0xc0/0x140 > > [ 379.333284] cpu_startup_entry+0x24/0x50 > > [ 379.337218] rest_init+0xc4/0xd0 > > [ 379.340451] arch_call_rest_init+0xc/0x14 > > [ 379.344471] start_kernel+0x5b4/0x5d4 > > [ 379.348144] __primary_switched+0xa0/0xa8 > > [ 379.352163] handlers: > > [ 379.354433] [<dd1abdd2>] pcie_pme_irq > > [ 379.358808] Disabling IRQ #149 > > > > And lspci: > root@OpenWrt:~# lspci > :00:00.0 PCI bridge: MEDIATEK Corp. Device 3258 > :01:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E > 802.11ax PCI Express Wireless Network Adapter > 0001:00:01.0 PCI bridge: MEDIATEK Corp. Device 3258 > 0001:01:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E > 802.11ax PCI Express Wireless Network Adapter > root@OpenWrt:~# > root@OpenWrt:~# > root@OpenWrt:~# lspci -tv > -+-[:00]---00.0-[01]00.0 MEDIATEK Corp. MT7915E 802.11ax PCI > Express Wireless Network Adapter > \-[0001:00]---01.0-[01]00.0 MEDIATEK Corp. MT7915E 802.11ax PCI > Express Wireless Network Adapter > root@OpenWrt:~# > root@OpenWrt:~# > root@OpenWrt:~# lspci -v > :00:00.0 PCI bridge: MEDIAT
Re: two mt7915e cards and irq 149: nobody cared dump
czw., 5 sty 2023 o 16:41 Janusz Dziedzic napisał(a): > > Hello, > > Have two mt7915e cards in my banana PI R64 (latest master). > After do ifconfig wlan1 up - dump. > While ifconfig wlan2 up works correctly. > > [7.093206] mt7915e :01:00.0: assign IRQ: got 148 > [7.098405] mt7915e :01:00.0: enabling device ( -> 0002) > [7.104537] mt7915e :01:00.0: enabling bus mastering > [7.181837] mt7622-wmac 1800.wmac: N9 Firmware Version: > _reserved_, Build Time: 20220630094834 > [7.193914] Bluetooth: hci0: Device setup in 243529 usecs > [7.233531] mtk-pcie 1a143000.pcie: msi#0 address_hi 0x0 address_lo > 0x44e050c0 > [7.291849] mt7915e :01:00.0: HW/SW Version: 0x8a108a10, Build > Time: 20220929104113a > [7.291849] > [7.435118] mt7915e :01:00.0: WM Firmware Version: 00, > Build Time: 20220929104145 > [7.492309] mt7915e :01:00.0: WA Firmware Version: DEV_00, > Build Time: 20220929104205 > [7.655412] mt7915e 0001:01:00.0: assign IRQ: got 149 > [7.660552] mt7915e 0001:01:00.0: enabling device ( -> 0002) > [7.666722] mt7915e 0001:01:00.0: enabling bus mastering > [7.783768] mtk-pcie 1a145000.pcie: msi#0 address_hi 0x0 address_lo > 0x44e150c0 > [7.803991] mt7915e 0001:01:00.0: HW/SW Version: 0x8a108a10, Build > Time: 20220929104113a > [7.803991] > [7.822350] mt7915e 0001:01:00.0: WM Firmware Version: 00, > Build Time: 20220929104145 > [7.846429] mt7915e 0001:01:00.0: WA Firmware Version: DEV_00, > Build Time: 20220929104205 > > > > # ifconfig wlan1 up > > Creating netns for phy2 on port 2302 > [ 379.207067] irq 149: nobody cared (try booting with the "irqpoll" option) > [ 379.213884] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G S > 5.15.86 #0 > [ 379.221291] Hardware name: Bananapi BPI-R64 (DT) > [ 379.225909] Call trace: > [ 379.228352] dump_backtrace+0x0/0x15c > [ 379.232035] show_stack+0x14/0x30 > [ 379.235359] dump_stack_lvl+0x64/0x7c > [ 379.239030] dump_stack+0x14/0x2c > [ 379.242351] __report_bad_irq+0x48/0x128 > [ 379.246280] note_interrupt+0x2e4/0x340 > [ 379.250124] handle_irq_event+0xb8/0xe0 > [ 379.253965] handle_simple_irq+0xb0/0x10c > [ 379.257980] generic_handle_domain_irq+0x28/0x3c > [ 379.262610] mtk_pcie_intr_handler+0x144/0x19c > [ 379.267064] handle_domain_irq+0x5c/0x8c > [ 379.270999] gic_handle_irq+0x64/0x8c > [ 379.274668] do_interrupt_handler+0x30/0x54 > [ 379.278859] el1_interrupt+0x2c/0x4c > [ 379.282446] el1h_64_irq_handler+0x14/0x20 > [ 379.286547] el1h_64_irq+0x74/0x78 > [ 379.289953] _stext+0xa0/0x294 > [ 379.293012] __irq_exit_rcu+0xdc/0xfc > [ 379.296680] irq_exit+0xc/0x1c > [ 379.299738] handle_domain_irq+0x60/0x8c > [ 379.303673] gic_handle_irq+0x64/0x8c > [ 379.307340] call_on_irq_stack+0x28/0x44 > [ 379.311269] do_interrupt_handler+0x4c/0x54 > [ 379.315460] el1_interrupt+0x2c/0x4c > [ 379.319045] el1h_64_irq_handler+0x14/0x20 > [ 379.323145] el1h_64_irq+0x74/0x78 > [ 379.326550] arch_cpu_idle+0x14/0x20 > [ 379.330131] do_idle+0xc0/0x140 > [ 379.333284] cpu_startup_entry+0x24/0x50 > [ 379.337218] rest_init+0xc4/0xd0 > [ 379.340451] arch_call_rest_init+0xc/0x14 > [ 379.344471] start_kernel+0x5b4/0x5d4 > [ 379.348144] __primary_switched+0xa0/0xa8 > [ 379.352163] handlers: > [ 379.354433] [<dd1abdd2>] pcie_pme_irq > [ 379.358808] Disabling IRQ #149 > And lspci: root@OpenWrt:~# lspci :00:00.0 PCI bridge: MEDIATEK Corp. Device 3258 :01:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E 802.11ax PCI Express Wireless Network Adapter 0001:00:01.0 PCI bridge: MEDIATEK Corp. Device 3258 0001:01:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E 802.11ax PCI Express Wireless Network Adapter root@OpenWrt:~# root@OpenWrt:~# root@OpenWrt:~# lspci -tv -+-[:00]---00.0-[01]00.0 MEDIATEK Corp. MT7915E 802.11ax PCI Express Wireless Network Adapter \-[0001:00]---01.0-[01]00.0 MEDIATEK Corp. MT7915E 802.11ax PCI Express Wireless Network Adapter root@OpenWrt:~# root@OpenWrt:~# root@OpenWrt:~# lspci -v :00:00.0 PCI bridge: MEDIATEK Corp. Device 3258 (prog-if 00 [Normal decode]) Device tree node: /sys/firmware/devicetree/base/pcie@1a143000/pcie@0,0 Flags: bus master, fast devsel, latency 0, IRQ 148 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 Memory behind bridge: 2000-201f [size=2M] [32-bit] Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Root Port (Slot+), MSI 00 Capabilities: [100] Virtual Channel Capabilities: [400] L1 PM Substates Capabilities: [600] Latency Tolerance Reporting Kernel dr
two mt7915e cards and irq 149: nobody cared dump
Hello, Have two mt7915e cards in my banana PI R64 (latest master). After do ifconfig wlan1 up - dump. While ifconfig wlan2 up works correctly. [7.093206] mt7915e :01:00.0: assign IRQ: got 148 [7.098405] mt7915e :01:00.0: enabling device ( -> 0002) [7.104537] mt7915e :01:00.0: enabling bus mastering [7.181837] mt7622-wmac 1800.wmac: N9 Firmware Version: _reserved_, Build Time: 20220630094834 [7.193914] Bluetooth: hci0: Device setup in 243529 usecs [7.233531] mtk-pcie 1a143000.pcie: msi#0 address_hi 0x0 address_lo 0x44e050c0 [7.291849] mt7915e :01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20220929104113a [7.291849] [7.435118] mt7915e :01:00.0: WM Firmware Version: 00, Build Time: 20220929104145 [7.492309] mt7915e :01:00.0: WA Firmware Version: DEV_00, Build Time: 20220929104205 [7.655412] mt7915e 0001:01:00.0: assign IRQ: got 149 [7.660552] mt7915e 0001:01:00.0: enabling device ( -> 0002) [7.666722] mt7915e 0001:01:00.0: enabling bus mastering [7.783768] mtk-pcie 1a145000.pcie: msi#0 address_hi 0x0 address_lo 0x44e150c0 [7.803991] mt7915e 0001:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20220929104113a [7.803991] [7.822350] mt7915e 0001:01:00.0: WM Firmware Version: 00, Build Time: 20220929104145 [7.846429] mt7915e 0001:01:00.0: WA Firmware Version: DEV_00, Build Time: 20220929104205 # ifconfig wlan1 up Creating netns for phy2 on port 2302 [ 379.207067] irq 149: nobody cared (try booting with the "irqpoll" option) [ 379.213884] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G S 5.15.86 #0 [ 379.221291] Hardware name: Bananapi BPI-R64 (DT) [ 379.225909] Call trace: [ 379.228352] dump_backtrace+0x0/0x15c [ 379.232035] show_stack+0x14/0x30 [ 379.235359] dump_stack_lvl+0x64/0x7c [ 379.239030] dump_stack+0x14/0x2c [ 379.242351] __report_bad_irq+0x48/0x128 [ 379.246280] note_interrupt+0x2e4/0x340 [ 379.250124] handle_irq_event+0xb8/0xe0 [ 379.253965] handle_simple_irq+0xb0/0x10c [ 379.257980] generic_handle_domain_irq+0x28/0x3c [ 379.262610] mtk_pcie_intr_handler+0x144/0x19c [ 379.267064] handle_domain_irq+0x5c/0x8c [ 379.270999] gic_handle_irq+0x64/0x8c [ 379.274668] do_interrupt_handler+0x30/0x54 [ 379.278859] el1_interrupt+0x2c/0x4c [ 379.282446] el1h_64_irq_handler+0x14/0x20 [ 379.286547] el1h_64_irq+0x74/0x78 [ 379.289953] _stext+0xa0/0x294 [ 379.293012] __irq_exit_rcu+0xdc/0xfc [ 379.296680] irq_exit+0xc/0x1c [ 379.299738] handle_domain_irq+0x60/0x8c [ 379.303673] gic_handle_irq+0x64/0x8c [ 379.307340] call_on_irq_stack+0x28/0x44 [ 379.311269] do_interrupt_handler+0x4c/0x54 [ 379.315460] el1_interrupt+0x2c/0x4c [ 379.319045] el1h_64_irq_handler+0x14/0x20 [ 379.323145] el1h_64_irq+0x74/0x78 [ 379.326550] arch_cpu_idle+0x14/0x20 [ 379.330131] do_idle+0xc0/0x140 [ 379.333284] cpu_startup_entry+0x24/0x50 [ 379.337218] rest_init+0xc4/0xd0 [ 379.340451] arch_call_rest_init+0xc/0x14 [ 379.344471] start_kernel+0x5b4/0x5d4 [ 379.348144] __primary_switched+0xa0/0xa8 [ 379.352163] handlers: [ 379.354433] [] pcie_pme_irq [ 379.358808] Disabling IRQ #149 BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Ethernet switch with linux/openwrt and DSA
czw., 22 gru 2022 o 18:26 Jan Hoffmann napisał(a): > > Hi Janusz, > > > BTW, this switch have some issues with IPv6? > > > > Simple remove lan2 from switch/bridge and configure manually - connect > > my device directly to eth2 port. > > Seems IPv4 works correctly - while IPv6 not (ping6 ff02::1%lan2 - no > > answer). > > Same config (with removed lan2 from bridge) works perfectly with > > mt7530 (also dsa) on my mt7621 board. > > I just tested this on my HPE 1920-48G, and it works. But I'm running a > build with some patches, so that may be the reason. > My fault, seems firewall was enabled and block all except lan zone. After disable firewall - see ipv6 packets. BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Ethernet switch with linux/openwrt and DSA
czw., 22 gru 2022 o 02:24 Luiz Angelo Daros de Luca napisał(a): > > > Thanks all! > > Finally buy: D-LINK DGS-1210-48 G1. > > > > U-Boot 2011.12.(2.1.5.67086)-Candidate1 (Apr 13 2017 - 13:58:11) > > > > Board: RTL839x CPU:700MHz LXB:200MHz MEM:400MHz > > DRAM: 128 MB > > SPI-F: 1x32 MB > > > > Next: > > - connected serial cable > > - stop in uboot > > - boot from > > tftp/openwrt-realtek-rtl839x-d-link_dgs-1210-52-initramfs-kernel.bin > > - next simple scp/sysupgrade > > openwrt-realtek-rtl839x-d-link_dgs-1210-52-squashfs-sysupgrade.bin > > > Great news! Interesting, is it the same model as 1210-52 but with the > extra ports as non combo? Or are SFP+ still combo ports with 45-48 > ports? Currently 49-52 they are disabled in -52 variant but they might > introduce a problem if someone gets that fixed and they are missing in > your device. Ports are statically defined in the DTS file and they > might brick the device if missing. > Ports 49-52 seems to be "shared" I have both eth and sfp ports with same numbers (btw eth ports 49-52 don't work correctly) > Did you try the image1 firmware? It should work from the web interface > but you need to write it to the image1, not image2 slot. If it is that > close to F1 series, might be able to dual boot the device back to the > original firmware. If that doesn't work, we might need to change some > flags in the dlink image generator. Is the original firmware shared > between -f1 and -g1 series? > From original GUI/SW wasn't able to change image1/image2 - only config1/config2. Because of that decide to run directly from uboout and RAM via tftp - just to check if will up correctly. But original SW show double mtds for kernel/rootfs - so maybe only GUI issue? Linux version 2.6.19 (jonathan@210Server) (gcc version 3.4.4 mipssde-6.03.00-20051020) #2 PREEMPT Fri Oct 6 14:29:30 CST 2017 CPU revision is: 00019555 Determined physical RAM map: memory: 0200 @ (usable) User-defined physical RAM map: memory: 0790 @ (usable) Built 1 zonelists. Total pages: 30734 Kernel command line: console=ttyS0,115200 mem=121M noinitrd root=/dev/mtdblock4 rw rootfstype=squashfs csb=0x0157CCD6 cso=0x0794DD64 csf=0x42662D12 sfin=,32MB,8376352;8335392 Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes. Primary data cache 32kB, 4-way, linesize 32 bytes. Synthesized TLB refill handler (20 instructions). Synthesized TLB load handler fastpath (32 instructions). Synthesized TLB store handler fastpath (32 instructions). Synthesized TLB modify handler fastpath (31 instructions). Cache parity protection disabled PID hash table entries: 512 (order: 9, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 120320k/123904k available (1786k kernel code, 3460k reserved, 393k data, 104k init, 0k highmem) Mount-cache hash table entries: 512 Checking for 'wait' instruction... available. NET: Registered protocol family 16 NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 2, 16384 bytes) TCP bind hash table entries: 2048 (order: 1, 8192 bytes) TCP: Hash tables configured (established 4096 bind 2048) TCP reno registered squashfs: version 3.3 (2007/10/31) Phillip Lougher JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 1 ports, IRQ sharing disabled serial8250: ttyS0 at MMIO 0x0 (irq = 31) is a 16550A Probe: SPI CS1 Flash Type MX25L25635F Creating 9 MTD partitions on "Total SPI FLASH": 0x-0x0008 : "BOOT" 0x0008-0x000c : "BDINFO" 0x000c-0x0010 : "BDINFO2" 0x0010-0x0028 : "KERNEL1" 0x0028-0x00e8 : "ROOTFS1" 0x00e8-0x0100 : "KERNEL2" 0x0100-0x0104 : "SYSINFO" 0x0104-0x01c4 : "ROOTFS2" 0x01c4-0x0200 : "JFFS2" TCP cubic registered > I would include a new DTS file/firmware generation, even if it only > includes/copies -52 variant. It would make the lives of newcomers much > easier. > G1 - have dedicated SW - DGS-1210-48-G1-7-00-B006.hex BTW, this switch have some issues with IPv6? Simple remove lan2 from switch/bridge and configure manually - connect my device directly to eth2 port. Seems IPv4 works correctly - while IPv6 not (ping6 ff02::1%lan2 - no answer). Same config (with removed lan2 from bridge) works perfectly with mt7530 (also dsa) on my mt7621 board. Or we miss some configuration? Some logs below: Thu Dec 22 15:05:20 2022 kern.info kernel: [98039.948092] rtl83xx-switch switch@1b00 lan2: Link is Up - 1Gbps/Full - flow control rx/tx Thu Dec 22 15:05:20 2022 kern.info kernel: [98039.957695] IPv6: ADDRCONF(NETDEV_CHANGE): lan2: link becomes ready Thu Dec 22 15:05:20 2022 daemon.notice netifd: Network
Re: Ethernet switch with linux/openwrt and DSA
śr., 14 gru 2022 o 20:35 Jan Hoffmann napisał(a):
>
> > Hi Janusz,
> >
> > > Could I just buy (any experience):
> > >
> > > HP switch 1920-24G JG924A
> > > Do I need to check any HW ver? Or any JG924A should work?
> >
> > The devices from HPE 1920 series with model numbers JG92xA are all
> > Realtek-based, and should be compatible with OpenWrt (make sure not to
> > get a device from the similarly-named 1920S-series though, as those are
> > not supported).
> >
> > Note that the HPE devices are only supported in master and support for
> > 1920-48G is not yet included.
>
> And to be clear, the models with PoE are also not supported (I forgot
> about those in the initial message).
>
> > For 1920-24G, the patches 2 and 5 from [1] are probably still necessary,
> > as the device will reset during boot otherwise. I should really send
> > updated versions of these to finally get that issue fixed.
> >
Thanks all!
Finally buy: D-LINK DGS-1210-48 G1.
U-Boot 2011.12.(2.1.5.67086)-Candidate1 (Apr 13 2017 - 13:58:11)
Board: RTL839x CPU:700MHz LXB:200MHz MEM:400MHz
DRAM: 128 MB
SPI-F: 1x32 MB
Next:
- connected serial cable
- stop in uboot
- boot from
tftp/openwrt-realtek-rtl839x-d-link_dgs-1210-52-initramfs-kernel.bin
- next simple scp/sysupgrade
openwrt-realtek-rtl839x-d-link_dgs-1210-52-squashfs-sysupgrade.bin
root@OpenWrt:~# ubus call system board
{
"kernel": "5.10.156",
"hostname": "OpenWrt",
"system": "RTL8393",
"model": "D-Link DGS-1210-52",
"board_name": "d-link,dgs-1210-52",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "SNAPSHOT",
"revision": "r21432-4c0919839d",
"target": "realtek/rtl839x",
"description": "OpenWrt SNAPSHOT r21432-4c0919839d"
}
}
root@OpenWrt:~#
BR
Janusz
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Ethernet switch with linux/openwrt and DSA
śr., 14 gru 2022 o 12:59 Janusz Dziedzic napisał(a): > > wt., 13 gru 2022 o 14:20 Daniel Golle napisał(a): > > > > On Tue, Dec 13, 2022 at 11:17:49AM +0100, Janusz Dziedzic wrote: > > > Hello, > > > > > > Do you know any/some ethernet switch project (best 18+ gbps ports) > > > that using linux/openwrt and DSA architecture? > > > > Some switches with high port density currently supported by OpenWrt: > > * TP-Link SG2452P > > * ZyXEL GS1900-48 > > * Panasonic Switch-M48eG PN28480K > > > > All of the above are using RealTek RTL839x platform. > > > > Could I just buy (any experience): > > HP switch 1920-24G JG924A > Do I need to check any HW ver? Or any JG924A should work? > Or D-Link DGS-1210-48 HW Ver. G1 - will be fine? I need some confirmation. Anyone could confirm? BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: Ethernet switch with linux/openwrt and DSA
wt., 13 gru 2022 o 14:20 Daniel Golle napisał(a): > > On Tue, Dec 13, 2022 at 11:17:49AM +0100, Janusz Dziedzic wrote: > > Hello, > > > > Do you know any/some ethernet switch project (best 18+ gbps ports) > > that using linux/openwrt and DSA architecture? > > Some switches with high port density currently supported by OpenWrt: > * TP-Link SG2452P > * ZyXEL GS1900-48 > * Panasonic Switch-M48eG PN28480K > > All of the above are using RealTek RTL839x platform. > Could I just buy (any experience): HP switch 1920-24G JG924A Do I need to check any HW ver? Or any JG924A should work? BR Janusz -- Janusz Dziedzic ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Ethernet switch with linux/openwrt and DSA
Hello, Do you know any/some ethernet switch project (best 18+ gbps ports) that using linux/openwrt and DSA architecture? BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH-22.03] netifd: bridge: add support option for untagged
pt., 9 wrz 2022 o 12:30 Andrey Jr. Melnikov napisał(a): > > Janusz Dziedzic wrote: > > [-- text/plain, encoding quoted-printable, charset: UTF-8, 86 lines --] > > > pt., 9 wrz 2022 o 04:32 LiXiong Liu napisał(a): > > > > > > ### swconfig & DSA VLAN Configuration Comparison > > [] > > > > #bridge vlan show > > > port vlan-id > > > lan1 100 PVID Egress Untagged > > > lan2 100 PVID Egress Untagged > > > lan3 1 PVID Egress Untagged > > > lan4 1 PVID Egress Untagged > > > lan5 1 PVID Egress Untagged > > > 10 > > > br-lan1 PVID Egress Untagged > > > 10 > > > > > > We are using smth like this: > > > config bridge-vlan 'vlan1' > > option name 'vlan1' > > option device 'br-lan' > > option vlan '1' > > option flags 'untagged pvid' > "untagged pvid" is tautology. PVID stands for "Port VLAN ID" - is a default > VLAN ID that is assigned to an access > port. Access ports only for untagged (stripped tag) frames. So, drop > 'untagged' > from options or 'pvid'. > What in case I would like to have smth like: br-lan1 PVID Egress Untagged 10 Egress Untagged bridge vlan <> - tool allow this configuration. Why we should add any limitation in UCI? BR Janusz > > option local '1' > > list ports 'eth2:*' > > list ports 'eth3:*' > > [...] > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Janusz Dziedzic ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH-22.03] netifd: bridge: add support option for untagged
pt., 9 wrz 2022 o 04:32 LiXiong Liu napisał(a):
>
> ### swconfig & DSA VLAN Configuration Comparison
> Doesn't just support Tunnk on lan5,
> also need access to 192.168.1.1
> so must setting untagged at br-lan
>
> #switch-vlan
> config switch
> option name 'switch0'
> option reset '1'
> option enable_vlan '1'
>
> config switch_vlan
> option device 'switch0'
> option vlan '0'
> option vid '0'
> option ports '2 3 5 6'
>
> config switch_vlan
> option device 'switch0'
> option vlan '100'
> option vid '100'
> option ports '0 1 4t'
>
>
> #bridge-vlan
> config interface 'lan'
> option device 'br-lan'
> option proto 'static'
> option ipaddr '192.168.1.1'
> option netmask '255.255.255.0'
> option ip6assign '60'
> config device
> option name 'br-lan'
> option type 'bridge'
> list ports 'lan1'
> list ports 'lan2'
> list ports 'lan3'
> list ports 'lan4'
> list ports 'lan5'
>
> config bridge-vlan
> option device 'br-lan'
> option untagged '1'
> option vlan '1'
> list ports 'lan3'
> list ports 'lan4'
> list ports 'lan5'
>
> config bridge-vlan
> option device 'br-lan'
> option vlan '100'
> list ports 'lan1:u*'
> list ports 'lan1:u*'
> list ports 'lan5:t'
>
> #bridge vlan show
> port vlan-id
> lan1 100 PVID Egress Untagged
> lan2 100 PVID Egress Untagged
> lan3 1 PVID Egress Untagged
> lan4 1 PVID Egress Untagged
> lan5 1 PVID Egress Untagged
> 10
> br-lan1 PVID Egress Untagged
> 10
>
We are using smth like this:
config bridge-vlan 'vlan1'
option name 'vlan1'
option device 'br-lan'
option vlan '1'
option flags 'untagged pvid'
option local '1'
list ports 'eth2:*'
list ports 'eth3:*'
And attached patch - not sure what is best. For sure any option to set
self br config looks good.
BR
Janusz
--- a/bridge.c
+++ b/bridge.c
@@ -233,7 +233,7 @@ bridge_set_local_vlan(struct bridge_stat
if (!vlan->local && add)
return;
- system_bridge_vlan(bst->dev.ifname, vlan->vid, add, BRVLAN_F_SELF);
+ system_bridge_vlan(bst->dev.ifname, vlan->vid, add, vlan->local_flags | BRVLAN_F_SELF);
}
static void
@@ -951,6 +951,7 @@ bridge_dump_vlan(struct blob_buf *b, str
blobmsg_add_u32(b, "id", vlan->vid);
blobmsg_add_u8(b, "local", vlan->local);
+ blobmsg_add_u32(b, "local_flags", vlan->local_flags);
p = blobmsg_open_array(b, "ports");
--- a/device.h
+++ b/device.h
@@ -293,6 +293,7 @@ struct bridge_vlan {
uint16_t vid;
bool local;
+ enum bridge_vlan_flags local_flags;
bool pending;
};
--- a/config.c
+++ b/config.c
@@ -312,6 +312,7 @@ config_parse_vlan(struct device *dev, st
enum {
BRVLAN_ATTR_VID,
BRVLAN_ATTR_LOCAL,
+ BRVLAN_ATTR_FLAGS,
BRVLAN_ATTR_PORTS,
BRVLAN_ATTR_ALIAS,
__BRVLAN_ATTR_MAX,
@@ -319,6 +320,7 @@ config_parse_vlan(struct device *dev, st
static const struct blobmsg_policy vlan_attrs[__BRVLAN_ATTR_MAX] = {
[BRVLAN_ATTR_VID] = { "vlan", BLOBMSG_TYPE_INT32 },
[BRVLAN_ATTR_LOCAL] = { "local", BLOBMSG_TYPE_BOOL },
+ [BRVLAN_ATTR_FLAGS] = { "flags", BLOBMSG_TYPE_STRING },
[BRVLAN_ATTR_PORTS] = { "ports", BLOBMSG_TYPE_ARRAY },
[BRVLAN_ATTR_ALIAS] = { "alias", BLOBMSG_TYPE_ARRAY },
};
@@ -338,6 +340,7 @@ config_parse_vlan(struct device *dev, st
unsigned int vid;
const char *val;
char *name_buf;
+ char *local_flags;
int name_len = 0;
int n_ports = 0;
int rem;
@@ -371,6 +374,15 @@ config_parse_vlan(struct device *dev, st
if (tb[BRVLAN_ATTR_LOCAL])
vlan->local = blobmsg_get_bool(tb[BRVLAN_ATTR_LOCAL]);
+ if (tb[BRVLAN_ATTR_FLAGS]) {
+ local_flags = blobmsg_get_string(tb[BRVLAN_ATTR_FLAGS]);
+
+ if (strstr(local_flags, "pvid"))
+ vlan->local_flags |= BRVLAN_F_PVID;
+ if (strstr(local_flags, "untagged"))
+ vlan->local_flags |= BRVLAN_F_UNTAGGED;
+ }
+
vlan->n_ports = n_ports;
vlan->ports = port = (struct bridge_vlan_port *)[1];
INIT_LIST_HEAD(>hotplug_ports);
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: mt7915e in mt7621 - Failed to get patch semaphore
niedz., 19 gru 2021 o 14:39 Bastian Bittorf napisał(a): > > On Sat, Dec 18, 2021 at 01:21:21PM +0100, Janusz Dziedzic wrote: > > Hello, > > > > Have mt7915e in my mt7621 router (pandora box/ramips). > > the same here with 'TP-LINK Archer C6U' (also ramips) > (but since a long time and maybe forever). > @Felix Fietkau @Lorenzo Bianconi Any idea if that could be fixed in 7915 driver? Or this is smth wrong with PCIE controller? I could add that I have same cards in: - my laptop x86_64 - banana_pi aarch64 And there is no issue - seems only rampis (32bit) affected? BR Janusz -- Janusz Dziedzic ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
mt7915e in mt7621 - Failed to get patch semaphore
Hello, Have mt7915e in my mt7621 router (pandora box/ramips). After fresh start (disconnect/connect power supply) works correctly. After reboot seems to always fail with: Sat Dec 18 08:43:58 2021 kern.info kernel: [ 14.552269] mt7621-pci 1e14.pcie: bus=3 slot=2 irq=25 Sat Dec 18 08:43:58 2021 kern.info kernel: [ 14.557823] pci :00:02.0: enabling device ( -> 0003) Sat Dec 18 08:43:58 2021 kern.info kernel: [ 14.563499] mt7915e :03:00.0: enabling device ( -> 0002) Sat Dec 18 08:43:58 2021 kern.err kernel: [ 35.094270] mt7915e :03:00.0: Message 0010 (seq 1) timeout Sat Dec 18 08:43:58 2021 kern.err kernel: [ 35.100457] mt7915e :03:00.0: Failed to get patch semaphore Sat Dec 18 08:43:58 2021 kern.err kernel: [ 55.574220] mt7915e :03:00.0: Message 0010 (seq 2) timeout Sat Dec 18 08:43:58 2021 kern.err kernel: [ 55.580380] mt7915e :03:00.0: Failed to get patch semaphore Sat Dec 18 08:43:58 2021 kern.warn kernel: [ 55.586529] mt7915e: probe of :03:00.0 failed with error -11 This is lspci output: 02:00.0 Network controller: MEDIATEK Corp. MT7612E 802.11acbgn PCI Express Wireless Network Adapter 03:00.0 Unclassified device [0002]: MEDIATEK Corp. MT7915E 802.11ax PCI Express Wireless Network Adapter Detection works correctly after disconnect/connect power supply. Any idea what could be wrong - pci controller? This is with latest master. I don't see this issue with banana-pi-r64 (arm based board). BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
banana-pi-r64 eth wan speed
Hello, I see that my board negotiate only 100mbps on wan iface. First think cable or switch issue - but using same cable and same ext switch port I get 1000 when using lanX iface. Do you see the same - or my board have some issue with WAN? Fresh master used. root@OpenWrt:~# ethtool wan Settings for wan: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: external Auto-negotiation: on Supports Wake-on: d Wake-on: d Link detected: yes root@OpenWrt:~# ethtool lan1 Settings for lan1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: external Auto-negotiation: on Supports Wake-on: d Wake-on: d Link detected: yes BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [RFC 1/3] kernel: allow to choose QCOM_QMI_HELPERS
niedz., 24 paź 2021 o 21:42 Janusz Dziedzic napisał(a): > > We need this when build ath11k from backports. > > Signed-off-by: Janusz Dziedzic > --- > .../generic/pending-5.10/930-qcom-qmi-helpers.patch | 13 + > 1 file changed, 13 insertions(+) > create mode 100644 > target/linux/generic/pending-5.10/930-qcom-qmi-helpers.patch > > diff --git a/target/linux/generic/pending-5.10/930-qcom-qmi-helpers.patch > b/target/linux/generic/pending-5.10/930-qcom-qmi-helpers.patch > new file mode 100644 > index 00..0a274334b9 > --- /dev/null > +++ b/target/linux/generic/pending-5.10/930-qcom-qmi-helpers.patch > @@ -0,0 +1,13 @@ > +diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig > +index 6a3b69b..58c7dd9 100644 > +--- a/drivers/soc/qcom/Kconfig > b/drivers/soc/qcom/Kconfig > +@@ -92,7 +92,7 @@ config QCOM_PDR_HELPERS > + select QCOM_QMI_HELPERS > + > + config QCOM_QMI_HELPERS > +- tristate > ++ tristate "Qualcomm QMI Helpers" > + depends on NET > + > + config QCOM_RMTFS_MEM > -- > 2.25.1 > Already resend original patch to linux-kernel group, but suspect we will need this one for a while -- Janusz Dziedzic ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [RFC 2/3] kernel: add kmod packages required by ath11k
niedz., 24 paź 2021 o 21:55 Robert Marko napisał(a): > > On Sun, 24 Oct 2021 at 21:43, Janusz Dziedzic > wrote: > > > > When build ath11k from backports we need enable > > such packages: > > - mhi-bus > > - qrtr > > - qrtr-mhi > > - michael-mic > > - qcom-qmi-helpers > > > > Signed-off-by: Janusz Dziedzic > > --- > > package/kernel/linux/modules/lib.mk | 14 > > package/kernel/linux/modules/mhi.mk | 21 +++ > > package/kernel/linux/modules/other.mk | 14 > > package/kernel/linux/modules/qrtr.mk | 51 +++ > > 4 files changed, 100 insertions(+) > > create mode 100644 package/kernel/linux/modules/mhi.mk > > create mode 100644 package/kernel/linux/modules/qrtr.mk > > > > diff --git a/package/kernel/linux/modules/lib.mk > > b/package/kernel/linux/modules/lib.mk > > index 9a341932bd..51a8c6a753 100644 > > --- a/package/kernel/linux/modules/lib.mk > > +++ b/package/kernel/linux/modules/lib.mk > > @@ -121,6 +121,20 @@ endef > > $(eval $(call KernelPackage,lib-lzo)) > > > > > > +define KernelPackage/lib-michael-mic > > Hi Janusz, > thanks for working on the kernel modules that ath11k depends on. > I have had ath11k packaged for a while, but didn't work on the > dependencies to be > packaged as kmods as well. > > That being said, there is an existing kmod-crypto-michael-mic package > in the crypto modules, > so no need for it. > Thanks! Seems I missed it :) BR Janusz > Regards, > Robert > > + SUBMENU:=$(LIB_MENU) > > + TITLE:=MICHAEL_MIC support > > + KCONFIG:=CONFIG_CRYPTO_MICHAEL_MIC > > + FILES:= $(LINUX_DIR)/crypto/michael_mic.ko > > + AUTOLOAD:=$(call AutoProbe,michael_mic) > > +endef > > + > > +define KernelPackage/lib-michael-mic/description > > + Kernel module for MICHAEL_MIC support > > +endef > > + > > +$(eval $(call KernelPackage,lib-michael-mic)) > > + > > define KernelPackage/lib-zstd > >SUBMENU:=$(LIB_MENU) > >TITLE:=ZSTD support > > diff --git a/package/kernel/linux/modules/mhi.mk > > b/package/kernel/linux/modules/mhi.mk > > new file mode 100644 > > index 00..a247b37efe > > --- /dev/null > > +++ b/package/kernel/linux/modules/mhi.mk > > @@ -0,0 +1,21 @@ > > +# > > +# Copyright (C) 2021 OpenWrt.org > > +# > > +# This is free software, licensed under the GNU General Public License v2. > > +# See /LICENSE for more information. > > +# > > + > > +MHI_MENU:=MHI support > > + > > +define KernelPackage/mhi-bus > > + SUBMENU:=$(MHI_MENU) > > + TITLE:=Support for Modem Host Interface (MHI) bus > > + KCONFIG:=CONFIG_MHI_BUS CONFIG_MHI_BUS_DEBUG=n > > + FILES:=$(LINUX_DIR)/drivers/bus/mhi/core/mhi.ko > > +endef > > + > > +define KernelPackage/mhi-bus/description > > + Kernel support for Modem Host Interface (MHI) > > +endef > > + > > +$(eval $(call KernelPackage,mhi-bus)) > > diff --git a/package/kernel/linux/modules/other.mk > > b/package/kernel/linux/modules/other.mk > > index fdcc089025..555a94c442 100644 > > --- a/package/kernel/linux/modules/other.mk > > +++ b/package/kernel/linux/modules/other.mk > > @@ -1256,3 +1256,17 @@ define KernelPackage/f71808e-wdt/description > > endef > > > > $(eval $(call KernelPackage,f71808e-wdt)) > > + > > +define KernelPackage/qcom-qmi-helpers > > + SUBMENU:=$(OTHER_MENU) > > + TITLE:=Qualcomm QMI helpers > > + KCONFIG:=CONFIG_QCOM_QMI_HELPERS > > + FILES:=$(LINUX_DIR)/drivers/soc/qcom/qmi_helpers.ko > > + AUTOLOAD:=$(call AutoProbe,qmi_helpers,1) > > +endef > > + > > +define KernelPackage/qcom-qmi-helpers/description > > + Kernel module qcom_qmi_helpers > > +endef > > + > > +$(eval $(call KernelPackage,qcom-qmi-helpers)) > > diff --git a/package/kernel/linux/modules/qrtr.mk > > b/package/kernel/linux/modules/qrtr.mk > > new file mode 100644 > > index 00..eea95bfd54 > > --- /dev/null > > +++ b/package/kernel/linux/modules/qrtr.mk > > @@ -0,0 +1,51 @@ > > +# > > +# Copyright (C) 2021 OpenWrt.org > > +# > > +# This is free software, licensed under the GNU General Public License v2. > > +# See /LICENSE for more information. > > +# > > + > > +QRTR_MENU:=Qualcomm IPC Router support > > + > > +define KernelPackage/qrtr > > + SUBMENU:=$(QRTR_MENU) > > + TITLE:=Qualcomm IPC Router support > > + KCONFIG:=CONFIG_QRTR > > + FILES:
Re: [RFC 3/3] mac80211: allow to choose ath11k driver
niedz., 24 paź 2021 o 22:04 Robert Marko napisał(a): > > On Sun, 24 Oct 2021 at 21:43, Janusz Dziedzic > wrote: > > > > Signed-off-by: Janusz Dziedzic > > --- > > package/kernel/mac80211/ath.mk | 26 -- > > 1 file changed, 24 insertions(+), 2 deletions(-) > > > > diff --git a/package/kernel/mac80211/ath.mk b/package/kernel/mac80211/ath.mk > > index ba03ae11a6..634fb13195 100644 > > --- a/package/kernel/mac80211/ath.mk > > +++ b/package/kernel/mac80211/ath.mk > > @@ -1,6 +1,6 @@ > > PKG_DRIVERS += \ > > ath ath5k ath6kl ath6kl-sdio ath6kl-usb ath9k ath9k-common > > ath9k-htc ath10k \ > > - carl9170 owl-loader ar5523 wil6210 > > + ath11k carl9170 owl-loader ar5523 wil6210 > > > > PKG_CONFIG_DEPENDS += \ > > CONFIG_PACKAGE_ATH_DEBUG \ > > @@ -19,6 +19,7 @@ ifdef CONFIG_PACKAGE_MAC80211_DEBUGFS > > ATH9K_DEBUGFS \ > > ATH9K_HTC_DEBUGFS \ > > ATH10K_DEBUGFS \ > > + ATH11K_DEBUGFS \ > > CARL9170_DEBUGFS \ > > ATH5K_DEBUG \ > > ATH6KL_DEBUG \ > > @@ -27,6 +28,7 @@ endif > > > > ifdef CONFIG_PACKAGE_MAC80211_TRACING > >config-y += \ > > + ATH11K_TRACING \ > > ATH10K_TRACING \ > > ATH6KL_TRACING \ > > ATH_TRACEPOINTS \ > > @@ -35,7 +37,7 @@ ifdef CONFIG_PACKAGE_MAC80211_TRACING > > endif > > > > config-$(call config_package,ath) += ATH_CARDS ATH_COMMON > > -config-$(CONFIG_PACKAGE_ATH_DEBUG) += ATH_DEBUG ATH10K_DEBUG > > ATH9K_STATION_STATISTICS > > +config-$(CONFIG_PACKAGE_ATH_DEBUG) += ATH_DEBUG ATH10K_DEBUG ATH11K_DEBUG > > ATH9K_STATION_STATISTICS > > config-$(CONFIG_PACKAGE_ATH_DFS) += ATH9K_DFS_CERTIFIED > > ATH10K_DFS_CERTIFIED > > config-$(CONFIG_PACKAGE_ATH_SPECTRAL) += ATH9K_COMMON_SPECTRAL > > ATH10K_SPECTRAL > > Hi Janusz, > > thanks for working on this, I have had ath11k packaged for a while due > to IPQ807x but didn't want to send the patches > until 5.15 backports landed. > > That being said, ath11k has spectral support as well. > > config-$(CONFIG_PACKAGE_ATH_DYNACK) += ATH9K_DYNACK > > @@ -55,6 +57,7 @@ config-$(CONFIG_ATH10K_THERMAL) += ATH10K_THERMAL > > > > config-$(call config_package,ath9k-htc) += ATH9K_HTC > > config-$(call config_package,ath10k) += ATH10K ATH10K_PCI > > +config-$(call config_package,ath11k) += ATH11K ATH11K_PCI > > > > config-$(call config_package,ath5k) += ATH5K > > ifdef CONFIG_TARGET_ath25 > > @@ -281,6 +284,25 @@ define KernelPackage/ath10k/config > > > > endef > > > > +define KernelPackage/ath11k > > + $(call KernelPackage/mac80211/Default) > > + TITLE:=Qualcomm 802.11ax wireless chipset support > > + URL:=https://wireless.wiki.kernel.org/en/users/drivers/ath11k > > + DEPENDS+= \ > > + @PCI_SUPPORT +kmod-mac80211 +kmod-ath +@DRIVER_11N_SUPPORT > > +@DRIVER_11AC_SUPPORT \ > > + +@DRIVER_11AX_SUPPORT +kmod-hwmon-core +kmod-thermal > > +kmod-crypto-michael-mic \ > HWMON and thermal are optional things that is not included in every > target, so this needs to be a selectable thing > and needs to pull in both hwmon and thermal kmods if selected. Seems ath11k driver base here on ath11k-$(CONFIG_THERMAL) += thermal.o So, probably you should add ATH11K_CONFIG_THERMAL and send to linux-wireless ... > > + +kmod-qrtr-mhi +kmod-qcom-qmi-helpers > > + FILES:= \ > > + $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath11k/ath11k.ko \ > > + $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath11k/ath11k_pci.ko > > I am not really a fan of this approach as it always bundles PCI support. > I have it packaged as 3 packaged, ath11k core, AHB and PCI so you can > pick and choose what do you need. > > > + AUTOLOAD:=$(call AutoProbe,ath11k_pci) > This would work for AHB based stuff. > I only have PCI version and really need smth that will at least build after will check kmod-ath11k. Don't see any problem to fix it later - similar like we have in ath10k - should be easy to do. > So, would you be interested in combining your MHI/QRTR kmod and QMI > selectable patches with my ath11k packaging patches? > I see it as a way to reduce effort on both sides and get this added. > Now I think will focus on adding this series, while my platform don't support 32 MSI vectors (not sure why we don't have them in 5.15): Carl Huang (6): ath11k: get msi_data again after request_irq is called ath11k: add ce and ext irq flag to indicate irq_handler ath11k: use ATH11K_PCI_IRQ_DP_OFFSET for dp irqx
[RFC 1/3] kernel: allow to choose QCOM_QMI_HELPERS
We need this when build ath11k from backports. Signed-off-by: Janusz Dziedzic --- .../generic/pending-5.10/930-qcom-qmi-helpers.patch | 13 + 1 file changed, 13 insertions(+) create mode 100644 target/linux/generic/pending-5.10/930-qcom-qmi-helpers.patch diff --git a/target/linux/generic/pending-5.10/930-qcom-qmi-helpers.patch b/target/linux/generic/pending-5.10/930-qcom-qmi-helpers.patch new file mode 100644 index 00..0a274334b9 --- /dev/null +++ b/target/linux/generic/pending-5.10/930-qcom-qmi-helpers.patch @@ -0,0 +1,13 @@ +diff --git a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig +index 6a3b69b..58c7dd9 100644 +--- a/drivers/soc/qcom/Kconfig b/drivers/soc/qcom/Kconfig +@@ -92,7 +92,7 @@ config QCOM_PDR_HELPERS + select QCOM_QMI_HELPERS + + config QCOM_QMI_HELPERS +- tristate ++ tristate "Qualcomm QMI Helpers" + depends on NET + + config QCOM_RMTFS_MEM -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[RFC 3/3] mac80211: allow to choose ath11k driver
Signed-off-by: Janusz Dziedzic --- package/kernel/mac80211/ath.mk | 26 -- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/package/kernel/mac80211/ath.mk b/package/kernel/mac80211/ath.mk index ba03ae11a6..634fb13195 100644 --- a/package/kernel/mac80211/ath.mk +++ b/package/kernel/mac80211/ath.mk @@ -1,6 +1,6 @@ PKG_DRIVERS += \ ath ath5k ath6kl ath6kl-sdio ath6kl-usb ath9k ath9k-common ath9k-htc ath10k \ - carl9170 owl-loader ar5523 wil6210 + ath11k carl9170 owl-loader ar5523 wil6210 PKG_CONFIG_DEPENDS += \ CONFIG_PACKAGE_ATH_DEBUG \ @@ -19,6 +19,7 @@ ifdef CONFIG_PACKAGE_MAC80211_DEBUGFS ATH9K_DEBUGFS \ ATH9K_HTC_DEBUGFS \ ATH10K_DEBUGFS \ + ATH11K_DEBUGFS \ CARL9170_DEBUGFS \ ATH5K_DEBUG \ ATH6KL_DEBUG \ @@ -27,6 +28,7 @@ endif ifdef CONFIG_PACKAGE_MAC80211_TRACING config-y += \ + ATH11K_TRACING \ ATH10K_TRACING \ ATH6KL_TRACING \ ATH_TRACEPOINTS \ @@ -35,7 +37,7 @@ ifdef CONFIG_PACKAGE_MAC80211_TRACING endif config-$(call config_package,ath) += ATH_CARDS ATH_COMMON -config-$(CONFIG_PACKAGE_ATH_DEBUG) += ATH_DEBUG ATH10K_DEBUG ATH9K_STATION_STATISTICS +config-$(CONFIG_PACKAGE_ATH_DEBUG) += ATH_DEBUG ATH10K_DEBUG ATH11K_DEBUG ATH9K_STATION_STATISTICS config-$(CONFIG_PACKAGE_ATH_DFS) += ATH9K_DFS_CERTIFIED ATH10K_DFS_CERTIFIED config-$(CONFIG_PACKAGE_ATH_SPECTRAL) += ATH9K_COMMON_SPECTRAL ATH10K_SPECTRAL config-$(CONFIG_PACKAGE_ATH_DYNACK) += ATH9K_DYNACK @@ -55,6 +57,7 @@ config-$(CONFIG_ATH10K_THERMAL) += ATH10K_THERMAL config-$(call config_package,ath9k-htc) += ATH9K_HTC config-$(call config_package,ath10k) += ATH10K ATH10K_PCI +config-$(call config_package,ath11k) += ATH11K ATH11K_PCI config-$(call config_package,ath5k) += ATH5K ifdef CONFIG_TARGET_ath25 @@ -281,6 +284,25 @@ define KernelPackage/ath10k/config endef +define KernelPackage/ath11k + $(call KernelPackage/mac80211/Default) + TITLE:=Qualcomm 802.11ax wireless chipset support + URL:=https://wireless.wiki.kernel.org/en/users/drivers/ath11k + DEPENDS+= \ + @PCI_SUPPORT +kmod-mac80211 +kmod-ath +@DRIVER_11N_SUPPORT +@DRIVER_11AC_SUPPORT \ + +@DRIVER_11AX_SUPPORT +kmod-hwmon-core +kmod-thermal +kmod-crypto-michael-mic \ + +kmod-qrtr-mhi +kmod-qcom-qmi-helpers + FILES:= \ + $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath11k/ath11k.ko \ + $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath11k/ath11k_pci.ko + AUTOLOAD:=$(call AutoProbe,ath11k_pci) +endef + +define KernelPackage/ath11k/description +This module adds support for Qualcomm Technologies 802.11ax family of +chipsets. +endef + define KernelPackage/carl9170 $(call KernelPackage/mac80211/Default) TITLE:=Driver for Atheros AR9170 USB sticks -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[RFC 2/3] kernel: add kmod packages required by ath11k
When build ath11k from backports we need enable such packages: - mhi-bus - qrtr - qrtr-mhi - michael-mic - qcom-qmi-helpers Signed-off-by: Janusz Dziedzic --- package/kernel/linux/modules/lib.mk | 14 package/kernel/linux/modules/mhi.mk | 21 +++ package/kernel/linux/modules/other.mk | 14 package/kernel/linux/modules/qrtr.mk | 51 +++ 4 files changed, 100 insertions(+) create mode 100644 package/kernel/linux/modules/mhi.mk create mode 100644 package/kernel/linux/modules/qrtr.mk diff --git a/package/kernel/linux/modules/lib.mk b/package/kernel/linux/modules/lib.mk index 9a341932bd..51a8c6a753 100644 --- a/package/kernel/linux/modules/lib.mk +++ b/package/kernel/linux/modules/lib.mk @@ -121,6 +121,20 @@ endef $(eval $(call KernelPackage,lib-lzo)) +define KernelPackage/lib-michael-mic + SUBMENU:=$(LIB_MENU) + TITLE:=MICHAEL_MIC support + KCONFIG:=CONFIG_CRYPTO_MICHAEL_MIC + FILES:= $(LINUX_DIR)/crypto/michael_mic.ko + AUTOLOAD:=$(call AutoProbe,michael_mic) +endef + +define KernelPackage/lib-michael-mic/description + Kernel module for MICHAEL_MIC support +endef + +$(eval $(call KernelPackage,lib-michael-mic)) + define KernelPackage/lib-zstd SUBMENU:=$(LIB_MENU) TITLE:=ZSTD support diff --git a/package/kernel/linux/modules/mhi.mk b/package/kernel/linux/modules/mhi.mk new file mode 100644 index 00..a247b37efe --- /dev/null +++ b/package/kernel/linux/modules/mhi.mk @@ -0,0 +1,21 @@ +# +# Copyright (C) 2021 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +MHI_MENU:=MHI support + +define KernelPackage/mhi-bus + SUBMENU:=$(MHI_MENU) + TITLE:=Support for Modem Host Interface (MHI) bus + KCONFIG:=CONFIG_MHI_BUS CONFIG_MHI_BUS_DEBUG=n + FILES:=$(LINUX_DIR)/drivers/bus/mhi/core/mhi.ko +endef + +define KernelPackage/mhi-bus/description + Kernel support for Modem Host Interface (MHI) +endef + +$(eval $(call KernelPackage,mhi-bus)) diff --git a/package/kernel/linux/modules/other.mk b/package/kernel/linux/modules/other.mk index fdcc089025..555a94c442 100644 --- a/package/kernel/linux/modules/other.mk +++ b/package/kernel/linux/modules/other.mk @@ -1256,3 +1256,17 @@ define KernelPackage/f71808e-wdt/description endef $(eval $(call KernelPackage,f71808e-wdt)) + +define KernelPackage/qcom-qmi-helpers + SUBMENU:=$(OTHER_MENU) + TITLE:=Qualcomm QMI helpers + KCONFIG:=CONFIG_QCOM_QMI_HELPERS + FILES:=$(LINUX_DIR)/drivers/soc/qcom/qmi_helpers.ko + AUTOLOAD:=$(call AutoProbe,qmi_helpers,1) +endef + +define KernelPackage/qcom-qmi-helpers/description + Kernel module qcom_qmi_helpers +endef + +$(eval $(call KernelPackage,qcom-qmi-helpers)) diff --git a/package/kernel/linux/modules/qrtr.mk b/package/kernel/linux/modules/qrtr.mk new file mode 100644 index 00..eea95bfd54 --- /dev/null +++ b/package/kernel/linux/modules/qrtr.mk @@ -0,0 +1,51 @@ +# +# Copyright (C) 2021 OpenWrt.org +# +# This is free software, licensed under the GNU General Public License v2. +# See /LICENSE for more information. +# + +QRTR_MENU:=Qualcomm IPC Router support + +define KernelPackage/qrtr + SUBMENU:=$(QRTR_MENU) + TITLE:=Qualcomm IPC Router support + KCONFIG:=CONFIG_QRTR + FILES:= \ + $(LINUX_DIR)/net/qrtr/qrtr.ko \ + $(LINUX_DIR)/net/qrtr/ns.ko +endef + +define KernelPackage/qrtr/description + Kernel support for Qualcomm IPC Router +endef + +$(eval $(call KernelPackage,qrtr)) + +define KernelPackage/qrtr-mhi + SUBMENU:=$(QRTR_MENU) + TITLE:=MHI IPC Router channels + KCONFIG:=CONFIG_QRTR_MHI + DEPENDS:=+kmod-mhi-bus +kmod-qrtr + FILES:= $(LINUX_DIR)/net/qrtr/qrtr-mhi.ko +endef + +define KernelPackage/qrtr-mhi/description + Kernel support for MHI IPC Router channels +endef + +$(eval $(call KernelPackage,qrtr-mhi)) + +define KernelPackage/qrtr-tun + SUBMENU:=$(QRTR_MENU) + TITLE:=TUN device for Qualcomm IPC Router + KCONFIG:=CONFIG_QRTR_TUN + DEPENDS:=+kmod-qrtr + FILES:= $(LINUX_DIR)/net/qrtr/qrtr-tun.ko +endef + +define KernelPackage/qrtr-tun/description + Kernel support for TUN device for Qualcomm IPC Router +endef + +$(eval $(call KernelPackage,qrtr-tun)) -- 2.25.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: ath11k - pci - backports/.config issue
czw., 21 paź 2021 o 23:00 Robert Marko napisał(a): > > On Thu, 21 Oct 2021 at 22:54, Hauke Mehrtens wrote: > > > > On 10/21/21 6:52 PM, Robert Marko wrote: > > > On Thu, 21 Oct 2021 at 18:30, Janusz Dziedzic > > > wrote: > > >> > > >> czw., 21 paź 2021 o 17:54 Robert Marko napisał(a): > > >>> > > >>> For PCI/USB bus level support there are per target feature flags that > > >>> are set and then you can check if those are set so that you cant even > > >>> select usb wlan driver if the target doesnt even have usb support > > >>> enabled. > > >>> > > >> OK I see. Seems I can select all required kernel parts except: > > >> QCOM_QMI_HELPERS - which is slected when ath11k/mac80211 - and we get > > >> this from backports :) > > >> > > >> ATH11K [=n] && NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_ATH [=y] && > > >> MAC80211 [=n] && HAS_DMA [=y] && CRYPTO_MICHAEL_MIC [=y] > > >> > > >> Seems kernel patch required to choose it manaully. > > > > > > Yes, I had to add text to the tristate as otherwise its hidden. > > > > > > Regards, > > > Robert > > > > You can create kmod packages for the kernel modules build by MHI_BUS, > > QRTR, QCOM_QMI_HELPERS and whatever you need. Then the ath11k package in > > OpenWrt selects them and it should build on all targets. > > Yeah, that is my plan to package it in a target agnostic way. > Just lacking the time to do it. > > > > We already added a title text to other configuration symbols, see > > target/linux/generic/hack-5.10/251-kconfig.patch > > > > The hard part is known which patches to backport in addition. ;-) > > I have identified a couple that are must have, but I am sure more will pop up. > Finally added all packages to kernel and build correctly. Also load correctly: [ 162.361441] ath11k_pci :01:00.0: assign IRQ: got 0 [ 162.366922] ath11k_pci :01:00.0: BAR 0: assigned [mem 0x2000-0x20ff 64bit] [ 162.380001] ath11k_pci :01:00.0: enabling device ( -> 0002) [ 162.386358] ath11k_pci :01:00.0: enabling bus mastering [ 162.392043] ath11k_pci :01:00.0: failed to get 32 MSI vectors, only -28 available [ 162.399927] ath11k_pci :01:00.0: failed to enable msi: -28 [ 162.405778] ath11k_pci :01:00.0: disabling bus mastering [ 162.411481] ath11k_pci: probe of :01:00.0 failed with error -28 Seems other ath11k patch will be required, while MSI failed to get 32 vectors > Regards, > Robert > > > > Hauke -- Janusz Dziedzic ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: ath11k - pci - backports/.config issue
czw., 21 paź 2021 o 17:54 Robert Marko napisał(a): > > For PCI/USB bus level support there are per target feature flags that are set > and then you can check if those are set so that you cant even select usb wlan > driver if the target doesnt even have usb support enabled. > OK I see. Seems I can select all required kernel parts except: QCOM_QMI_HELPERS - which is slected when ath11k/mac80211 - and we get this from backports :) ATH11K [=n] && NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_ATH [=y] && MAC80211 [=n] && HAS_DMA [=y] && CRYPTO_MICHAEL_MIC [=y] Seems kernel patch required to choose it manaully. Thanks for help. BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: ath11k - pci - backports/.config issue
czw., 21 paź 2021 o 16:54 Robert Marko napisał(a): > > On Thu, 21 Oct 2021 at 16:53, Janusz Dziedzic > wrote: > > > > czw., 21 paź 2021 o 16:43 Robert Marko napisał(a): > > > > > > On Thu, 21 Oct 2021 at 16:40, Janusz Dziedzic > > > wrote: > > > > > > > > Hello, > > > > > > > > Hit some issue with my ath11k card, so maybe someone already fix > > > > it/know what I missed? > > > > > > > > My card (pcie): > > > > root@OpenWrt:~# lspci > > > > :00:00.0 PCI bridge: MEDIATEK Corp. Device 3258 > > > > :01:00.0 Unassigned class [ff00]: Qualcomm QCA6390 Wireless > > > > Network Adapter [AX500-DBS (2x2)] > > > > > > > > I have this card in my banana-pi-r64 board in pcie slot. > > > > > > > > Checked with current/latest backports (v5.10/v5.15) > > > > On top added patch (added some changes, attached) based on: > > > > https://git.openwrt.org/?p=openwrt/staging/hauke.git;a=commit;h=0b115adb1b0cc9c19c7c780f3a9e6437fa0398a5 > > > > Simple choose kmod-ath11k from menuconfig. > > > > > > > > Check it little bit (Makefile) and after: > > > > $(SH_FUNC) var2file "$(call shvar,mac80211_config)" > > > > $(PKG_BUILD_DIR)/.config > > > > Have correct backports/.config (ATH11K included) > > > > And next we call: > > > > $(MAKE) $(MAKE_OPTS) allnoconfig > > > > After this step we remove ATH11K option(s) from backports/.config > > > > > > > > Any idea, did I miss something? > > > > > > Your kernel must also have MHI and QRTR enabled, but it wont work with > > > the 5.10 QRTR > > > directly, you need to backport support for it starting the MHI interface. > > > > > > You can find those patches and some other clues in my WIP branch: > > > https://github.com/robimarko/openwrt/tree/IPQ807x-5.10-backports > > > > > OK, so this is removed from .config because of this? > > depends on MHI_BUS > > depends on QRTR > > depends on QRTR_MHI > > Yes as backports cannot just select stuff like the in-tree driver can. > Sounds good, But we also have smth like this in backports: depends on PCI/USB I suspect we don't have pci/usb drivers in backports also (using 'current' kernel for that) - and works somehow - do we hack it? BR Janusz -- Janusz Dziedzic ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: ath11k - pci - backports/.config issue
czw., 21 paź 2021 o 16:43 Robert Marko napisał(a): > > On Thu, 21 Oct 2021 at 16:40, Janusz Dziedzic > wrote: > > > > Hello, > > > > Hit some issue with my ath11k card, so maybe someone already fix > > it/know what I missed? > > > > My card (pcie): > > root@OpenWrt:~# lspci > > :00:00.0 PCI bridge: MEDIATEK Corp. Device 3258 > > :01:00.0 Unassigned class [ff00]: Qualcomm QCA6390 Wireless > > Network Adapter [AX500-DBS (2x2)] > > > > I have this card in my banana-pi-r64 board in pcie slot. > > > > Checked with current/latest backports (v5.10/v5.15) > > On top added patch (added some changes, attached) based on: > > https://git.openwrt.org/?p=openwrt/staging/hauke.git;a=commit;h=0b115adb1b0cc9c19c7c780f3a9e6437fa0398a5 > > Simple choose kmod-ath11k from menuconfig. > > > > Check it little bit (Makefile) and after: > > $(SH_FUNC) var2file "$(call shvar,mac80211_config)" $(PKG_BUILD_DIR)/.config > > Have correct backports/.config (ATH11K included) > > And next we call: > > $(MAKE) $(MAKE_OPTS) allnoconfig > > After this step we remove ATH11K option(s) from backports/.config > > > > Any idea, did I miss something? > > Your kernel must also have MHI and QRTR enabled, but it wont work with > the 5.10 QRTR > directly, you need to backport support for it starting the MHI interface. > > You can find those patches and some other clues in my WIP branch: > https://github.com/robimarko/openwrt/tree/IPQ807x-5.10-backports > OK, so this is removed from .config because of this? depends on MHI_BUS depends on QRTR depends on QRTR_MHI BR Janusz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
ath11k - pci - backports/.config issue
Hello, Hit some issue with my ath11k card, so maybe someone already fix it/know what I missed? My card (pcie): root@OpenWrt:~# lspci :00:00.0 PCI bridge: MEDIATEK Corp. Device 3258 :01:00.0 Unassigned class [ff00]: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] I have this card in my banana-pi-r64 board in pcie slot. Checked with current/latest backports (v5.10/v5.15) On top added patch (added some changes, attached) based on: https://git.openwrt.org/?p=openwrt/staging/hauke.git;a=commit;h=0b115adb1b0cc9c19c7c780f3a9e6437fa0398a5 Simple choose kmod-ath11k from menuconfig. Check it little bit (Makefile) and after: $(SH_FUNC) var2file "$(call shvar,mac80211_config)" $(PKG_BUILD_DIR)/.config Have correct backports/.config (ATH11K included) And next we call: $(MAKE) $(MAKE_OPTS) allnoconfig After this step we remove ATH11K option(s) from backports/.config Any idea, did I miss something? BR Janusz diff --git a/package/kernel/mac80211/ath.mk b/package/kernel/mac80211/ath.mk index ba03ae11a6..e0b8f4a4fb 100644 --- a/package/kernel/mac80211/ath.mk +++ b/package/kernel/mac80211/ath.mk @@ -1,5 +1,5 @@ PKG_DRIVERS += \ - ath ath5k ath6kl ath6kl-sdio ath6kl-usb ath9k ath9k-common ath9k-htc ath10k \ + ath ath5k ath6kl ath6kl-sdio ath6kl-usb ath9k ath9k-common ath9k-htc ath10k ath11k \ carl9170 owl-loader ar5523 wil6210 PKG_CONFIG_DEPENDS += \ @@ -19,6 +19,7 @@ ifdef CONFIG_PACKAGE_MAC80211_DEBUGFS ATH9K_DEBUGFS \ ATH9K_HTC_DEBUGFS \ ATH10K_DEBUGFS \ + ATH11K_DEBUGFS \ CARL9170_DEBUGFS \ ATH5K_DEBUG \ ATH6KL_DEBUG \ @@ -27,7 +28,9 @@ endif ifdef CONFIG_PACKAGE_MAC80211_TRACING config-y += \ + ATH11K_TRACING \ ATH10K_TRACING \ + ATH11K_TRACING \ ATH6KL_TRACING \ ATH_TRACEPOINTS \ ATH5K_TRACER \ @@ -35,7 +38,7 @@ ifdef CONFIG_PACKAGE_MAC80211_TRACING endif config-$(call config_package,ath) += ATH_CARDS ATH_COMMON -config-$(CONFIG_PACKAGE_ATH_DEBUG) += ATH_DEBUG ATH10K_DEBUG ATH9K_STATION_STATISTICS +config-$(CONFIG_PACKAGE_ATH_DEBUG) += ATH_DEBUG ATH10K_DEBUG ATH11K_DEBUG ATH9K_STATION_STATISTICS config-$(CONFIG_PACKAGE_ATH_DFS) += ATH9K_DFS_CERTIFIED ATH10K_DFS_CERTIFIED config-$(CONFIG_PACKAGE_ATH_SPECTRAL) += ATH9K_COMMON_SPECTRAL ATH10K_SPECTRAL config-$(CONFIG_PACKAGE_ATH_DYNACK) += ATH9K_DYNACK @@ -55,6 +58,7 @@ config-$(CONFIG_ATH10K_THERMAL) += ATH10K_THERMAL config-$(call config_package,ath9k-htc) += ATH9K_HTC config-$(call config_package,ath10k) += ATH10K ATH10K_PCI +config-$(call config_package,ath11k) += ATH11K ATH11K_PCI config-$(call config_package,ath5k) += ATH5K ifdef CONFIG_TARGET_ath25 @@ -281,6 +285,22 @@ define KernelPackage/ath10k/config endef +define KernelPackage/ath11k + $(call KernelPackage/mac80211/Default) + TITLE:=Qualcomm 802.11ax wireless chipset support + URL:=https://wireless.wiki.kernel.org/en/users/drivers/ath11k + DEPENDS+= @PCI_SUPPORT +kmod-ath +@DRIVER_11N_SUPPORT +@DRIVER_11AC_SUPPORT + FILES:= \ + $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath11k/ath11k.ko \ + $(PKG_BUILD_DIR)/drivers/net/wireless/ath/ath11k/ath11k_pci.ko + AUTOLOAD:=$(call AutoProbe,ath11k) +endef + +define KernelPackage/ath11k/description +This module adds support for Qualcomm Technologies 802.11ax family of +chipsets. +endef + define KernelPackage/carl9170 $(call KernelPackage/mac80211/Default) TITLE:=Driver for Atheros AR9170 USB sticks ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [RFC PATCH 0/6] mac80211: Update to version 5.15-rc6
de 100644 > package/kernel/mac80211/patches/subsys/372-mac80211-set-sk_pacing_shift-for-802.3-txpath.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/373-mac80211-support-Rx-timestamp-calculation-for-all-pr.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/374-mac80211-move-A-MPDU-session-check-from-minstrel_ht-.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/375-mac80211-call-ieee80211_tx_h_rate_ctrl-when-dequeue.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/376-mac80211-add-rate-control-support-for-encap-offload.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/377-mac80211-minstrel_ht-fix-sample-time-check.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/379-mac80211-fix-starting-aggregation-sessions-on-mesh-i.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/380-mac80211-introduce-aql_enable-node-in-debugfs.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/381-mac80211-rearrange-struct-txq_info-for-fewer-holes.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/382-mac80211-Switch-to-a-virtual-time-based-airtime-sche.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/384-nl80211-add-common-API-to-configure-SAR-power-limita.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/385-mac80211-add-ieee80211_set_sar_specs.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/386-mac80211-check-per-vif-offload_flags-in-Tx-path.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/387-nl80211-add-support-for-BSS-coloring.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/388-mac80211-add-support-for-BSS-color-change.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/389-ieee80211-add-TWT-element-definitions.patch > delete mode 100644 > package/kernel/mac80211/patches/subsys/390-mac80211-introduce-individual-TWT-support-in-AP-mode.patch > create mode 100644 > package/kernel/mt76/patches/001-wireless-align-some-HE-capabilities-with-the-spec.patch > create mode 100644 > package/kernel/mt76/patches/002-wireless-align-HE-capabilities-A-MPDU-Length-Exponen.patch > create mode 100644 > package/kernel/mt76/patches/003-wireless-fix-spelling-of-A-MSDU-in-HE-capabilities.patch > > -- > 2.30.2 > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel -- Janusz Dziedzic ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [packages] add sysprof tool
Add sysprof - preformance profiler for Linux - to the development tools. Patches for mips/arm are from openembedded code. sysprof-cli outfile get required events/stack frames. Next outfile can be loaded/displayed on PC using sysprof. Tool using: - PERF events - /proc/kallsyms for kernel symbols You should compile kernel with profiling enabled, debug information, symbol table information. Signed-off-by: Janusz Dziedzic janusz.dzied...@tieto.com --- Code is from http://sysprof.com patches from openembedded devel/sysprof/Makefile | 44 devel/sysprof/patches/define-NT_GNU_BUILD_ID.patch | 22 ++ devel/sysprof/patches/rmb-arm.patch| 21 ++ devel/sysprof/patches/rmb-mips.patch | 22 ++ 4 files changed, 109 insertions(+) create mode 100644 devel/sysprof/Makefile create mode 100644 devel/sysprof/patches/define-NT_GNU_BUILD_ID.patch create mode 100644 devel/sysprof/patches/rmb-arm.patch create mode 100644 devel/sysprof/patches/rmb-mips.patch diff --git a/devel/sysprof/Makefile b/devel/sysprof/Makefile new file mode 100644 index 000..9242cf4 --- /dev/null +++ b/devel/sysprof/Makefile @@ -0,0 +1,44 @@ +# +# Copyright (C) 2009-2013 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:=sysprof +PKG_VERSION:=1.2.0 +PKG_RELEASE:=1 + +PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz +PKG_SOURCE_URL:=http://sysprof.com +PKG_MD5SUM:=a81808d847732f8dafb59d26ec2eebbf + +PKG_BUILD_DEPENDS:= glib2 +PKG_FIXUP:=autoreconf +PKG_INSTALL:=1 +PKG_BUILD_PARALLEL:=1 + +include $(INCLUDE_DIR)/package.mk +include $(INCLUDE_DIR)/kernel.mk + +define Package/sysprof + SECTION:=devel + CATEGORY:=Development + TITLE:=Sysprof System Profiler + URL:=http://sysprof.com + DEPENDS:=+glib2 +endef + + +define Package/sysprof/description + Sysprof is a statistical, system-wide profiler for Linux +endef + +define Package/sysprof/install + $(INSTALL_DIR) $(1)/usr/bin + $(INSTALL_BIN) $(PKG_INSTALL_DIR)/usr/bin/sysprof-cli $(1)/usr/bin/ +endef + +$(eval $(call BuildPackage,sysprof)) diff --git a/devel/sysprof/patches/define-NT_GNU_BUILD_ID.patch b/devel/sysprof/patches/define-NT_GNU_BUILD_ID.patch new file mode 100644 index 000..dcc2cbe --- /dev/null +++ b/devel/sysprof/patches/define-NT_GNU_BUILD_ID.patch @@ -0,0 +1,22 @@ +On uclibc elf.h does not have GNU extentions but we need this define +so we define it locally if its not getting it from elf.h + +Signed-off-by: Khem Raj raj.k...@gmail.com + +Upstream-Status: Pending + +Index: git/elfparser.h +=== +--- git.orig/elfparser.h 2011-07-16 18:57:41.0 -0700 git/elfparser.h2011-07-16 20:28:54.733829895 -0700 +@@ -17,6 +17,10 @@ + */ + #include glib.h + ++#ifndef NT_GNU_BUILD_ID ++#define NT_GNU_BUILD_ID 3 ++#endif ++ + typedef struct ElfSym ElfSym; + typedef struct ElfParser ElfParser; + diff --git a/devel/sysprof/patches/rmb-arm.patch b/devel/sysprof/patches/rmb-arm.patch new file mode 100644 index 000..a440348 --- /dev/null +++ b/devel/sysprof/patches/rmb-arm.patch @@ -0,0 +1,21 @@ + +Upstream-Status: Pending + +Index: git/util.h +=== +--- git.orig/util.h2010-12-07 22:41:57.156243001 -0600 git/util.h 2010-12-07 22:43:47.616243002 -0600 +@@ -37,4 +37,13 @@ + #define cpu_relax() asm volatile( ::: memory); + #endif + ++#ifdef __arm__ ++/* ++ * Use the __kuser_memory_barrier helper in the CPU helper page. See ++ * arch/arm/kernel/entry-armv.S in the kernel source for details. ++ */ ++#define rmb() ((void(*)(void))0x0fa0)() ++#define cpu_relax() asm volatile(:::memory) ++#endif ++ + #endif diff --git a/devel/sysprof/patches/rmb-mips.patch b/devel/sysprof/patches/rmb-mips.patch new file mode 100644 index 000..e055b8a --- /dev/null +++ b/devel/sysprof/patches/rmb-mips.patch @@ -0,0 +1,22 @@ +Upstream-Status: Pending + +Index: git/util.h +=== +--- git.orig/util.h2010-12-08 01:22:44.486243001 -0600 git/util.h 2010-12-08 01:23:27.836243001 -0600 +@@ -37,4 +37,15 @@ + #define cpu_relax() asm volatile( ::: memory); + #endif + ++#ifdef __mips__ ++#define rmb() asm volatile( \ ++ .set mips2\n\t \ ++ sync\n\t \ ++ .set mips0 \ ++ : /* no output */ \ ++ : /* no input */\ ++ : memory) ++#define cpu_relax() asm volatile( ::: memory) ++#endif ++ + #endif
