Skip to content
Snippets Groups Projects
Select Git revision
  • experimental default protected
  • nrb/airmax-test
  • v2023.2.4-ffs
  • nrb/ar9344-reset-sequence
  • autinerd/experimental-openwrt-24.10
  • v2023.2.3-ffs
  • v2023.2.2-ffs
  • v2023.2-ffs
  • v2023.1-ffs
  • v2022.1.4-ffs
  • feature/addMikrotikwAP
  • v2022.1.3-ffs
  • v2021.1.2-ffs
  • v2022.1.1-ffs
  • master protected
  • v2021.1.1-ffs
  • nrb/gluon-master-cpe510
  • v2021.1-ffs
  • v2020.2.3-ffs
  • nrbffs/fastd-remove-delay
  • experimental-2025-05-27
  • experimental-2025-05-27-base
  • experimental-2025-05-18
  • experimental-2025-05-18-base
  • experimental-2025-05-15
  • experimental-2025-05-15-base
  • experimental-2025-05-13
  • experimental-2025-05-13-base
  • experimental-2025-05-08
  • experimental-2025-05-08-base
  • experimental-2025-05-05
  • experimental-2025-05-05-base
  • experimental-2025-05-02
  • experimental-2025-05-02-base
  • experimental-2025-05-01
  • experimental-2025-05-01-base
  • experimental-2025-04-29
  • experimental-2025-04-29-base
  • experimental-2025-04-27
  • experimental-2025-04-27-base
40 results

patches

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Sven Eckelmann authored
    It was noticed that various devices had not the correct board-2.bin
    installed. This was caused by a typo in the package name. The ath10k driver
    (unfortunately) is then loading a completely unrelated BDF from the
    ath10k-board-qca4019 board-2.bin. It is usually a rather bad idea to use
    calibration data from a different board - but the effects depend on the
    actual device.
    
    For the PA1200, it was mostly noticed by the bad 2.4GHz performance.
    
    Signed-off-by: default avatarSven Eckelmann <sven@narfation.org>
    d4cb1777
    History
    Name Last commit Last update
    ..