[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: hwe-next Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
This bug was fixed in the package linux - 4.10.0-30.34 --- linux (4.10.0-30.34) zesty; urgency=low * CVE-2017-7533 - dentry name snapshots linux (4.10.0-29.33) zesty; urgency=low * linux: 4.10.0-29.33 -proposed tracker (LP: #1704961) * Opal and POWER9 DD2 (LP: #1702159) - powerpc/powernv: Tell OPAL about our MMU mode on POWER9 - powerpc/powernv: Fix boot on Power8 bare metal due to opal_configure_cores() * CVE-2017-1000364 - mm/mmap.c: do not blow on PROT_NONE MAP_FIXED holes in the stack - mm/mmap.c: expand_downwards: don't require the gap if !vm_prev * [Xenial] nvme: Quirks for PM1725 controllers (LP: #1704435) - nvme: Quirks for PM1725 controllers * hns: under heavy load, NIC may fail and require reboot (LP: #1704146) - net: hns: Bugfix for Tx timeout handling in hns driver * New ACPI identifiers for ThunderX SMMU (LP: #1703437) - iommu/arm-smmu: Plumb in new ACPI identifiers * CVE-2017-7482 - rxrpc: Fix several cases where a padded len isn't checked in ticket decode * CVE-2017-1000365 - fs/exec.c: account for argv/envp pointers * CVE-2017-10810 - drm/virtio: don't leak bo on drm_gem_object_init failure * Data corruption with hio driver (LP: #1701316) - SAUCE: hio: Fix incorrect use of enum req_opf values * arm64: fix crash reading /proc/kcore (LP: #1702749) - fs/proc: kcore: use kcore_list type to check for vmalloc/module address - arm64: mm: select CONFIG_ARCH_PROC_KCORE_TEXT * cxlflash update request in the Xenial SRU stream (LP: #1702521) - scsi: cxlflash: Refactor context reset to share reset logic - scsi: cxlflash: Support SQ Command Mode - scsi: cxlflash: Cleanup prints - scsi: cxlflash: Cancel scheduled workers before stopping AFU - scsi: cxlflash: Enable PCI device ID for future IBM CXL Flash AFU - scsi: cxlflash: Separate RRQ processing from the RRQ interrupt handler - scsi: cxlflash: Serialize RRQ access and support offlevel processing - scsi: cxlflash: Implement IRQ polling for RRQ processing - scsi: cxlflash: Update sysfs helper routines to pass config structure - scsi: cxlflash: Support dynamic number of FC ports - scsi: cxlflash: Remove port configuration assumptions - scsi: cxlflash: Hide FC internals behind common access routine - scsi: cxlflash: SISlite updates to support 4 ports - scsi: cxlflash: Support up to 4 ports - scsi: cxlflash: Fence EEH during probe - scsi: cxlflash: Remove unnecessary DMA mapping - scsi: cxlflash: Fix power-of-two validations - scsi: cxlflash: Fix warnings/errors - scsi: cxlflash: Improve asynchronous interrupt processing - scsi: cxlflash: Support multiple hardware queues - scsi: cxlflash: Add hardware queues attribute - scsi: cxlflash: Introduce hardware queue steering - cxl: Enable PCI device IDs for future IBM CXL adapters - scsi: cxlflash: Select IRQ_POLL - scsi: cxlflash: Combine the send queue locks - scsi: cxlflash: Update cxlflash_afu_sync() to return errno - scsi: cxlflash: Reset hardware queue context via specified register - scsi: cxlflash: Schedule asynchronous reset of the host - scsi: cxlflash: Handle AFU sync failures - scsi: cxlflash: Track pending scsi commands in each hardware queue - scsi: cxlflash: Flush pending commands in cleanup path - scsi: cxlflash: Add scsi command abort handler - scsi: cxlflash: Create character device to provide host management interface - scsi: cxlflash: Separate AFU internal command handling from AFU sync specifics - scsi: cxlflash: Introduce host ioctl support - scsi: cxlflash: Refactor AFU capability checking - scsi: cxlflash: Support LUN provisioning - scsi: cxlflash: Support AFU debug - scsi: cxlflash: Support WS16 unmap - scsi: cxlflash: Remove zeroing of private command data - scsi: cxlflash: Update TMF command processing - scsi: cxlflash: Avoid double free of character device - scsi: cxlflash: Update send_tmf() parameters - scsi: cxlflash: Update debug prints in reset handlers * Ath10k to read different board data file if specify in SMBIOS (LP: #1666742) - ath10k: search SMBIOS for OEM board file extension * APST gets enabled against explicit kernel option (LP: #1699004) - nvme: Display raw APST configuration via DYNAMIC_DEBUG - nvme: Add nvme_core.force_apst to ignore the NO_APST quirk - nvme: explicitly disable APST on quirked devices * Quirk for non-compliant PCI bridge on HiSilicon D05 board (LP: #1698706) - SAUCE: PCI: Support hibmc VGA cards behind a misbehaving HiSilicon bridge * New NVLINK2 patches (LP: #1701272) - powerpc/powernv/npu-dma: Add explicit flush when sending an ATSD - powerpc/npu-dma: Remove spurious WARN_ON when a PCI device has no of_node * ERAT invalidate on context switch removal (LP: #1700819) - powerpc: Only do ERAT invalidate on radix context
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
This bug was fixed in the package linux - 4.10.0-30.34 --- linux (4.10.0-30.34) zesty; urgency=low * CVE-2017-7533 - dentry name snapshots linux (4.10.0-29.33) zesty; urgency=low * linux: 4.10.0-29.33 -proposed tracker (LP: #1704961) * Opal and POWER9 DD2 (LP: #1702159) - powerpc/powernv: Tell OPAL about our MMU mode on POWER9 - powerpc/powernv: Fix boot on Power8 bare metal due to opal_configure_cores() * CVE-2017-1000364 - mm/mmap.c: do not blow on PROT_NONE MAP_FIXED holes in the stack - mm/mmap.c: expand_downwards: don't require the gap if !vm_prev * [Xenial] nvme: Quirks for PM1725 controllers (LP: #1704435) - nvme: Quirks for PM1725 controllers * hns: under heavy load, NIC may fail and require reboot (LP: #1704146) - net: hns: Bugfix for Tx timeout handling in hns driver * New ACPI identifiers for ThunderX SMMU (LP: #1703437) - iommu/arm-smmu: Plumb in new ACPI identifiers * CVE-2017-7482 - rxrpc: Fix several cases where a padded len isn't checked in ticket decode * CVE-2017-1000365 - fs/exec.c: account for argv/envp pointers * CVE-2017-10810 - drm/virtio: don't leak bo on drm_gem_object_init failure * Data corruption with hio driver (LP: #1701316) - SAUCE: hio: Fix incorrect use of enum req_opf values * arm64: fix crash reading /proc/kcore (LP: #1702749) - fs/proc: kcore: use kcore_list type to check for vmalloc/module address - arm64: mm: select CONFIG_ARCH_PROC_KCORE_TEXT * cxlflash update request in the Xenial SRU stream (LP: #1702521) - scsi: cxlflash: Refactor context reset to share reset logic - scsi: cxlflash: Support SQ Command Mode - scsi: cxlflash: Cleanup prints - scsi: cxlflash: Cancel scheduled workers before stopping AFU - scsi: cxlflash: Enable PCI device ID for future IBM CXL Flash AFU - scsi: cxlflash: Separate RRQ processing from the RRQ interrupt handler - scsi: cxlflash: Serialize RRQ access and support offlevel processing - scsi: cxlflash: Implement IRQ polling for RRQ processing - scsi: cxlflash: Update sysfs helper routines to pass config structure - scsi: cxlflash: Support dynamic number of FC ports - scsi: cxlflash: Remove port configuration assumptions - scsi: cxlflash: Hide FC internals behind common access routine - scsi: cxlflash: SISlite updates to support 4 ports - scsi: cxlflash: Support up to 4 ports - scsi: cxlflash: Fence EEH during probe - scsi: cxlflash: Remove unnecessary DMA mapping - scsi: cxlflash: Fix power-of-two validations - scsi: cxlflash: Fix warnings/errors - scsi: cxlflash: Improve asynchronous interrupt processing - scsi: cxlflash: Support multiple hardware queues - scsi: cxlflash: Add hardware queues attribute - scsi: cxlflash: Introduce hardware queue steering - cxl: Enable PCI device IDs for future IBM CXL adapters - scsi: cxlflash: Select IRQ_POLL - scsi: cxlflash: Combine the send queue locks - scsi: cxlflash: Update cxlflash_afu_sync() to return errno - scsi: cxlflash: Reset hardware queue context via specified register - scsi: cxlflash: Schedule asynchronous reset of the host - scsi: cxlflash: Handle AFU sync failures - scsi: cxlflash: Track pending scsi commands in each hardware queue - scsi: cxlflash: Flush pending commands in cleanup path - scsi: cxlflash: Add scsi command abort handler - scsi: cxlflash: Create character device to provide host management interface - scsi: cxlflash: Separate AFU internal command handling from AFU sync specifics - scsi: cxlflash: Introduce host ioctl support - scsi: cxlflash: Refactor AFU capability checking - scsi: cxlflash: Support LUN provisioning - scsi: cxlflash: Support AFU debug - scsi: cxlflash: Support WS16 unmap - scsi: cxlflash: Remove zeroing of private command data - scsi: cxlflash: Update TMF command processing - scsi: cxlflash: Avoid double free of character device - scsi: cxlflash: Update send_tmf() parameters - scsi: cxlflash: Update debug prints in reset handlers * Ath10k to read different board data file if specify in SMBIOS (LP: #1666742) - ath10k: search SMBIOS for OEM board file extension * APST gets enabled against explicit kernel option (LP: #1699004) - nvme: Display raw APST configuration via DYNAMIC_DEBUG - nvme: Add nvme_core.force_apst to ignore the NO_APST quirk - nvme: explicitly disable APST on quirked devices * Quirk for non-compliant PCI bridge on HiSilicon D05 board (LP: #1698706) - SAUCE: PCI: Support hibmc VGA cards behind a misbehaving HiSilicon bridge * New NVLINK2 patches (LP: #1701272) - powerpc/powernv/npu-dma: Add explicit flush when sending an ATSD - powerpc/npu-dma: Remove spurious WARN_ON when a PCI device has no of_node * ERAT invalidate on context switch removal (LP: #1700819) - powerpc: Only do ERAT invalidate on radix context
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
This bug was fixed in the package linux - 4.4.0-89.112 --- linux (4.4.0-89.112) xenial; urgency=low * CVE-2017-7533 - dentry name snapshots linux (4.4.0-88.111) xenial; urgency=low * linux: 4.4.0-88.111 -proposed tracker (LP: #1705270) * [Xenial] nvme: Quirks for PM1725 controllers (LP: #1704435) - nvme: Quirks for PM1725 controllers * Upgrade Redpine WLAN/BT driver to ver. 1.2 (production release) (LP: #1697829) - SAUCE: Redpine: Upgrade to ver. 1.2 production release * ubuntu/rsi driver has several issues as picked up by static analysis (LP: #1694733) - SAUCE: Redpine: Upgrade to ver. 1.2 production release * Redpine vendor driver - Switching to AP mode causes kernel panic (LP: #1700941) - SAUCE: Redpine: Upgrade to ver. 1.2 production release * CVE-2017-10810 - drm/virtio: don't leak bo on drm_gem_object_init failure * Ath10k to read different board data file if specify in SMBIOS (LP: #1666742) - ath10k: search SMBIOS for OEM board file extension * make snap-pkg support (LP: #1700747) - SAUCE: make snap-pkg support * ISST-LTE: Briggs:Stratton:UbuntuKVM: ics_opal_set_affinity on host kernel log using Intel X710 (i40e driver) (LP: #1703663) - i40e: use valid online CPU on q_vector initialization * Update snapcraft.yaml (LP: #1700480) - snapcraft.yaml: various improvements * Xenial update to 4.4.76 stable release (LP: #1702863) - ipv6: release dst on error in ip6_dst_lookup_tail - net: don't call strlen on non-terminated string in dev_set_alias() - decnet: dn_rtmsg: Improve input length sanitization in dnrmg_receive_user_skb - net: Zero ifla_vf_info in rtnl_fill_vfinfo() - af_unix: Add sockaddr length checks before accessing sa_family in bind and connect handlers - Fix an intermittent pr_emerg warning about lo becoming free. - net: caif: Fix a sleep-in-atomic bug in cfpkt_create_pfx - igmp: acquire pmc lock for ip_mc_clear_src() - igmp: add a missing spin_lock_init() - ipv6: fix calling in6_ifa_hold incorrectly for dad work - net/mlx5: Wait for FW readiness before initializing command interface - decnet: always not take dst->__refcnt when inserting dst into hash table - net: 8021q: Fix one possible panic caused by BUG_ON in free_netdev - sfc: provide dummy definitions of vswitch functions - ipv6: Do not leak throw route references - rtnetlink: add IFLA_GROUP to ifla_policy - netfilter: xt_TCPMSS: add more sanity tests on tcph->doff - netfilter: synproxy: fix conntrackd interaction - NFSv4: fix a reference leak caused WARNING messages - drm/ast: Handle configuration without P2A bridge - mm, swap_cgroup: reschedule when neeed in swap_cgroup_swapoff() - MIPS: Avoid accidental raw backtrace - MIPS: pm-cps: Drop manual cache-line alignment of ready_count - MIPS: Fix IRQ tracing & lockdep when rescheduling - ALSA: hda - Fix endless loop of codec configure - ALSA: hda - set input_path bitmap to zero after moving it to new place - drm/vmwgfx: Free hash table allocated by cmdbuf managed res mgr - usb: gadget: f_fs: Fix possibe deadlock - sysctl: enable strict writes - mm: numa: avoid waiting on freed migrated pages - KVM: x86: fix fixing of hypercalls - scsi: sd: Fix wrong DPOFUA disable in sd_read_cache_type - scsi: lpfc: Set elsiocb contexts to NULL after freeing it - qla2xxx: Fix erroneous invalid handle message - ARM: dts: BCM5301X: Correct GIC_PPI interrupt flags - net: mvneta: Fix for_each_present_cpu usage - MIPS: ath79: fix regression in PCI window initialization - net: korina: Fix NAPI versus resources freeing - MIPS: ralink: MT7688 pinmux fixes - MIPS: ralink: fix USB frequency scaling - MIPS: ralink: Fix invalid assignment of SoC type - MIPS: ralink: fix MT7628 pinmux typos - MIPS: ralink: fix MT7628 wled_an pinmux gpio - mtd: bcm47xxpart: limit scanned flash area on BCM47XX (MIPS) only - bgmac: fix a missing check for build_skb - mtd: bcm47xxpart: don't fail because of bit-flips - bgmac: Fix reversed test of build_skb() return value. - net: bgmac: Fix SOF bit checking - net: bgmac: Start transmit queue in bgmac_open - net: bgmac: Remove superflous netif_carrier_on() - powerpc/eeh: Enable IO path on permanent error - gianfar: Do not reuse pages from emergency reserve - Btrfs: fix truncate down when no_holes feature is enabled - virtio_console: fix a crash in config_work_handler - swiotlb-xen: update dev_addr after swapping pages - xen-netfront: Fix Rx stall during network stress and OOM - scsi: virtio_scsi: Reject commands when virtqueue is broken - platform/x86: ideapad-laptop: handle ACPI event 1 - amd-xgbe: Check xgbe_init() return code - net: dsa: Check return value of phy_connect_direct() - drm/amdgpu: check ring being ready before using
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
This bug was fixed in the package linux - 4.4.0-89.112 --- linux (4.4.0-89.112) xenial; urgency=low * CVE-2017-7533 - dentry name snapshots linux (4.4.0-88.111) xenial; urgency=low * linux: 4.4.0-88.111 -proposed tracker (LP: #1705270) * [Xenial] nvme: Quirks for PM1725 controllers (LP: #1704435) - nvme: Quirks for PM1725 controllers * Upgrade Redpine WLAN/BT driver to ver. 1.2 (production release) (LP: #1697829) - SAUCE: Redpine: Upgrade to ver. 1.2 production release * ubuntu/rsi driver has several issues as picked up by static analysis (LP: #1694733) - SAUCE: Redpine: Upgrade to ver. 1.2 production release * Redpine vendor driver - Switching to AP mode causes kernel panic (LP: #1700941) - SAUCE: Redpine: Upgrade to ver. 1.2 production release * CVE-2017-10810 - drm/virtio: don't leak bo on drm_gem_object_init failure * Ath10k to read different board data file if specify in SMBIOS (LP: #1666742) - ath10k: search SMBIOS for OEM board file extension * make snap-pkg support (LP: #1700747) - SAUCE: make snap-pkg support * ISST-LTE: Briggs:Stratton:UbuntuKVM: ics_opal_set_affinity on host kernel log using Intel X710 (i40e driver) (LP: #1703663) - i40e: use valid online CPU on q_vector initialization * Update snapcraft.yaml (LP: #1700480) - snapcraft.yaml: various improvements * Xenial update to 4.4.76 stable release (LP: #1702863) - ipv6: release dst on error in ip6_dst_lookup_tail - net: don't call strlen on non-terminated string in dev_set_alias() - decnet: dn_rtmsg: Improve input length sanitization in dnrmg_receive_user_skb - net: Zero ifla_vf_info in rtnl_fill_vfinfo() - af_unix: Add sockaddr length checks before accessing sa_family in bind and connect handlers - Fix an intermittent pr_emerg warning about lo becoming free. - net: caif: Fix a sleep-in-atomic bug in cfpkt_create_pfx - igmp: acquire pmc lock for ip_mc_clear_src() - igmp: add a missing spin_lock_init() - ipv6: fix calling in6_ifa_hold incorrectly for dad work - net/mlx5: Wait for FW readiness before initializing command interface - decnet: always not take dst->__refcnt when inserting dst into hash table - net: 8021q: Fix one possible panic caused by BUG_ON in free_netdev - sfc: provide dummy definitions of vswitch functions - ipv6: Do not leak throw route references - rtnetlink: add IFLA_GROUP to ifla_policy - netfilter: xt_TCPMSS: add more sanity tests on tcph->doff - netfilter: synproxy: fix conntrackd interaction - NFSv4: fix a reference leak caused WARNING messages - drm/ast: Handle configuration without P2A bridge - mm, swap_cgroup: reschedule when neeed in swap_cgroup_swapoff() - MIPS: Avoid accidental raw backtrace - MIPS: pm-cps: Drop manual cache-line alignment of ready_count - MIPS: Fix IRQ tracing & lockdep when rescheduling - ALSA: hda - Fix endless loop of codec configure - ALSA: hda - set input_path bitmap to zero after moving it to new place - drm/vmwgfx: Free hash table allocated by cmdbuf managed res mgr - usb: gadget: f_fs: Fix possibe deadlock - sysctl: enable strict writes - mm: numa: avoid waiting on freed migrated pages - KVM: x86: fix fixing of hypercalls - scsi: sd: Fix wrong DPOFUA disable in sd_read_cache_type - scsi: lpfc: Set elsiocb contexts to NULL after freeing it - qla2xxx: Fix erroneous invalid handle message - ARM: dts: BCM5301X: Correct GIC_PPI interrupt flags - net: mvneta: Fix for_each_present_cpu usage - MIPS: ath79: fix regression in PCI window initialization - net: korina: Fix NAPI versus resources freeing - MIPS: ralink: MT7688 pinmux fixes - MIPS: ralink: fix USB frequency scaling - MIPS: ralink: Fix invalid assignment of SoC type - MIPS: ralink: fix MT7628 pinmux typos - MIPS: ralink: fix MT7628 wled_an pinmux gpio - mtd: bcm47xxpart: limit scanned flash area on BCM47XX (MIPS) only - bgmac: fix a missing check for build_skb - mtd: bcm47xxpart: don't fail because of bit-flips - bgmac: Fix reversed test of build_skb() return value. - net: bgmac: Fix SOF bit checking - net: bgmac: Start transmit queue in bgmac_open - net: bgmac: Remove superflous netif_carrier_on() - powerpc/eeh: Enable IO path on permanent error - gianfar: Do not reuse pages from emergency reserve - Btrfs: fix truncate down when no_holes feature is enabled - virtio_console: fix a crash in config_work_handler - swiotlb-xen: update dev_addr after swapping pages - xen-netfront: Fix Rx stall during network stress and OOM - scsi: virtio_scsi: Reject commands when virtqueue is broken - platform/x86: ideapad-laptop: handle ACPI event 1 - amd-xgbe: Check xgbe_init() return code - net: dsa: Check return value of phy_connect_direct() - drm/amdgpu: check ring being ready before using
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Tags removed: verification-needed-zesty ** Tags added: verification-done-zesty ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: hwe-next Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Committed Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Committed Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
@AceLan and @Shrirang, Could you please verify if the fix available on the kernels currently in -proposed fix the issue? Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Committed Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- zesty' to 'verification-done-zesty'. If the problem still exists, change the tag 'verification-needed-zesty' to 'verification-failed-zesty'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-zesty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Changed in: linux (Ubuntu Yakkety) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Changed in: linux (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux (Ubuntu Zesty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Yakkety: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Changed in: hwe-next Status: New => In Progress ** Tags added: originate-from-1641490 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Yakkety: New Status in linux source package in Zesty: New Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Changed in: linux (Ubuntu Yakkety) Status: Won't Fix => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Yakkety: New Status in linux source package in Zesty: New Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Changed in: linux (Ubuntu Yakkety) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: New Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
On XPS-13-9360 (SMBIOS board variant BDF_RV_0520), ath10k falls back to default firmware. Partial log is below: [ 1151.458814] ath10k_pci :3a:00.0: Hardware name qca6174 hw3.2 version 0x503 [ 1151.458844] ath10k_pci :3a:00.0: Direct firmware load for ath10k/cal-pci-:3a:00.0.bin failed with error -2 [ 1151.458849] ath10k_pci :3a:00.0: trying fw api 5 [ 1151.458865] ath10k_pci :3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [ 1151.458870] ath10k_pci :3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [ 1151.458873] ath10k_pci :3a:00.0: trying fw api 4 [ 1151.459279] ath10k_pci :3a:00.0: found fw version WLAN.RM.2.0-00180-QCARMSWPZ-1 [ 1151.459283] ath10k_pci :3a:00.0: found fw timestamp 1438990954 [ 1151.459287] ath10k_pci :3a:00.0: found otp image ie (23921 B) [ 1151.459290] ath10k_pci :3a:00.0: found fw image ie (709754 B) [ 1151.459293] ath10k_pci :3a:00.0: found firmware features ie (2 B) [ 1151.459296] ath10k_pci :3a:00.0: Enabling feature bit: 6 [ 1151.459299] ath10k_pci :3a:00.0: Enabling feature bit: 7 [ 1151.459302] ath10k_pci :3a:00.0: Enabling feature bit: 8 [ 1151.459305] ath10k_pci :3a:00.0: features [ 1151.459310] ath10k_pci :3a:00.0: : c0 01 00 00 00 00 00 00 [ 1151.459313] ath10k_pci :3a:00.0: found fw ie wmi op version 4 [ 1151.459316] ath10k_pci :3a:00.0: using fw api 4 [ 1151.459320] ath10k_pci :3a:00.0: boot upload otp to 0x1234 len 23921 for board id [ 1151.521485] ath10k_pci :3a:00.0: boot get otp board id result 0x0001 board_id 0 chip_id 0 [ 1151.521489] ath10k_pci :3a:00.0: found and validated bdf variant smbios_type 0xf8 bdf BDF_RV_0520 [ 1151.521494] ath10k_pci :3a:00.0: boot using board name 'bus=pci,vendor=168c,device=003e,subsystem-vendor=1a56,subsystem-device=1535,variant=RV_0520' [ 1151.521579] ath10k_pci :3a:00.0: board name [ 1151.521580] ath10k_pci :3a:00.0: : 62 75 73 3d 70 63 69 2c 76 65 6e 64 6f 72 3d 31 bus=pci,vendor=1 [ 1151.521581] ath10k_pci :3a:00.0: 0010: 36 38 63 2c 64 65 76 69 63 65 3d 30 30 33 65 2c 68c,device=003e, [ 1151.521582] ath10k_pci :3a:00.0: 0020: 73 75 62 73 79 73 74 65 6d 2d 76 65 6e 64 6f 72 subsystem-vendor [ 1151.521584] ath10k_pci :3a:00.0: 0030: 3d 31 36 38 63 2c 73 75 62 73 79 73 74 65 6d 2d =168c,subsystem- [ 1151.521585] ath10k_pci :3a:00.0: 0040: 64 65 76 69 63 65 3d 33 33 34 65 device=334e [ 1151.521749] ath10k_pci :3a:00.0: board name [ 1151.521750] ath10k_pci :3a:00.0: : 62 75 73 3d 70 63 69 2c 76 65 6e 64 6f 72 3d 31 bus=pci,vendor=1 [ 1151.521751] ath10k_pci :3a:00.0: 0010: 36 38 63 2c 64 65 76 69 63 65 3d 30 30 33 65 2c 68c,device=003e, [ 1151.521752] ath10k_pci :3a:00.0: 0020: 73 75 62 73 79 73 74 65 6d 2d 76 65 6e 64 6f 72 subsystem-vendor [ 1151.521753] ath10k_pci :3a:00.0: 0030: 3d 31 61 35 36 2c 73 75 62 73 79 73 74 65 6d 2d =1a56,subsystem- [ 1151.521754] ath10k_pci :3a:00.0: 0040: 64 65 76 69 63 65 3d 31 35 33 35 device=1535 [ 1151.521755] ath10k_pci :3a:00.0: boot found match for name 'bus=pci,vendor=168c,device=003e,subsystem-vendor=1a56,subsystem-device=1535' [ 1151.521756] ath10k_pci :3a:00.0: boot found board data for 'bus=pci,vendor=168c,device=003e,subsystem-vendor=1a56,subsystem-device=1535' [ 1151.521757] ath10k_pci :3a:00.0: using board api 2 [ 1151.522014] ath10k_pci :3a:00.0: boot did not find a calibration file, try DT next: -2 [ 1151.522015] ath10k_pci :3a:00.0: boot did not find DT entry, try OTP next: -2 [ 1151.522102] ath10k_pci :3a:00.0: boot push board extended data addr 0x0 [ 1151.542144] ath10k_pci :3a:00.0: boot upload otp to 0x1234 len 23921 [ 1151.605488] ath10k_pci :3a:00.0: boot otp execute result 3 [ 1151.605490] ath10k_pci :3a:00.0: boot using calibration mode otp [ 1151.605492] ath10k_pci :3a:00.0: boot uploading firmware image c90001239dc4 len 709754 mode normal [ 1165.436677] wlp58s0: authenticate with 04:a1:51:32:0d:b7 [ 1165.487505] wlp58s0: send auth to 04:a1:51:32:0d:b7 (try 1/3) [ 1165.492422] wlp58s0: send auth to 04:a1:51:32:0d:b7 (try 2/3) [ 1165.497119] wlp58s0: send auth to 04:a1:51:32:0d:b7 (try 3/3) [ 1165.501897] wlp58s0: authentication with 04:a1:51:32:0d:b7 timed out [ 1165.989771] wlp58s0: authenticate with c0:c1:c0:2a:ab:e0 [ 1166.045768] wlp58s0: send auth to c0:c1:c0:2a:ab:e0 (try 1/3) [ 1166.047753] wlp58s0: authenticated [ 1166.050204] wlp58s0: associate with c0:c1:c0:2a:ab:e0 (try 1/3) [ 1166.056954] wlp58s0: RX AssocResp from c0:c1:c0:2a:ab:e0 (capab=0x411 status=0 aid=1) [ 1166.060159] wlp58s0: associated [ 1166.060278] IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes ready ** Attachment added: "xps-13-ath10k log"
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux source package in Yakkety: New Status in linux source package in Zesty: New Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Changed in: linux (Ubuntu) Assignee: AceLan Kao (acelankao) => Shrirang Bagul (shrirang-bagul) ** Changed in: hwe-next Assignee: AceLan Kao (acelankao) => Shrirang Bagul (shrirang-bagul) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
Instead, it will be better to backport this patch (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1657b8f84ed9fc1d2a100671f1d42d6286f20073) which fixes possible regression issues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
@Acelan, The patch mentioned in comment#1 was reverted in the upstream tree (see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v4.12=005c3490e9db23738d91e02788606c0fe4734723). Do we still want to backport this to xenial & yaketty? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
** Also affects: hwe-next Importance: Undecided Status: New ** Changed in: hwe-next Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: hwe-next Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1666742] Re: Ath10k to read different board data file if specify in SMBIOS
We need to backport this commit to xenial and yaketty https://patchwork.kernel.org/patch/9521307/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1666742 Title: Ath10k to read different board data file if specify in SMBIOS Status in linux package in Ubuntu: In Progress Bug description: Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified, among others, by device and sybsystem ids. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a different board data file. To solve the issue QCA uses SMBIOS type 0xF8 to store Board Data File Name Extension to specify the extension/variant name. The driver will take the extension suffix into consideration and will load the right (non-default) board data file if necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
