aboutsummaryrefslogtreecommitdiffstats
path: root/package/firmware
Commit message (Collapse)AuthorAgeFilesLines
* firmware: intel-microcode: bump to 20180703Zoltan HERPAI2018-08-091-6/+6
| | | | | | | | | | | | | | | | | | | | | | | * New upstream microcode data file 20180703 + Updated Microcodes: sig 0x000206d6, pf_mask 0x6d, 2018-05-08, rev 0x061d, size 18432 sig 0x000206d7, pf_mask 0x6d, 2018-05-08, rev 0x0714, size 19456 sig 0x000306e4, pf_mask 0xed, 2018-04-25, rev 0x042d, size 15360 sig 0x000306e7, pf_mask 0xed, 2018-04-25, rev 0x0714, size 17408 sig 0x000306f2, pf_mask 0x6f, 2018-04-20, rev 0x003d, size 33792 sig 0x000306f4, pf_mask 0x80, 2018-04-20, rev 0x0012, size 17408 sig 0x000406f1, pf_mask 0xef, 2018-04-19, rev 0xb00002e, size 28672 sig 0x00050654, pf_mask 0xb7, 2018-05-15, rev 0x200004d, size 31744 sig 0x00050665, pf_mask 0x10, 2018-04-20, rev 0xe00000a, size 18432 sig 0x000706a1, pf_mask 0x01, 2017-12-26, rev 0x0022, size 73728 + First batch of fixes for: Intel SA-00115, CVE-2018-3639, CVE-2018-3640 + Implements IBRS/IBPB/STIPB support, Spectre-v2 mitigation + SSBD support (Spectre-v4 mitigation) and fix Spectre-v3a for: Sandybridge server, Ivy Bridge server, Haswell server, Skylake server, Broadwell server, a few HEDT Core i7/i9 models that are actually gimped server dies. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* ath10k: update QCA4019 firmwareMassimo Tum2018-07-301-1/+1
| | | | | | | | | | With AVM Fritz!Box 4040 and OpenWrt 18.06 RC1 there are many kernel warnings kern.warn kernel: [87771.917049] ath10k_ahb a000000.wifi: Invalid VHT mcs 15 peer stats and there are disconnections when the connected clients are many, at the moment I tried with 16 clients on 2.4 GHz and 8 on 5 GHZ. Firmware 10.4-3.5.3-00057 fixes these warnings and the problem of disconnections of some clients. Signed-off-by: Massimo Tum <masnia@tiscali.it>
* ipq-wifi: add a note / reminder about upstreaming new board filesChristian Lamparter2018-07-301-0/+3
| | | | | | | | |Please send a mail with your device-specific board files upstream. |You can find instructions and examples on the linux-wireless wiki: |<https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: amd64-microcode: update to 20180524Zoltan HERPAI2018-07-071-2/+2
| | | | | | | | | | | | | * New microcode update packages from AMD upstream: + New Microcodes: sig 0x00800f12, patch id 0x08001227, 2018-02-09 + Updated Microcodes: sig 0x00600f12, patch id 0x0600063e, 2018-02-07 sig 0x00600f20, patch id 0x06000852, 2018-02-06 * Adds Spectre v2 (CVE-2017-5715) microcode-based mitigation support, plus other unspecified fixes/updates. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* ipq40xx: add support for the ZyXEL NBG6617Christian Lamparter2018-06-262-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for ZyXEL NBG6617 Hardware highlights: SOC: IPQ4018 / QCA Dakota CPU: Quad-Core ARMv7 Processor rev 5 (v7l) Cortex-A7 DRAM: 256 MiB DDR3L-1600/1866 Nanya NT5CC128M16IP-DI @ 537 MHz NOR: 32 MiB Macronix MX25L25635F ETH: Qualcomm Atheros QCA8075 Gigabit Switch (4 x LAN, 1 x WAN) USB: 1 x 3.0 (via Synopsys DesignWare DWC3 controller in the SoC) WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11bgn 2:2x2 WLAN2: Qualcomm Atheros QCA4018 5GHz 802.11a/n/ac 2:2x2 INPUT: RESET Button, WIFI/Rfkill Togglebutton, WPS Button LEDS: Power, WAN, LAN 1-4, WLAN 2.4GHz, WLAN 5GHz, USB, WPS Serial: WARNING: The serial port needs a TTL/RS-232 3.3v level converter! The Serial setting is 115200-8-N-1. The 1x4 .1" header comes pre-soldered. Pinout: 1. 3v3 (Label printed on the PCB), 2. RX, 3. GND, 4. TX first install / debricking / restore stock: 0. Have a PC running a tftp-server @ 192.168.1.99/24 1. connect the PC to any LAN-Ports 2. put the openwrt...-factory.bin (or V1.00(ABCT.X).bin for stock) file into the tftp-server root directory and rename it to just "ras.bin". 3. power-cycle the router and hold down the the WPS button (for 30sek) 4. Wait (for a long time - the serial console provides some progress reports. The u-boot says it best: "Please be patient". 5. Once the power LED starts to flashes slowly and the USB + WPS LEDs flashes fast at the same time. You have to reboot the device and it should then come right up. Installation via Web-UI: 0. Connect a PC to the powered-on router. It will assign your PC a IP-address via DHCP 1. Access the Web-UI at 192.168.1.1 (Default Passwort: 1234) 2. Go to the "Expert Mode" 3. Under "Maintenance", select "Firmware-Upgrade" 4. Upload the OpenWRT factory image 5. Wait for the Device to finish. It will reboot into OpenWRT without any additional actions needed. To open the ZyXEL NBG6617: 0. remove the four rubber feet glued on the backside 1. remove the four philips screws and pry open the top cover (by applying force between the plastic top housing from the backside/lan-port side) Access the real u-boot shell: ZyXEL uses a proprietary loader/shell on top of u-boot: "ZyXEL zloader v2.02" When the device is starting up, the user can enter the the loader shell by simply pressing a key within the 3 seconds once the following string appears on the serial console: | Hit any key to stop autoboot: 3 The user is then dropped to a locked shell. |NBG6617> HELP |ATEN x[,y] set BootExtension Debug Flag (y=password) |ATSE x show the seed of password generator |ATSH dump manufacturer related data in ROM |ATRT [x,y,z,u] RAM read/write test (x=level, y=start addr, z=end addr, u=iterations) |ATGO boot up whole system |ATUR x upgrade RAS image (filename) |NBG6617> In order to escape/unlock a password challenge has to be passed. Note: the value is dynamic! you have to calculate your own! First use ATSE $MODELNAME (MODELNAME is the hostname in u-boot env) to get the challange value/seed. |NBG6617> ATSE NBG6617 |012345678901 This seed/value can be converted to the password with the help of this bash script (Thanks to http://www.adslayuda.com/Zyxel650-9.html authors): - tool.sh - ror32() { echo $(( ($1 >> $2) | (($1 << (32 - $2) & (2**32-1)) ) )) } v="0x$1" a="0x${v:2:6}" b=$(( $a + 0x10F0A563)) c=$(( 0x${v:12:14} & 7 )) p=$(( $(ror32 $b $c) ^ $a )) printf "ATEN 1,%X\n" $p - end of tool.sh - |# bash ./tool.sh 012345678901 | |ATEN 1,879C711 copy and paste the result into the shell to unlock zloader. |NBG6617> ATEN 1,0046B0017430 If the entered code was correct the shell will change to use the ATGU command to enter the real u-boot shell. |NBG6617> ATGU |NBG6617# Co-authored-by: David Bauer <mail@david-bauer.net> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com> Signed-off-by: David Bauer <mail@david-bauer.net>
* ipq40xx: add support for ZyXEL WRE6606Magnus Frühling2018-06-182-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: SOC: Qualcomm IPQ4018 (DAKOTA) ARM Quad-Core RAM: 128 MB Nanya NT5CC64M16GP-DI FLASH: 16 MiB Macronix MX25L12845EMI-12G ETH: Qualcomm QCA8072 WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11b/g/n 2x2 WLAN2: Qualcomm Atheros QCA4018 5GHz 802.11n/ac W2 2x2 INPUT: WPS, Mode-toggle-switch LED: Power, WLAN 2.4GHz, WLAN 5GHz, LAN, WPS (LAN not controllable by software) (WLAN each green / red) SERIAL: Header next to eth-phy. VCC, TX, GND, RX (Square hole is VCC) The Serial setting is 115200-8-N-1. Tested and working: - Ethernet (Correct MAC-address) - 2.4 GHz WiFi (Correct MAC-address) - 5 GHz WiFi (Correct MAC-address) - Factory installation from tftp - OpenWRT sysupgrade - LEDs - WPS Button Not Working: - Mode-toggle-switch Install via TFTP: Connect to the devices serial. Hit Enter-Key in bootloader to stop autobooting. Command `tftpboot` will pull an initramfs image named `C0A86302.img` from a tftp server at `192.168.99.08/24`. After successfull transfer, boot the image with `bootm`. To persistently write the firmware, flash an openwrt sysupgrade image from inside the initramfs, for example transfer via `scp <sysupgrade> root@192.168.1.1:/tmp` and flash on the device with `sysupgrade -n /tmp/<sysupgrade>`. append-cmdline patch taken from chunkeeys work on the NBG6617. Signed-off-by: Magnus Frühling <skorpy@frankfurt.ccc.de> Co-authored-by: David Bauer <mail@david-bauer.net> Co-authored-by: Christian Lamparter <chunkeey@googlemail.com>
* brcm2708: move wifi calibration EEPROMs out of base-filesDaniel Golle2018-06-141-0/+88
| | | | | | | | Ship EEPROM blobs for specific supported board only and don't have them lurking around in our source tree but rather download them from @github/RPi-Distro/firmware-nonfree upstream. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* linux-firmware: add firmware for BCM43455 SDIO wlan found on RPi3B+Daniel Golle2018-06-141-0/+9
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ath10k-firmware: Fix two more typosRosen Penev2018-05-301-2/+2
| | | | | | Actually tested with a local build instead of with scp'ing the firmware. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ath10k-firmware: Fix typo in last commitRosen Penev2018-05-271-2/+0
| | | | Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ath10k-firmware: Fix QCA6174 supportRosen Penev2018-05-271-2/+16
| | | | | | | | | | | | | | Currently when installing the firmware, a bunch of files and directories that the ath10k driver does not look for are created. The package now installs firmware for both hw 2.1 and 3.0 devices. 2.1 is abandonware but may be useful to keep. 3.0 firmware was tested on a Killer 1535 to be relatively stable with 802.11w disabled. 802.11w causes multiple firmware crashes but that's true of other ath10k firmwares as well. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ath10k-firmware: Fix mirror hash sumHauke Mehrtens2018-05-211-1/+1
| | | | | | | | This now matches what was generated locally on my PC and the file on the mirror server. Fixes: 349fe46103359 ("ath10k-firmware: Update QCA988X firmware to the latest version") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath3k: Add firmware support for QCA RomeRobert Marko2018-05-181-0/+4
| | | | | | | Add needed firmware for newer QCA Rome Bluetooth family. This enables use of bluetooth with ath3k driver on QCA9377/9378 devices. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ath10k-firmware: Update QCA988X firmware to the latest versionTimo Sigurdsson2018-05-181-4/+4
| | | | | | | | | | This patch updates the QCA988X firmware to the latest revision firmware-5.bin_10.2.4-1.0-00037 found in the ath10k-firmware and linux-firmware repositories. Tested on TP-Link Archer C7 v2 (ar71xx). Signed-off-by: Timo Sigurdsson <public_timo.s@silentcreek.de>
* linux-firmware: Add firmware for usb-serial-ti-usbDavid Woodhouse2018-05-151-0/+13
| | | | Signed-off-by: David Woodhouse <dwmw2@infradead.org>
* ipq-wifi: drop custom board-2.binsSven Eckelmann2018-04-237-7/+3
| | | | | | | | | | | | | The BDFs for all boards were upstreamed to the ath10k-firmware repository and are now part of ath10k-firmware 2018-04-19. We switched to the upstream board-2.bin, hence the files can be removed here. Keep the ipq-wifi package in case new boards are added. It might take some time till board-2.bins send upstream are merged. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* firmware: ath10k-firmware: update to 2018-04-19Sven Eckelmann2018-04-231-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * introduces the BDFs in /lib/firmware/ath10k/QCA4019/hw1.0/board-2.bin for: - 8devices Jalapeno - Asus RT-AC58U - AVM FRITZ!Box 4040 - GL.iNet GL-B1300 - Meraki MR33 - Netgear EX6100v2 - Netgear EX6150v2 - OpenMesh A62 * introduces the BDFs in /lib/firmware/ath10k/QCA9888/hw2.0/board-2.bin - OpenMesh A62 * adds new firmware for QCA6174 hw3.0 - firmware-6.bin_RM.4.4.1.c1-00038-QCARMSWP-1 - firmware-6.bin_RM.4.4.1.c1-00041-QCARMSWP-1 * various undocumented BDF updates to: - QCA4019 hw1.0: + bus=ahb,bmi-chip-id=0,bmi-board-id=16 + bus=ahb,bmi-chip-id=0,bmi-board-id=17 + bus=ahb,bmi-chip-id=0,bmi-board-id=19 + bus=ahb,bmi-chip-id=0,bmi-board-id=20 + bus=ahb,bmi-chip-id=0,bmi-board-id=21 + bus=ahb,bmi-chip-id=0,bmi-board-id=29 + bus=ahb,bmi-chip-id=0,bmi-board-id=30 - QCA9888 hw2.0: + bus=pci,bmi-chip-id=0,bmi-board-id=16 + bus=pci,bmi-chip-id=0,bmi-board-id=17 + bus=pci,bmi-chip-id=0,bmi-board-id=18 + bus=pci,bmi-chip-id=0,bmi-board-id=23 + bus=pci,bmi-chip-id=0,bmi-board-id=24 + bus=pci,bmi-chip-id=0,bmi-board-id=25 - QCA9984 hw1.0: + bus=pci,bmi-chip-id=0,bmi-board-id=1 + bus=pci,bmi-chip-id=0,bmi-board-id=3 + bus=pci,bmi-chip-id=0,bmi-board-id=5 + bus=pci,bmi-chip-id=0,bmi-board-id=6 + bus=pci,bmi-chip-id=0,bmi-board-id=7 + bus=pci,bmi-chip-id=0,bmi-board-id=8 Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>
* mac80211: add RedPine RS9113 module supportEvgeniy Didin2018-04-181-0/+6
| | | | | | | | | | | RedPine RS9113 wireless module requires rsi91x driver to be built and linux-firmware/rsi/rs9113_wlan_qspi.rps to be installed. Also we add patch for successful compilation of rsi91x driver. Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org>
* ath10k-ct: Update firmwareBen Greear2018-04-131-24/+24
| | | | | | | | | | | | | | | This firmware has only small changes from the last commit, but it does have an important fix for at least some PTK rekey logic. The old firmware would have issues if the driver managed to set a clear key while encryption was 'enabled'. This new firmware for both wave-1 and wave-2 should not be susceptible to this type of bug any more. And remove mesh-bcast IE flag from wave-2, still need more work before we can enable that flag in ath10k-ct firmware it seems. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ipq40xx: unbundle firmware and board fileMathias Kresin2018-04-131-1/+1
| | | | | | | | | | | Don't select the firmware with the board file, it prevents an easy use of the -ct ath10k firmware. Select the firmware within the default packages instead. Remove the per device selection of the firmware now that it the firmware is selected by default. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ipq40xx: add support for Netgear EX6100v2/EX6150v2David Bauer2018-04-132-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: SOC: Qualcomm IPQ4018 (DAKOTA) ARM Quad-Core RAM: 256 MB Winbond W632GU6KB12J FLASH: 16 MiB Macronix MX25L12805D ETH: Qualcomm QCA8072 WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11b/g/n/ac 2x2 WLAN2: Qualcomm Atheros QCA4018 5GHz 802.11n/ac 1x1 (EX6100) 2x2 (EX6150) INPUT: Power, WPS, reset button AP / Range-extender toggle LED: Power, Router, Extender (dual), WPS, Left-/Right-arrow SERIAL: Header next to QCA8072 chip. VCC, TX, RX, GND (Square hole is VCC) WARNING: The serial port needs a TTL/RS-232 v3.3 level converter! The Serial setting is 115200-8-N-1. Tested and working: - Ethernet - 2.4 GHz WiFi (Correct MAC-address) - 5 GHz WiFi (Correct MAC-address) - Factory installation from WebIF - Factory installation from tftp - OpenWRT sysupgrade (Preserving and non-preserving) - LEDs - Buttons Not Working: - AP/Extender toggle-switch Untested: - Support on EX6100v2. They share the same GPL-Code and vendor-images. The 6100v2 seems to lack one 5GHz stream and differs in the 5GHz board-blob. I only own a EX6150v2, therefore i am only able to verify functionality on this device. Install via Web-Interface: Upload the factory image to the device to the Netgear Web-Interface. The device might asks you to confirm the update a second time due to detecting the OpenWRT firmware as older. The device will automatically reboot after the image is written to flash. Install via TFTP: Connect to the devices serial. Hit Enter-Key in bootloader to stop autobooting. Command "fw_recovery" will start a tftp server, waiting for a DNI image to be pushed. Assign your computer the IP-address 192.168.1.10/24. Push image with tftp -4 -v -m binary 192.168.1.1 -c put <OPENWRT_FACTORY> Device will erase factory-partition first, then writes the pushed image to flash and reboots. Parts of this commit are based on Thomas Hebb's work on the openwrt-devel mailinglist. See https://lists.openwrt.org/pipermail/openwrt-devel/2018-January/043418.html Signed-off-by: David Bauer <mail@david-bauer.net>
* ipq-wifi: Add 8devices JalapenoRobert Marko2018-04-132-1/+2
| | | | | | | Add custom board-2.bin for 8devices Jalapeno. Upstreaming is in progress. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ath10k-ct: Update firmware to latest.Ben Greear2018-03-311-29/+29
| | | | | | | | | | | | | | Wave-1 firmware has a fix for 'addba' not finding the peer. Thanks to Hauke for finding and reporting this. Wave-2 firmware has a fix for leaking a peer multicast key when a monitor device is created. And I re-ordered the '4019' firmware images in the Makefile to match the order of the others. No functional change for that reorder. Signed-off-by: Ben Greear <greearb@candelatech.com> Tested-by: Rosen Penev <rosenp@gmail.com>
* ath10k-ct: Add htt-mgt variants of ath10k-ct firmware.Ben Greear2018-03-231-33/+217
| | | | | | | | | | | | | | | | | | The HTT-MGT variants transport management frames over the normal HTT tx path, just like data frames. This saves limitted WMI buffers which can become depleted if lots of management frames become stuck in TX queues due to peer that went away. In addition, at least for the wave-1 firmware, htt-mgt is required in order for 802.11r (fast roaming) authentication to function properly. The htt-mgt firmware requires the use of the ath10k-ct driver. Normal non-htt-mgt ath10k-ct firmware should work with stock drivers. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-ct: Update wave-1 and wave-2 firmware to latest.Ben Greear2018-03-231-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This updates to latest ath10k-ct firmware. Hopefully we are at the end of the development cycle for this firmware release, so these should be stable. wave-1 changes since last release: Release 20 * Allow flushing peer when deleting. Hopefully this will allow the peer delete command to happen in a reasonable amount of time even if the RF environment is busy (or peer has died). To enable this, set the high flag in the mac-addr second word in the ath10k driver near end of the ath10k_wmi_op_gen_peer_delete method: cmd->peer_macaddr.word1 |= __cpu_to_le32(0x80000000); * Attempt to fix crash seen in resmgr-ocs, appearantly due to list corruption. Use a temporary list instead of trying to rely on for-each-safe. * Add flag to tx-descriptor to allow driver to request no-ack on data frames. This is bit 15 on the flag1 field (previously un-used). * Add option to support specifying the tx-rate-code and retry count on a per-packet basis. Only a single series is supported at this time. Useful mainly for radiotap monitor-tx type testing at this point. * Fix crash on startup when chip is at -40 deg C and calibration fails. Instead of asserting, just keep retrying calibration, which appears to start working after a few minutes (when the chip warms up). * Allow reporting per-chain rssi for management frames. We pack the values into empty space in the mgt-frame wmi header. This will only be enabled if the driver requests it, since otherwise the driver is assumed to not understand the new API. ath10k-ct drivers that support this feature will automatically enable it. * A customer reports a case that appears to be the hardware not properly detecting end of AMPDU, so frames were being mis-delivered to the wrong peer. Attempt to work around this, and in doing so, clean up a bunch of void* abuse in the block-ack reordering code (could not ever confirm there was a problem in this area). * Re-work the rx-mem logic to be less complicated and to use less memory. * Attempt to fix crash that appearanty happens because the driver can sometimes delete a vdev in 'up' state. * Attempt to fix hung scan state machine issues. * Fix crash in tx path due to un-initialized memory. wave-2 changes since last release: Release 10 * Fix an assert related to tx scheduling. This hopefully fixes what appears to be a regression that I added some time back. * Enable CSI reporting for 9984, and maybe 9888/9886. Only in non-trimmed builds. * Other stability improvements, including regression fixes from some tricky bugs introduced in earlier releases. * Allow compiling for IPQ4019 chipset. * Firmware will now send txbf frames to the host (driver) if the TXBF (0xF00000001) set-special feature is enabled, or when the radio is in monitor mode. But, if the frame is consumed by the txbf_cv logic, then the pkt cannot be delivered to the host in this manner. Instead, a WMI event will be sent and host can find the txbf_cv data in shared memory. See ath10k_wmi_event_txbf_cv_mesg() in ath10k-ct driver. * Support rx-all-mgt option. When enabled, the firmware will deliver all management frames that it can to the host. No RX filters are changed when this option is enabled. * Fix at least some problems with sending tx-beamforming frames to SU-MIMO peers. Looks like this was a regression in my code. * Fix a crash in rate-ctrl due to nss mismatch. This was something I introduced while trying to fix other bugs in rate-ctrl some time back. * Attempt to fix a sw-peer-key object leak in IBSS mode. The peer key code is very complex, and shares some pointers as union members. I think I fixed at least some of the issues, but would not be surprised if more exist. * Improve ath10k user guide to document CT firmware features: https://www.candelatech.com/ath10k-ug.php * Add ct-special option to configure the txbf sounding time. See ath10k-ug.php * Fix and allow the driver to tell the firmware to send sounding frames. See ath10k-ug.php In further testing, this seems to fail much of the time, and I am not sure why. Disabling this in diet (trimmed) builds. * Fix crashes related to deleting peers while they are in power-save mode. Reported by LEDE user on r7800 with 9984 NIC. * Make rate-ctrl txbf probe work better. If enabled, the rate-ctrl logic will periodically send out probes at an NSS that can to txbf. Previously, txbf probes would not reliably happen if both AP and peer had the same nss (ie, 2x2 talking to 2x2). To enable this feature, you need to enable the fwtest-cmdid number 20. * Report rx-timeout error counters. These were previously un-reported, though the field existed in the wmi struct already. * txbf: Ignore frames not destined for us. If NIC is in promisc mode, it could acquire and process NDPA frames that were not destined for it. Check the dest-MAC and ignore frames not for us (pass them up the stack for monitor mode instead of save them in the peer's rate-ctrl logic.) * Port ping-pong crash handling and othe related features to IPQ4019 target. It should now act similar to 9984 in this regard. * Fix a few asserts related to txbf and tx-seq logic. * Add custom-stats support, for rx-reorder-stats. Similar to what I did for wave-1. * Disable AMSDU for IBSS. This now matches what I did for peregrine. It seems to work better this way, though I did not debug it in detail. * Enable the set-special command to re-enable AMSDU for IBSS if user wants to experiment. * Fix bug where dbglog did not disable IRQs, so if you made dbglog messages from the IRQ handler, it could cause corruption that could crash the firmware and/or corrupt the log message buffers. * Don't assert if there are no buffer descriptors for RX of non-data frame. * Retry any stuck block-ack sessions every 20 seconds instead of just disabling BA for ever when we get too many failures. * Fix SGI flag when reporting tx-rate info. The flag moved since wave-1 days, and I did not notice that when I ported my changes forward to wave-2. * Allow disabling special CCA handling for IBSS txqs. Earlier testing indicated this might improve throughput in some testing on 9984 chips in IBSS mode, but subsequent testing looks about the same without it. Since I do not really understand what this setting exists for, leave it at upstream defaults. A new set-special API command (0x12) can be used to enable this hack for testing. Setting 0x1 bit disables special CCA handling for non-beacon IBSS txqs, setting 0x2 bit disables it for beacon queues as well. * Add MCAST-BCAST feature flag. This tells driver we do not need a monitor interface to do MESH. * When calculating the rx-address filter (affects ACK & BLOCK-ACK, among other things), to not add in monitor interfaces if other interfaces are up. There is no need for a monitor device to ACK frames. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-ct: Update DEPENDS and PROVIDESBen Greear2018-03-231-0/+8
| | | | | | | | | | Update DEPENDS and PROVIDES so that ath10k-ct firmware and drivers can be used to replace stock firmware and drivers. The -htt firmware variant, which requires ath10k-ct driver now selects ath10k-ct driver when the firmware is selected. Signed-off-by: Ben Greear <greearb@candelatech.com>
* ath10k-firmware: Support CT IPQ4019 firmware.Ben Greear2018-03-221-3/+71
| | | | | | | Initial beta release of the CT IPQ4019 firmware. Features are similar to the CT 9984 firmware Signed-off-by: Ben Greear <greearb@candelatech.com>
* intel-microcode: update to 20180312Zoltan HERPAI2018-03-211-3/+3
| | | | | | | | | | | | | | | | - Update microcode for 24 CPU types - Implements IBRS/IBPB/STIPB support, Spectre-v2 mitigation for: Sandybridge, Ivy Bridge, Haswell, Broadwell, Skylake, Kaby Lake, Coffee Lake - Missing production updates: - Broadwell-E/EX Xeons (sig 0x406f1) - Anniedale/Morefield, Apollo Lake, Avoton, Cherry Trail, Braswell, Gemini Lake, Denverton - New Microcodes: - sig 0x00050653, pf_mask 0x97, 2018-01-29, rev 0x1000140 - sig 0x00050665, pf_mask 0x10, 2018-01-22, rev 0xe000009 Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* ipq-wifi: add board-2.bin for ASUS RT-AC58UMathias Kresin2018-03-151-0/+0
| | | | | | | The existing file is 0 byte. Replace the ASUS RT-AC58U board-2.bin with the correct file. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ipq40xx: add Cisco Meraki MR33 SupportChris Blake2018-03-142-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for Cisco Meraki MR33 hardware highlights: SOC: IPQ4029 Quad-Core ARMv7 Processor rev 5 (v7l) Cortex-A7 DRAM: 256 MiB DDR3L-1600 @ 627 MHz Micron MT41K128M16JT-125IT NAND: 128 MiB SLC NAND Spansion S34ML01G200TFV00 (106 MiB usable) ETH: Qualcomm Atheros AR8035 Gigabit PHY (1 x LAN/WAN) + PoE WLAN1: QCA9887 (168c:0050) PCIe 1x1:1 802.11abgn ac Dualband VHT80 WLAN2: Qualcomm Atheros QCA4029 2.4GHz 802.11bgn 2:2x2 WLAN3: Qualcomm Atheros QCA4029 5GHz 802.11a/n/ac 2:2x2 VHT80 LEDS: 1 x Programmable RGB+White Status LED (driven by Ti LP5562 on i2c-1) 1 x Orange LED Fault Indicator (shared with LP5562) 2 x LAN Activity / Speed LEDs (On the RJ45 Port) BUTTON: one Reset button MISC: Bluetooth LE Ti cc2650 PG2.3 4x4mm - BL_CONFIG at 0x0001FFD8 AT24C64 8KiB EEPROM Kensington Lock Serial: WARNING: The serial port needs a TTL/RS-232 3V3 level converter! The Serial setting is 115200-8-N-1. The board has a populated 1x4 0.1" header with half-height/low profile pins. The pinout is: VCC (little white arrow), RX, TX, GND. Flashing needs a serial adaptor, as well as patched ubootwrite utility (needs Little-Endian support). And a modified u-boot (enabled Ethernet). Meraki's original u-boot source can be found in: <https://github.com/riptidewave93/meraki-uboot/tree/mr33-20170427> Add images to do an installation via bootloader: 0. open up the MR33 and connect the serial console. 1. start the 2nd stage bootloader transfer from client pc: # ubootwrite.py --write=mr33-uboot.bin (The ubootwrite tool will interrupt the boot-process and hence it needs to listen for cues. If the connection is bad (due to the low-profile pins), the tool can fail multiple times and in weird ways. If you are not sure, just use a terminal program and see what the device is doing there. 2. power on the MR33 (with ethernet + serial cables attached) Warning: Make sure you do this in a private LAN that has no connection to the internet. - let it upload the u-boot this can take 250-300 seconds - 3. use a tftp client (in binary mode!) on your PC to upload the sysupgrade.bin (the u-boot is listening on 192.168.1.1) # tftp 192.168.1.1 binary put openwrt-ipq40xx-meraki_mr33-squashfs-sysupgrade.bin 4. wait for it to reboot 5. connect to your MR33 via ssh on 192.168.1.1 For more detailed instructions, please take a look at the: "Flashing Instructions for the MR33" PDF. This can be found on the wiki: <https://openwrt.org/toh/meraki/mr33> (A link to the mr33-uboot.bin + the modified ubootwrite is also there) Thanks to Jerome C. for sending an MR33 to Chris. Signed-off-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: add support for ASUS RT-AC58U/RT-ACRH13Christian Lamparter2018-03-142-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for ASUS RT-AC58U/RT-ACRH13. hardware highlights: SOC: IPQ4018 / QCA Dakota CPU: Quad-Core ARMv7 Processor rev 5 (v7l) Cortex-A7 DRAM: 128 MiB DDR3L-1066 @ 537 MHz (1074?) NT5CC64M16GP-DI NOR: 2 MiB Macronix MX25L1606E (for boot, QSEE) NAND: 128 MiB Winbond W25NO1GVZE1G (cal + kernel + root, UBI) ETH: Qualcomm Atheros QCA8075 Gigabit Switch (4 x LAN, 1 x WAN) USB: 1 x 3.0 (via Synopsys DesignWare DWC3 controller in the SoC) WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11bgn 2:2x2 WLAN2: Qualcomm Atheros QCA4018 5GHz 802.11a/n/ac 2:2x2 INPUT: one Reset and one WPS button LEDS: Status, WAN, WIFI1/2, USB and LAN (one blue LED for each) Serial: WARNING: The serial port needs a TTL/RS-232 3V3 level converter! The Serial setting is 115200-8-N-1. The board has an unpopulated 1x4 0.1" header. The pinout (VDD, RX, GND, TX) is printed on the PCB right next to the connector. U-Boot Note: The ethernet driver isn't always reliable and can sometime time out... Don't worry, just retry. Access via the serial console is required. As well as a working TFTP-server setup and the initramfs image. (If not provided, it has to be built from the OpenWrt source. Make sure to enable LZMA as the compression for the INITRAMFS!) To install the image permanently, you have to do the following steps in the listed order. 1. Open up the router. There are four phillips screws hiding behind the four plastic feets on the underside. 2. Connect the serial cable (See notes above) 3. Connect your router via one of the four LAN-ports (yellow) to a PC which can set the IP-Address and ssh and scp from. If possible set your PC's IPv4 Address to 192.168.1.70 (As this is the IP-Address the Router's bootloader expects for the tftp server) 4. power up the router and enter the u-boot choose option 1 to upload the initramfs image. And follow through the ipv4 setup. Wait for your router's status LED to stop blinking rapidly and glow just blue. (The LAN LED should also be glowing blue). 3. Connect to the OpenWrt running in RAM The default IPv4-Address of your router will be 192.168.1.1. 1. Copy over the openwrt-sysupgrade.bin image to your router's temporary directory # scp openwrt-sysupgrade.bin root@192.168.1.1:/tmp 2. ssh from your PC into your router as root. # ssh root@192.168.1.1 The default OpenWrt-Image won't ask for a password. Simply hit the Enter-Key. Once connected...: run the following commands on your temporary installation 3. delete the "jffs2" ubi partition to make room for your new root partition # ubirmvol /dev/ubi0 --name=jffs2 4. install OpenWrt on the NAND Flash. # sysupgrade -v /tmp/openwrt-sysupgrade.bin - This will will automatically reboot the router - Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: add targetJohn Crispin2018-03-141-1/+1
| | | | | | Signed-off-by: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: John Crispin <john@phrozen.org>
* firmware: ath10k-firmware: update QCA9984 firmware to 10.4-3.5.3-00053Henryk Heisig2018-03-091-1/+1
| | | | | | | | | | | | | | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.4-3.5.3-00053 firmware for the QCA9984. The update fixes "ath10k_pci 0001:01:00.0: Invalid VHT mcs 15 peer stats" spamming the kernel ring buffer at very high frequencies, but introduces the new "ath10k_pci 0001:01:00.0: Unknown eventid: 36925". This new warning doesn't appear to cause problems in practice and is only emitted relatively rarely, not causing dmesg to overflow within minutes. Tested on the ZyXEL NBG6817; early feedback also suggests this firmware to work well (with the same fixes and caveats) on the Netgear r7800 as well. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* firmware: ath10k-firmware: update to 2018-02-09Henryk Heisig2018-03-091-4/+4
| | | | | | | This patch updates ath10k-firmware to last commit and use the firmware-5.bin_10.4-3.5.3-00053 firmware for the QCA9888. Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* linux-firmware: bump firmware for Intel Wireless 8260AC to version 31Stijn Segers2018-03-091-1/+1
| | | | | | Bump the firmware for 8260AC and related hardware to version 31. Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* ipq806x: add support for GL.iNet GL-B1300Dongming Han2018-02-142-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for GL.iNet GL-B1300 Specification: - SOC: IPQ4028 / QCA Dakota - RAM: 256 MiB - FLASH: 32 MiB - ETH: Qualcomm Atheros QCA8075 Gigabit Switch (2 x LAN, 1 x WAN) - USB: 1 x 3.0 (via Synopsys DesignWare DWC3 controller in the SoC) - WLAN1: Qualcomm Atheros QCA4028 2.4GHz 802.11bgn 2:2x2 - WLAN2: Qualcomm Atheros QCA4028 5GHz 802.11a/n/ac 2:2x2 - INPUT: one reset and one WPS button - LEDS: 3 leds: Power, WIFI(only for 2.4G currently), and one reserved - UART: 1 x UART on PCB (3.3V, TX, RX, GND) - 115200 8N1 Installation: Method 1: - use serial port to stop uboot - uboot command: run lf Method 2: - push down reset button and power on - wait until three leds constantly on then release - upgrade by uboot web at http://192.168.1.1 Note: - the sysupgrade image need to be renamed to lede-gl-b1300.bin in both method. - the sysupgrade image can be automatically downloaded if tftp server at 192.168.1.2 have that file. - the wifi led will be flashing when writing image. Signed-off-by: Dongming Han <handongming@gl-inet.com>
* layerscape: update ppfe firmware to LSDK1712Yangbo Lu2018-02-131-5/+5
| | | | | | | | Updated ppfe firmware to NXP LSDK1712 release. Used ppfe firmware git tree on NXP github since it was migrated here from qoriq-open-source github. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add ls-rcw-bin packageYangbo Lu2018-02-132-28/+103
| | | | | | | | | | | | NXP LSDK1712 release used two rcw git trees. The original rcw git tree was still source code but dropping ls1012a/ls1088a/ls2088a boards in LSDK1712. Instead another new rcw git tree was used to just provided rcw binaries for these boards dropped. So this patch is to update ls-rcw to LSDK1712 release and add a new ls-rcw-bin package. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update PPA firmware to LSDK1712Yangbo Lu2018-02-131-3/+3
| | | | | | | This patch is to update PPA firmware to NXP LSDK1712 release. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: migrate fman-ucode to NXP githubYangbo Lu2018-02-131-1/+1
| | | | | | | | fman-ucode had been migrated from qoriq-open-source github to NXP github. So the Makefile should be fixed accordingly. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update MC firmware to LSDK1712Yangbo Lu2018-02-131-6/+6
| | | | | | | | Updated MC firmware to NXP LSDK1712 release. Used MC firmware git tree on NXP github since it was migrated here from qoriq-open-source github. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* ipq-wifi: drop OpenMesh A42 board-2.binSven Eckelmann2018-02-112-2/+1
| | | | | | | | | | | The BDFs for OpenMesh A42 were upstreamed [1] to the ath10k-firmware repository and are now part of ath10k-firmware 2018-01-26. The ipq-wifi-openmesh_a42 package can now be dropped because OpenWrt already ships the QCA4019 board-2.bin from this version. [1] https://wireless.wiki.kernel.org/en/users/drivers/ath10k/boardfiles Signed-off-by: Sven Eckelmann <sven.eckelmann@open-mesh.com>
* firmware: ath10k-firmware: update to 2018-01-26Sven Eckelmann2018-02-111-3/+3
| | | | | | | | | * introduces the BDFs for the OpenMesh A42 in /lib/firmware/ath10k/QCA4019/hw1.0/board-2.bin. * adds new firmware firmware-6.bin_RM.4.4.1.c1-00037-QCARMSWP-1 for QCA6174 hw3.0 Signed-off-by: Sven Eckelmann <sven.eckelmann@open-mesh.com>
* firmware: add microcode package for IntelZoltan HERPAI2018-02-111-0/+49
| | | | | | | | | | | | | | | | Compiling the Intel microcode package results in a microcode.bin and a microcode-64.bin. As we can decide based on the subtarget which should be used, we'll only split the required .bin file with iucode-tool. x64 will get the intel-microcode-64.bin All other variants will get intel-microcode.bin The microcodes will be updated from preinit via a common script - that's the earliest place where we can do it. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* firmware: add microcode package for AMDZoltan HERPAI2018-02-111-0/+45
| | | | | | | | | | | Use the Debian repository for sourcing the ucode files. Current (20171205) includes support for fam17h CPUs already. The microcodes will be updated from preinit via a common script - that's the earliest place where we can do it. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* ipq-wifi: align AVM FRITZ!Box 4040's board-2.bin packageChristian Lamparter2018-01-182-2/+2
| | | | | | | This patch renames the AVM FRITZ!Box 4040's board-2.bin file and package to match the 'vendor_product' format. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA988x firmware to 10.2.4-1.0-00033Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.2.4-1.0-00033 firmware for the QCA988x. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA9887 firmware to 10.2.4-1.0-00033Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.2.4-1.0-00033 firmware for the QCA9887. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA9888 firmware to 10.4-3.4-00104Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.4-3.4-00104 firmware for the QCA9888. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* firmware: ath10k-firmware: update QCA9984 firmware to 10.4-3.4-00104Christian Lamparter2018-01-181-1/+1
| | | | | | | This patch updates ath10k-firmware to use the firmware-5.bin_10.4-3.4-00104 firmware for the QCA9984. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-26 03:52:29 +0000