aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* base-files: prevent issues w/ overlay on powerloss after sysupgradeSergey Ryazanov2020-06-032-1/+3
| | | | | | | | | | | | | | | | Due to filesystem write caching the old configuration data could stay out of flash for a long time during a first boot after the sysupgrade. Power loss during this period could damage the overlay data and even make device inaccessable via the network. Fix this by syncing data to a flash as soon as the previous configuration will be unpacked after the sysupgrade. Also sync the FS state after the sysupgrade.tgz archive removing to prevent duplicative extraction of a previous configuration. Tested with AMD Geode based board. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* dnsmasq: add /etc/dnsmasq.d/ to conffilesSven Roederer2020-06-031-1/+2
| | | | | | This directory can hold configuration-snippets which should also included in the backup. Signed-off-by: Sven Roederer <devel-sven@geroedel.de>
* mvebu: espressobin: fix SATA and USB 3.0 ports detectionTomasz Maciej Nowak2020-06-031-0/+53
| | | | | | | | | | | | | | | | | This commit removes changes from upstream commits: 8e18c8e58da6 arm64: dts: marvell: armada-3720-espressobin: declare SATA PHY property bd3d25b07342 arm64: dts: marvell: armada-37xx: link USB hosts with their PHYs For most boards which have factory bootloader this caused that devices connected to USB 3.0 and SATA port were not detected. For them to function users would need to upgrade the bootloader to version with ARM Trusted Firmware 2.1 or later. Unfortunately there is no official bootloader image with updated ATF component, therefore drop these properties from nodes. This change was also tested briefly with bootloader with updated ATF and the ports functioned properly. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* uboot-mxs: bump to v2020.04Michael Heimpold2020-06-032-34/+36
| | | | | | Also update the U-Boot BSP patch for I2SE Duckbill devices. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* ipq806x: enable disk-activity LED triggerThomas Albers2020-06-032-0/+2
| | | | | | | | | Enable the disk-activity LED trigger for ipq806x, since this SoC has an onboard SATA controller. Signed-off-by: Thomas Albers <thomas.gameiro@googlemail.com> [split into separate commit] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* base-files: fix LED IDE triggerThomas Albers2020-06-031-1/+1
| | | | | | | | | | This changes the ide-disk LED trigger to the generic disk-activity as ide-disk trigger was removed in upstream commit eb25cb9956cc ("leds: convert IDE trigger to common disk trigger"). Signed-off-by: Thomas Albers <thomas.gameiro@googlemail.com> [split into separate commit, commit description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* linux/generic: remove obsolete config option LEDS_TRIGGER_IDE_DISKThomas Albers2020-06-033-3/+0
| | | | | | | | | | | | | Kernel config option LEDS_TRIGGER_IDE_DISK was renamed in kernel 4.8 to CONFIG_LEDS_TRIGGER_DISK in upstream commit eb25cb9956cc ("leds: convert IDE trigger to common disk trigger"). Removing it as it should be added only on targets which has usage for this trigger. Signed-off-by: Thomas Albers <thomas.gameiro@googlemail.com> [commit description facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build, imagebuilder: Do not require libncurses-devPaul Spooren2020-06-031-0/+2
| | | | | | | | | | The buildroot and SDK both require `libncurses-dev` to be installed on the system, however the ImageBuilder uses precompiled binaries. This patch changes the prerequirements checks to skip the `libncurses-dev` part if running as ImageBuilder. Signed-off-by: Paul Spooren <mail@aparcar.org>
* ramips: add kmod-usb-dwc2 to ZyXEL Keenetic imageAlexey Dobrovolsky2020-06-031-1/+2
| | | | | | | | | | ZyXEL Keenetic has a USB port. Thus, DWC2 USB controller driver should be in the default image for this device. Fixes: a7cbf59e0e04 ("ramips: add new device ZyXEL Keenetic as kn") Signed-off-by: Alexey Dobrovolsky <dobrovolskiy.alexey@gmail.com> [fixed whitespace issue] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: remove patches for USB-dwc2Alexey Dobrovolsky2020-06-032-58/+0
| | | | | | | | | | | | | | In FS#2738 we can see that patch first introduced in e8ebcff ("ramips: add a explicit reset to dwc2") breaks USB functionality since 18.06. Thus, this patch should be removed. Removed: - 0032-USB-dwc2-add-device_reset.patch Fixes: FS#2738 Fixes: FS#2964 Signed-off-by: Alexey Dobrovolsky <dobrovolskiy.alexey@gmail.com>
* prereq-build: test for perl's Data::DumperRosen Penev2020-06-031-0/+4
| | | | | | | | | | | | | | | | | | | | | | Required for installation of autoconf: make[5]: Entering directory `/openwrt/build_dir/host/autoconf-2.69' Making all in bin make[6]: Entering directory `/openwrt/build_dir/host/autoconf-2.69/bin' autom4te_perllibdir='..'/lib AUTOM4TE_CFG='../lib/autom4te.cfg' ../bin/autom4te -B '..'/lib -B '..'/lib --language M4sh --cache '' --melt ./autoconf.as -o autoconf.in Can't locate Data/Dumper.pm in @INC (@INC contains: ../lib /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at ../lib/Autom4te/C4che.pm line 33. BEGIN failed--compilation aborted at ../lib/Autom4te/C4che.pm line 33. Compilation failed in require at ../bin/autom4te line 40. BEGIN failed--compilation aborted at ../bin/autom4te line 40. make[6]: *** [autoconf.in] Error 2 Signed-off-by: Rosen Penev <rosenp@gmail.com>
* apm821xx: set DEVICE_TYPE to "nas" for sata subtargetAdrian Schmutzler2020-06-031-0/+1
| | | | | | | | | | | | | | | | Since DEVICE_TYPE cannot be set per device, just set DEVICE_TYPE to "nas" for the entire subtarget, which only contains this single device. Note that while this looks like a cosmetic change in combination with the previous patches, this particular patch actually changes the packages for the device. Suggested-by: Christian Lamparter <chunkeey@gmail.com> Cc: Christian Lamparter <chunkeey@gmail.com> Cc: Sungbo Eo <mans0n@gorani.run> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: provide consistent basic DEVICE_TYPEAdrian Schmutzler2020-06-033-3/+4
| | | | | | | | | | | | | | | | | | | | | While the effective "default" based on frequent use is "router", the DEVICE_TYPE variable actually provides a "basic" configuration without selecting any additional packages. This is currently set up with the identifier "bootloader", which seems to be not used at all. However, the only targets not using "router" or "nas" are actually archs38 and arc770, which use their own value "developerboard" for DEVICE_TYPE which seems to have been invented when these targets where added. The latter is not implemented in target.mk, though, and will fall back to the "basic" set of packages then. So, to clean this up and make it more readable, let's just define a DEVICE_TYPE "basic" and use it for the aforementioned cases. Cc: Christian Lamparter <chunkeey@gmail.com> Cc: Sungbo Eo <mans0n@gorani.run> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: drop DEVICE_TYPE when used as device variableAdrian Schmutzler2020-06-033-4/+0
| | | | | | | | | | | | | | | | | | | | | | | DEVICE_TYPE is a target/subtarget variable, and it does not have any effect when set in a device definition. It can only be set in a target's or subtarget's Makefile. Consequently, having it set anyway is misleading, so this drops all cases. This effectively reverts the following commits: 7a1497fd601d ("apm821xx: MBL: set DEVICE_TYPE to NAS") 5b4765c93a1b ("gemini: Classify Raidsonic NAS IB-4220-B as a NAS") cdc6de460bb4 ("gemini: D-Link DNS-313 is a NAS") For the following commit, the variable was set when adding device support: 27b2f0fc0fc5 ("kirkwood: add support for Iomega Storcenter ix2-200") Cc: Christian Lamparter <chunkeey@gmail.com> Cc: Sungbo Eo <mans0n@gorani.run> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: lzma-loader: allow bigger ramdisksÁlvaro Fernández Rojas2020-06-032-4/+6
| | | | | | | | | | | | | | | | Some (older) CFEs are loaded at 0x80401000 and ramdisks are loaded at 0x80010000, which means that ramdisk size limit is 0x3F1000 (almost 4M). Therefore, current ramdisks (~4MB) are overwritting CFE in these devices, which results in a crash. This commit changes the address where ramdisks are loaded to 0x80a00000, which is the same address where kernel is loaded when booting from the flash. Therefore, lzma-loader will now be loaded at 0x80a00000, but it will still decompress the kernel at 0x80010000. Tested with huawei,hg556a-b, which has its CFE loaded at 0x80401000. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* uhttpd: fix script timeoutDaniel Golle2020-06-031-3/+3
| | | | | | 939c281 proc: do not cancel script killing after writing headers Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* malta: add missing symbols for kernel 5.4Daniel Golle2020-06-031-0/+2
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* bcm63xx: ad1018: remove cfe.bin image supportÁlvaro Fernández Rojas2020-06-032-27/+1
| | | | | | | | | | | | Apparently, Sercomm allows loading a BCM WFI image via CFE, but this image destroys "serial" and "protect" nand partitions, which is wrong. It will also set both bootflags to the same value, which causes booting issues with cferam (cferom will alternatively boot from cferam1 or cferam2 each time the device is rebooted). Now that OEM Sercomm images are supported it's time to remove this hacky cfe.bin image support. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: ad1018: add missing partitionsÁlvaro Fernández Rojas2020-06-031-0/+12
| | | | | | This partitions were missing when support for this device was added. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: stop using legacy lzma for all devicesÁlvaro Fernández Rojas2020-06-031-54/+59
| | | | | | | | | BCM6368 and newer devices are compatible with any lzma compression parameters. Add a new legacy device definition and use it on BCM6358 and older devices. Compressed kernel size is reduced by ~1.35%. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: vg-8050: switch to bcm-wfi-splitÁlvaro Fernández Rojas2020-06-022-6/+6
| | | | | | | Allows to keep a backup firmware in case active firmware is corrupted. Also fix hsspi address warning. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: vr-3032u: switch to bcm-wfi-splitÁlvaro Fernández Rojas2020-06-022-3/+3
| | | | | | Allows to keep a backup firmware in case active firmware is corrupted. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: order devices alphabeticallyÁlvaro Fernández Rojas2020-06-021-10/+10
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: add CFE_WFI_VERSION values for each deviceÁlvaro Fernández Rojas2020-06-021-1/+5
| | | | | | CFE_WFI_VERSION should be defined per device instead of using a generic value. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: mtdsplit: support Broadcom WFI bootflagsÁlvaro Fernández Rojas2020-06-021-0/+110
| | | | | | | | When firmware is flashed, cferam.000 extension is renamed to the next number. When booting, CFE scans the NAND and picks the partition with the highest cferam extension and ignores the other one. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: mtdsplit: improve JFFS2 scanÁlvaro Fernández Rojas2020-06-021-6/+20
| | | | | | Allow retrieving full file name and length by parameters. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: mtdsplit: bcm_wfi: refactor codeÁlvaro Fernández Rojas2020-06-021-82/+69
| | | | | | Create new parse_bcm_wfi function with common code from current parsers. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* scripts: config: remove accidentally added fileÁlvaro Fernández Rojas2020-06-022-0/+1
| | | | | | Also ignore the file. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: bump 5.4 to 5.4.43Petr Štetiar2020-06-029-57/+11
| | | | | | | | | | | Refreshed patches, removed upstreamed patch: bcm27xx: 950-0642-component-Silence-bind-error-on-EPROBE_DEFER.patch Run tested: qemu-x86-64 Build tested: x86/64, imx6, sunxi/a53 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* bcm63xx: nand: sercomm: switch to sercomm-load scriptÁlvaro Fernández Rojas2020-06-021-5/+6
| | | | | | | xxd is not a valid dependency and shouldn't be used. Fixes buildbot failure. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* scripts: support Sercomm load tagsÁlvaro Fernández Rojas2020-06-022-0/+56
| | | | | | | Header consists in Sercomm PID bytes, followed by a SHA256 hash of the input binary. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: ad1018: support Sercomm factory imagesÁlvaro Fernández Rojas2020-06-021-1/+11
| | | | | | | This images can be flashed from the official firmware, as opposed to CFE images, which can only be flashed from CFE and require opening the case. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: nand: support Sercomm firmwaresÁlvaro Fernández Rojas2020-06-022-0/+67
| | | | | | Add support for Sercomm factory firmwares (AES 256 CBC encrypted). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: mtdsplit: bcm_wfi: remove brcm,wfi-sercomm compatibilityÁlvaro Fernández Rojas2020-06-021-2/+1
| | | | | | | The only Sercomm WFI user has been migrated to a dedicated firmware parser. Keep support for no cferam partition based on a boolean DT property. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: ad1018: switch to Sercomm WFIÁlvaro Fernández Rojas2020-06-022-9/+6
| | | | | | | | Support Sercomm firmware partition split. WFI partition must be defined after bootflag partitions in order for the parser to properly find bootflag1 and bootflag2 partitions. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: mtdsplit: bcm_wfi: support Sercomm bootflagsÁlvaro Fernández Rojas2020-06-021-0/+148
| | | | | | | | Sercomm uses 2 bootflag partitions and boots the firmware with the highest bootflag. Support splitting the firmware partition while keeping support for unsplitted layout. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: mtdsplit: bcm_wfi: code refactoringÁlvaro Fernández Rojas2020-06-021-15/+18
| | | | | | | | - Rename master to mtd. - Pass mtd size as an argument. - Rename of_match_table. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* scripts: support Sercomm cryptoÁlvaro Fernández Rojas2020-06-021-0/+86
| | | | | | | | | | | | | | Sercomm firmwares are encrypted with AES 256 CBC. The key is generated with a custom algorithm from the firmware tag: char key[32]; char version[32]; char iv[32]; char random[32]; char size[32]; Key must be generated with Sercomm's algorithm. However, the rest of the header can be empty. IV and random are set to 0 on purpose. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* scripts: support Sercomm partition tagsÁlvaro Fernández Rojas2020-06-021-0/+81
| | | | | | | | | | | Sercomm uses a custom layout for partition tags: char part_name[32]; char size[32]; char part_version[32]; char reserved[32]; char rootfs_version[32]; Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ppp: update to version 2.4.8.git-2020-05-25Hans Dedecker2020-05-3111-170/+20
| | | | | | | | | | | | | | ddd57c2 pppd: Add lcp-echo-adaptive option c319558 pppd: Handle SIGINT and SIGTERM during interrupted syscalls (#148) 0bc11fb Added missing options to manual pages. (#149) b1fcf16 Merge branch 'monotonic-time' of https://github.com/themiron/ppp c78e312 pppd: linux: use monotonic time if possible Remove patch 121-debian_adaptive_lcp_echo as patch is upstream accepted Remove patch 206-compensate_time_change.patch as timewrap issues are solved by a patch making use of monotonic time Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ar71xx: correct button type for TL-MR3020 mode sliderDavid Bauer2020-05-311-2/+2
| | | | | | | | | | | | | | The TP-Link TL-MR3020 has a three-state mode slider which was previously integrated as a button (EV_KEY). This led to spurious activations of failsafe mode. Set the type for the button to switch (EV_SW), to avoid unintended activations of failsafe mode. Related: commit 27f3f493de06 ("gpio-button-hotplug: unify polled and interrupt code") Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add label MAC address for TP-Link RE450 v2/v3Adrian Schmutzler2020-05-311-0/+1
| | | | Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link RE450 v3Andreas Wiese2020-05-318-176/+290
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link RE450 v3 is a dual band router/range-extender based on Qualcomm/Atheros QCA9563 + QCA9880. This device is nearly identical to RE450 v2 besides a modified flash layout (hence I think force-flashing a RE450v2 image will lead to at least loss of MAC address). Specification: - 775 MHz CPU - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 3T3R 5 GHz - 1x 10/100/1000 Mbps Ethernet (AR8033 PHY) - 7x LED, 4x button- - possible UART header on PCB¹ Flash instruction: Apply factory image in OEM firmware web-gui. ¹ Didn't check to connect as I didn't even manage to connect on RE450v2 (AFAIU it requires disconnecting some resistors, which I was too much of a coward to do). But given the similarities to v2 I think it's the same or very similar procedure (and most likely also the only way to debrick). Signed-off-by: Andreas Wiese <aw-openwrt@meterriblecrew.net> [remove dts-v1 and compatible in DTSI] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link TL-WR802N V1 and V2Lech Perczak2020-05-316-1/+162
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specification: - SoC: Qualcomm Atheros QCA9533 (560 MHz, MIPS 24Kc) - RAM: 32 MiB - Storage: 4 MiB of Flash on board - Wireless: Built into QCA9533 (Honey Bee), PHY modes b/g/n - Ethernet: 1x100M (port0) Installation through OEM Web Interface: - Connect to TL-WR802N by Ethernet or Wi-Fi - Go to web interface: [V1] http://192.168.0.1 [V2] http://192.168.0.254 Default user is "admin" & password is "admin". On V2, there is no DHCP server running by default, so remember to set IP manually. - Go to "System Tools -> Firmware Upgrade" - Browse for firmware: [V1] "*.factory.bin" [V2] "*.factory-us.bin" or "*.factory-eu.bin" for eu model Web interface may complain if filename is too long. In such case, rename .bin to something shorter. - Click upgrade Installation through tftp: Note: T_OUT, T_IN and GND on the board must be connected to USB TTL Serial Configuration 115200 8n1 - Boot the TL-WR802N - When "Autobooting in 1 seconds" appears type "tpl" followed by enter - Connect to the board Ethernet port (IPADDR: 192.168.1.1, ServerIP: 192.168.1.10) - tftpboot 0x80000000 <Firmware Image Name> - Record the result of "printenv bootcmd" - Enter "erase <Result of 'printenv bootcmd'> +0x3c0000" (e.g erase 0x9f020000 +0x3c0000) - Enter "cp.b 0x80000000 <Result of 'printenv bootcmd'> 0x3c0000" (e.g cp.b 0x80000000 0x9f020000 0x3c0000) - Enter "bootm <Result of 'printenv bootcmd'>" (e.g bootm 0x9f020000) Notes: When porting from ar71xx target to ath79, I found out that on V2, reset button is on GPIO12 and active low, instead of GPIO11 and active high. By cross-flashing V1 firmware to V2, I confirmed the same is true for V1. Also according to manual of V1, this one also has green LED instead of blue - both of those issues were fixed accordingly. The MAC address assignment has been checked with OEM firmware. Installation manual based on ar71xx support by Thomas Roberts Signed-off-by: Lech Perczak <lech.perczak@gmail.com> [slightly adjust commit message, add MAC address comment] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: fix reset key for TP-Link TL-WR802N V1/V2Lech Perczak2020-05-311-2/+2
| | | | | | | | | | | | | | | | | | During porting support for this router to ath79 target it was discovered that GPIO mapping was incorrect (GPIO11 active high). Correct mapping for both V1 and V2 is GPIO12 active low. Default configuration from GPL source for V2 explicitly states this, and this was confirmed experimentally on ath79 by looking on /sys/kernel/debug/gpio. Correctness of this was also validated for V1 by cross-flashing vendor firmware for V1 on V2 hardware, in which reset button also worked. Fix it. Signed-off-by: Lech Perczak <lech.perczak@gmail.com> [slightly adjust commit title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: update WA/XC devices UBNT_VERSION to 8.5.3Roger Pueyo Centelles2020-05-311-3/+3
| | | | | | | | | | | | | | Ubiquiti WA devices with newer hw version 2011K require UBNT_VERSION to be at least 8.5.3, otherwise the image is rejected: New ver: WA.ar934x.v8.5.0-42.OpenWrt-r10947-65030d81f3 Versions: New(525568) 8.5.0, Required(525571) 8.5.3 Invalid version 'WA.ar934x.v8.5.0-42.OpenWrt-r10947-65030d81f3' For consistency, also increase version number for XC devices. Tested-by: Pedro <pedrowrt@cas.cat> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* ipq806x: EA8500 fix boot partition detectionSamantha Collard2020-05-311-2/+0
| | | | | | | Remove extraneous code that disabled boot partition detection. Fixes: b3770eaca39f ("mtd: base-files: Unify dual-firmware devices (Linksys)") Signed-off-by: Samantha Collard <sammyrc34@gmail.com>
* ath79: fix LEDs for GL.inet GL-AR150Adrian Schmutzler2020-05-312-12/+10
| | | | | | | | | | | | | | | | | Since the wireless LED was used for boot and set up with a DT trigger, the WiFi indication hasn't worked on ath79 at all. In addition, a look into the manual revealed that the OEM configuration is as follows: LED 1 (green): power LED 2 (green): configurable LED 3 (red): wireless So, let's just keep the WiFi trigger and convert the rest to its "intended" use. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mt76: update to the latest version (adds 7663e, 7663u, 7915 drivers)Felix Fietkau2020-05-311-10/+87
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 7aabfd0c9282 mt7615: add CONFIG_MT76_LEDS to cflags 10a5b7630a37 mt76: mt7615: fix getting maximum tx power from eeprom 8688ed70c987 mt76: mt7615: use module parameter option for offload firmware preference 04798aab1257 net: mt7603: remove duplicate error message 9636177117d8 mt76: mt7615: fix ssid configuration in mt7615_mcu_hw_scan d4ba139d8b8b mt76: mt7615: introduce mt7615_check_offload_capability routine 2cc0d54b65a1 mt76: mt7615: do not mark sched_scan disabled in mt7615_scan_work 5b73be962388 mt76: mt7615: add passive mode for hw scan 96e429e18174 mt76: mt7615: free pci_vector if mt7615_pci_probe fails 8fddbf6390ac mt76: mt7615: introduce support for hardware beacon filter f2c760177bdd mt76: mt7615: introduce mt7615_mcu_set_hif_suspend mcu command db454605106f mt76: mt7615: add WoW support 20b87321c39f mt76: mt7663u: introduce suspend/resume to mt7663u 20db7e73c586 mt76: mt7615: introduce PM support 523716bba561 mt76: mt7615: add gtk rekey offload support 50d377a825cc mt76: mt7615: introduce beacon_loss mcu event 4ef1957cea35 mt76: mt7663: read tx streams from eeprom f25a43cc53e7 mt76: mt7615: check return value of mt7615_eeprom_get_power_index 0a9f71652927 mt76: mt7615: fix ibss mode for mt7663 83f2ba3101b4 mt76: mt7663: fix target power parsing 3e6968593b61 mt76: mt7615: fix delta tx power for mt7663 c1d3ad194ae4 mt76: mt7663: introduce WoW with net detect support 891136ab99da mt76: mt7663: add support to sched scan with randomise addr 82e4d3ebe967 mt76: mt7615: scan all channels if not specified 690b84821cd3 mt76: avoid rx reorder buffer overflow f0117d3107b4 mt76: add support for HE RX rate reporting cc68782bab1a mt76: add Rx stats support for radiotap 3ec47f2fba61 mt76: adjust wcid size to support new 802.11ax generation 0a9f4173dd07 mt76: add HE phy modes and hardware queue c6b002bcdfa6 mt76: add mac80211 driver for MT7915 PCIe-based chipsets b96af5039581 mt76: mt7915: enable Rx HE rate reporting 230054096155 mt76: mt7915: implement HE per-rate tx power support c8f4b6cf1add mt76: mt7915: register per-phy HE capabilities for each interface de1e8af96e19 mt76: mt7915: add HE bss_conf support for interfaces 135a5085932b mt76: mt7915: add HE capabilities support for peers 3b5d908dae2f mt76: mt7915: add Rx radiotap header support 158253e2c11e mt76: mt7915: add .sta_add_debugfs support 7f40e8c2b98d mt76: mt7915: add .sta_statistics support a5368e5cad11 mt76: mt7915: set peer Tx fixed rate through debugfs 4f79c516be5c mt76: mt7915: add tsf related callbacks 509fceb43235 mt76: mt7915: enable firmware module debug support 56405976fc7b mt76: set runtime stream caps by mt76_phy 6bbf1a35c0da linux-firmware: add rebb firmware for mt7663 d7a10094c4e5 mt7663: add client offload firmware 9200732e8534 mt76: mt7663u: copy key pointer in mt7663u_mac_write_txwi 3aa810bde810 mt76: mt7663u: add missing register definitions e236ea5be344 mt76: mt7615: usb: cancel ps work stopping the vif 1d0903de2131 mt76: mt7915: introduce mt7915_get_he_phy_cap 095c72c81c74 mt76: mt7915: add Tx beamformer support 5f9e7664cd26 mt76: mt7915: add Tx beamformee support ac505404c385 mt76: mt7915: add TxBF capabilities 6656bebd39cd mt76: mt7915: add debugfs to track TxBF status 9590db025475 mt76: mt7915: allocate proper size for tlv tags 26eb1ed65987 mt76: mt7915: fix possible deadlock in mt7915_stop f85c1f3fc189 firmware: add mt7915 firmware 9b07251b00b0 mt76: mt7615: fix typo defining ps work 060e375a9244 mt76: fix per-driver wcid range checks after wcid array size bump 7270b56389a9 mt76: mt7615: do not report scan_complete twice to mac80211 8c9e4847d01e mt76: mt7615: reduce hw scan timeout 8bd88a1b1880 mt76: enable p2p support 1ea444d0e8e5 mt76: mt7615: configure bss info adding the interface fa81da5bb4e9 mt76: mt7615: introduce remain_on_channel support 44f2262c0289 mt76: mt76x02: remove check in mt76x02_mcu_msg_send 7005aa891440 mt76: mt7915: add spatial reuse support 1e3dc5b76649 mt76: mt7915: fix some sparse warnings 01b784174cd5 mt76: mt7915: fix sparse warnings: incorrect type initializer 40b7b5354a16 mt76: mt7615: fix NULL pointer deref in mt7615_register_ext_phy 6d731d188d31 mt76: mt7915: fix decoded radiotap HE flags b74d5b1c14cf mt76: mt7915: fix some sparse warnings 6679d35be5cc mt76: mt7615: switch to per-vif power_save support 01e870b44769 mt76: mt7915: fix a handful of spelling mistakes 7b2d16655904 mt76: mt7663: fix the usage WoW with net detect support ed3a244fb647 mt76: mt7915: Fix build error 5396a61cec99 mt76: mt7615: fix hw_scan with ssid_type for specified SSID only 466a5b4d041d mt76: mt7915: fix possible NULL pointer dereference in mt7915_register_ext_phy 984a172609c0 mt76: fix wcid allocation issues 6e02acddcb1a mt76: mt7615: add support for MT7611N 4e6f4e432d0d mt76: only iterate over initialized rx queues 9ad940fee593 mt76: mt7615: Use kmemdup in mt7615_queue_key_update() 85c516081338 mt76: mt7915: remove set but not used variable 'msta' Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: compress kernel debuginfo using zstdMatthias Schiffer2020-05-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | zstd with its default settings (compression level -3) compresses better than bzip2 -9 (which is the default setting), and is an order of magnitude faster. I made the following measurements for the most common compression tools (all standard Debian Buster versions, default flags unless noted otherwise), using the debug information of a large x86-64 kernel with ALL_KMODS: * kernel-debug.tar: 376M * kernel-debug.tar.gz: 101M, compressed in ~12s * kernel-debug.tar.bz2: 91M, compressed in ~15s * kernel-debug.tar.xz: 57M, compressed in ~101s * kernel-debug.tar.zst: 86M, compressed in ~1s With zstd, there is still some room for improvement by increasing the compression, but the slight increase in compression ratio (22.83% -> 19.46%) does not justify the significant increase in compression time (about 5 times on my machine) in my opinion. Note that multithreaded compression (-T argument) does not affect reproducibility with zstd. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-30 18:00:34 +0000