aboutsummaryrefslogtreecommitdiffstats
path: root/package/firmware
Commit message (Collapse)AuthorAgeFilesLines
* Revert "intel-microcode: create early load microcode image"John Crispin2018-11-271-8/+6
| | | | | | This reverts commit 022ffb56b2491fd7d8051ac6e6c7622ecc313d8f. Signed-off-by: John Crispin <john@phrozen.org>
* Revert "amd64-microcode: create early load microcode image"John Crispin2018-11-271-8/+2
| | | | | | This reverts commit 975019b3a755ec3b91864b60b45e5ee104075096. Signed-off-by: John Crispin <john@phrozen.org>
* amd64-microcode: create early load microcode imageTomasz Maciej Nowak2018-11-261-2/+8
| | | | | | | Create initrd image with packed microcode. This'll allow to load it at early boot stage. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* intel-microcode: create early load microcode imageTomasz Maciej Nowak2018-11-261-6/+8
| | | | | | | Create initrd image with packed microcode. This'll allow to load it at early boot stage. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* intel-microcode: remove dependency on iucode-toolTomasz Maciej Nowak2018-11-261-1/+1
| | | | | | | It is not necessary to have iucode-tool present on target system to have functional intel-microcode package. The build time dependency is kept. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* ipq-wifi: drop custom board-2.binsChristian Lamparter2018-11-013-3/+1
| | | | | | | | | | | | | The BDFs for all boards were upstreamed to the ath10k-firmware repository and linux-firmware.git. 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: Christian Lamparter <chunkeey@gmail.com>
* ath10k-firmware: update board-2.bin for community firmwaresChristian Lamparter2018-11-011-3/+3
| | | | | | | | This patch updates the board-2.bin for the default IPQ4019, QCA9984 and QCA9888 ath10k-firmware-xyz-ct and -ct-htt firmwares. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* linux-firmware: intel: Add iwl 9000 and 9260 firmwareHauke Mehrtens2018-10-201-0/+14
| | | | | | | Add the most recent supported firmware file for the Intel 9000 and 9260 wireless chips. The API version 41 is not yet supported by the driver. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* linux-firmware: intel: update firmware files for 7265D, 8000C and 8265Hauke Mehrtens2018-10-201-3/+3
| | | | | | Use more recent versions for the Intel wireless chips 7265D, 8000C and 8265. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* linux-firmware: Update linux-firmware to 2018-10-18Robert Marko2018-10-201-4/+4
| | | | | | | | | | | | | | | Kalles ath10k PR was finally merged so update linux-firmware to include those changes. This is needed since disabling ath10k-firmware a lot of custom BDF-s in board-2.bin-s are not available in previously outdated linux-firmware board-2.bin-s. This also includes support for boards currently using ipq-wifi and other WIP ones. Runtime tested on 8devices Jalapeno. Signed-off-by: Robert Marko <robimarko@gmail.com>
* intel-microcode: update to version 20180807aHauke Mehrtens2018-10-071-3/+3
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* linux-firmware: set PKG_MIRROR_HASHDaniel Golle2018-09-261-1/+1
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* linux-firmware: add ath10k supportJohn Crispin2018-09-262-4/+109
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ath10k-firmware: disable the package and use default linux-firmware packageJohn Crispin2018-09-261-7/+7
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* layerscape: build ls-dpl package with linux dtc toolYangbo Lu2018-09-221-0/+3
| | | | | | | | | Building ls-dpl package requires the dtc tool. This patch is to support using linux dtc tool for ls-dpl package. This avoids compile issue when host system doesn't have the dtc tool. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add ls1012afrwy support and drop ls1012afrdmYangbo Lu2018-09-222-7/+7
| | | | | | | | | | | | | | | | | | | | | | | ls1012afrdm was no longer supported in NXP Layerscape SDK. Instead a new board ls1012afrwy was introduced in LSDK. This patch is to drop ls1012afrdm and add ls1012afrwy support. Since only 2MB NOR flash could be used, we just put u-boot and firmware on NOR flash, and put kernel/dtb/rootfs on SD card. The Layerscape FRWY-LS1012A board is an ultra-low-cost development platform for LS1012A Series Communication Processors built on Arm Cortex-A53. This tool refines the FRDM-LS1012A with more features for a better hands-on experience for IoT, edge computing, and various advanced embedded applications. Features include easy access to processor I/O, low-power operation, micro SD card storage, an M2 connector, a small form factor, and expansion board options via mikroBUS Click Module. The MicroBUS Module provides easy expansion via hundreds of powerful modules supporting sensors, actuators, memories, and displays. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add SD card boot supportYangbo Lu2018-09-221-0/+6
| | | | | | | | | NOR/QSPI Flash on Layerscape board only has limited 64MB memory size. Since some boards (ls1043ardb/ls1046ardb/ls1088ardb/ls1021atwr) could support SD card boot, we added SD boot support for them to put all things on SD card to meet large memory requirement. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add armv7 subtarget and ls1021atwr board supportYangbo Lu2018-09-221-1/+7
| | | | | | | | | | | | | | | | | | The NXP TWR-LS1021A module is a development system based on the QorIQ LS1021A processor. - This feature-rich, high-performance processor module can be used standalone or as part of an assembled Tower System development platform. - Incorporating dual Arm Cortex-A7 cores running up to 1 GHz, the TWR-LS1021A delivers an outstanding level of performance. - The TWR-LS1021A offers HDMI, SATA3 and USB3 connectors as well as a complete Linux software developer's package. - The module provides a comprehensive level of security that includes support for secure boot, Trust Architecture and tamper detection in both standby and active power modes, safeguarding the device from manufacture to deployment. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ls-ppa to LSDK-18.06Yangbo Lu2018-09-221-73/+46
| | | | | | | This patch is to update ls-ppa to LSDK-18.06 release and to rework ls-ppa makefile to make it more readable. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ls-rcw to LSDK-18.06Yangbo Lu2018-09-223-175/+81
| | | | | | | | | | | | The rcw source code had been migrated to codeaurora for LSDK-18.06 release and the future release. The source code had also involved ls1012ardb/ls1012afrdm/ ls1088ardb/ls2088ardb rcw, so we updated ls-rcw to LSDK-18.06, reworked the makefile and dropped ls-rcw-bin package in this patch. Also reworked ls-rcw patch to adapt to the latest source code. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ppfe-firmware to LSDK-18.06Yangbo Lu2018-09-221-6/+4
| | | | | | This patch is to update ppfe-firmware to LSDK-18.06 release. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ls-mc to LSDK-18.06Yangbo Lu2018-09-221-13/+7
| | | | | | This patch is to update ls-mc to LSDK-18.06 release. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ls-dpl to LSDK-18.06Yangbo Lu2018-09-221-16/+12
| | | | | | | | | The dpl-examples source code had been migrated to codeaurora for LSDK-18.06 release and the future release. This patch is to update this package to LSDK-18.06. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update fman-ucode to LSDK-18.06Yangbo Lu2018-09-221-59/+21
| | | | | | | | | Actually there was no change for fman-ucode in LSDK-18.06 just tagged with LSDK-18.06. This patch is to rework the fman-ucode makefile to make it more readable, and to use lsdk-1806 as the PKG_VERSION. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* linux-firmware: realtek: Add FW for rtl8192eu, rtl8723au and rtl8723buHauke Mehrtens2018-08-271-0/+23
| | | | | | | These devices are more or less supported by the kmod-rtl8xxxu driver. Fixes: FS#1789 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath10k-firmware: update both QCA988X CT variantsStijn Tintel2018-08-261-4/+4
| | | | | | This fixes slow performance with 802.11w enabled. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* 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>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-29 02:38:42 +0000