aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ramips: add label MAC address for Edimax RG21SAdrian Schmutzler2019-12-171-0/+1
| | | | | | | | | | | | | | | | The Edimax RG21S has a label which bears two MAC addresses: 2.4 GHz (n) and 5 GHz (n+1) The complete MAC address setup is as follows: 2.4 GHz *:83 factory 0x4, u-boot-env wlanaddr 5 GHz *:84 factory 0x8004 LAN *:83 u-boot-env ethaddr WAN *:85 u-boot-env wanaddr Since 2.4 GHz is the first address on the label and the same as used for ethernet, take this one for label MAC address. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: increase SPI frequency for Edimax RG21SBirger Koblitz2019-12-171-1/+1
| | | | | | | | This increases SPI frequency from the relatively low 10 MHz to 40 MHz. Signed-off-by: Birger Koblitz <mail@birger-koblitz.de> [added commit title/message, split patch] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove unnecessary nodes in DTS for Edimax RG21SBirger Koblitz2019-12-171-10/+0
| | | | | | | | | This sdhci and i2c nodes were copy-pasted, but are not needed as the device does not provide that functionality. Remove them. Signed-off-by: Birger Koblitz <mail@birger-koblitz.de> [added commit title/message, split patch] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* rpcd: update to latest Git HEADJo-Philipp Wich2019-12-171-3/+3
| | | | | | aaa0836 file: extend exec acl checks to commands with arguments Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: indicate upgrade using system LEDDavid Bauer2019-12-161-0/+3
| | | | | | | | | This enables the system LED to indicate a running firmware upgrade. This pattern is used on most platforms provided by the generic base-files package. ar71xx uses it's own implementation for the system-LED, where the upgrade case is not yet implemented. Signed-off-by: David Bauer <mail@david-bauer.net>
* mac80211: fix txpower when using DFS channelsDavid Bauer2019-12-161-2/+7
| | | | | | | | | | | With this patch, txpower for the PHY is applied when configuring the PHY instead of the VIF. Otherwise, the configured txpower is not applied for the first initialized VIF when using DFS channels, as it is currently applied too early when the CAC hasn't finished. Reported-by: Martin Weinelt <martin@darmstadt.freifunk.net Signed-off-by: David Bauer <mail@david-bauer.net> Tested-by: Martin Weinelt <martin@darmstadt.freifunk.net>
* odhcpd: update to latest git HEADHans Dedecker2019-12-151-3/+3
| | | | | | d60f0a6 treewide: optimize syslog priority values Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* mpc85xx: add support for Enterasys WS-AP3710iDavid Bauer2019-12-137-0/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: NXP P1020 (2x e500 @ 800MHz) RAM: 256M DDR3 (Micron) FLASH: 32M NOR (Spansion S29GL128S) BTN: 1x Reset WiFi: 1x Atheros AR9590 2.4 bgn 3x3 2x Atheros AR9590 5.0 an 3x3 ETH: 1x Gigabit Ethernet (Atheros AR8033) LED: System (green/red) - Radio{0,1} (green) LAN (connected to PHY) - GE blue - FE green Serial is a Cisco-compatible RJ45 next to the ethernet port. 115200-N-8 are the settings for OS and U-Boot. Installation ------------ 1. Grab the OpenWrt initramfs, rename it to 01C8A8C0.img. Place it in the root directory of a TFTP server and serve it at 192.168.200.200/24. 2. Connect to the serial port and boot the AP. Stop autoboot in U-Boot by pressing Enter when prompted. Credentials are identical to the one in the APs interface. By default it is admin / new2day. 3. Set the bootcmd so the AP can boot OpenWrt by executing $ setenv boot_openwrt "setenv bootargs; cp.b 0xee000000 0x1000000 0x1000000; bootm 0x1000000" $ setenv bootcmd "run boot_openwrt" $ saveenv If you plan on going back to the vendor firmware - the bootcmd for it is stored in the boot_flash variable. 4. Load the initramfs image to RAM and boot by executing $ tftpboot 0x1000000 192.168.200.200:01C8A8C0.img; bootm 5. Make a backup of the "firmware" partition if you ever wish to go back to the vendor firmware. 6. Upload the OpenWrt sysupgrade image via SCP to the devices /tmp folder. 7. Flash OpenWrt using sysupgrade. $ sysupgrade -n /tmp/openwrt-sysupgrade.bin Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: add support for JCG JHR-AC876MDENG Qingfang2019-12-133-0/+162
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | JCG JHR-AC876M is an AC2600M router Hardware specs: SoC: MT7621AT 2.4GHz: MT7615N 4x4 @ PCIe0 5GHz: MT7615N 4x4 @ PCIe1 Flash: Winbond W25Q128JVSQ 16MiB RAM: Nanya NT5CB128M16 256MiB USB 2.0 and 3.0 ports 6 LEDs, 3 of which are connected to SoC GPIO Reset and WPS buttons Flash instructions: Stock to OpenWrt: Upload factory.bin in stock firmware's upgrade page, do not preserve settings OpenWrt to stock: Push and hold the reset button for 5s while power cycling to enter recovery mode; Visit 192.168.1.1 and upload stock firmware MAC addresses map: 0x0004 *:1c wlan2g/wan/label 0x8004 *:20 wlan5g 0xe000 *:1b lan 0xe006 *:1a not used in stock fw Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* ramips: allow JCG_MAXSIZE in kiB in Build/jcg-headerAdrian Schmutzler2019-12-132-2/+4
| | | | | | | | | | This allows JCG_MAXSIZE to be specified in kilobytes. This makes this value more consistent and easier comparable with other size variables. This also changes the only occurence of the variable, for Cudy WR1000. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add support for ipTIME A6ns-MSungbo Eo2019-12-133-0/+156
| | | | | | | | | | | | | | | | | | | | | | | | | ipTIME A6ns-M is a 2.4/5GHz band AC1900 router, based on MediaTek MT7621A. Specifications: - SoC: MT7621AT - RAM: DDR3 128MB - Flash: SPI NOR 16MB - WiFi: - 2.4GHz: MT7615 - 5GHz: MT7615 - Ethernet: 5x 10/100/1000Mbps - Switch: SoC internal - UART: - J4: 3.3V, TX, RX, GND (3.3V is the square pad) / 57600 8N1 Installation via web interface: 1. Flash **initramfs** image through the stock web interface. 2. Boot into OpenWrt and perform sysupgrade with sysupgrade image. Revert to stock firmware: 1. Perform sysupgrade with stock image. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: DTS style improvements for mt7621_wevo_w2914ns-v2.dtsiAdrian Schmutzler2019-12-133-14/+7
| | | | | | | | | | | | This does several trivial DTS style improvements: - Move device name compatible to DTS files (and fix compatible in 11acnas.dts) - Remove xhci node as status is set to okay in mt7621.dtsi already - 0x0 instead of 0x0000 - Simplify state_default node definition Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add support for ZIO FREEZIOSungbo Eo2019-12-133-2/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ZIO FREEZIO is a 2.4/5GHz band AC1200 router, based on MediaTek MT7621A. Specifications: - SoC: MT7621AT - RAM: DDR3 128MB - Flash: SPI NOR 16MB - WiFi: - 2.4GHz: MT7603EN - 5GHz: MT7612EN - Ethernet: 5x 10/100/1000Mbps - Switch: SoC internal - USB: 1x 3.0 - UART: - J4: 3.3V, RX, TX, GND (3.3V is the square pad) / 57600 8N1 Notes: - FREEZIO has almost the same board as WeVO W2914NS v2. - Stock firmware is based on OpenWrt BB. MAC addresses in factory partition: 0x0004: WiFi 2.4GHz (label_mac-8) 0x002e: WAN (label_mac) 0x8004: WiFi 5GHz (label_mac-4) 0xe000: LAN (label_mac+1) Installation via web interface: 1. Access web admin page and turn on "OpenWrt UI mode". 2. Flash sysupgrade image through LuCI, with the "Keep settings" option OFF. Revert to stock firmware: 1. Perform sysupgrade with stock image. Make sure to NOT preserve settings. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rebase, use mt7621_wevo_w2914ns-v2.dtsi] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* sunxi: add support for FriendlyARM Nano PI NEO Air dev boardRoman Bazalevsky2019-12-132-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware: Allwinner H3 upto 1.2GHz 512MB DDR3 RAM 8GB on-board eMMC - mountable, can be used as boot with custom boot.scr microSD-card slot WiFi 802.11n (AP6212A) - working Bluetooth (AP6212A) - not working for now Micro-USB OTG + 2*USB headers UART 3.3V - working GPIO/I2C/SPI 2.54mm headers Standard sunxi SD-card installation procedure - copy image to SD card, insert in into slot and boot. First time you will need UART adapter to enable on-board wireless (or just build custom image with enabled WiFi). To boot from eMMC: - boot from SD - copy SD image to emmc (dd bs=... if=.... of=/dev/mmcblk2) - mount eMMC boot partition and replace boot script on it - unmount, reboot To use i2c, spi and more uarts - replace dtb on boot partition with fixed one (use dtc or fdt-tools). Signed-off-by: Roman Bazalevsky <rvb@rvb.name> [rebase onto device name consolidation patches] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* sunxi: construct DTS name from device node name and SOCAdrian Schmutzler2019-12-134-35/+45
| | | | | | | | | The device part in the SUNXI_DTS variable always corresponds to device node name. This is another redundancy that can be removed by calculating the DTS name from a newly introduced SUNXI_SOC variable and the node name. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* sunxi: use vendor_device scheme for device definitionsAdrian Schmutzler2019-12-135-133/+103
| | | | | | | | | | | | This changes device definition to resemble the vendor_device scheme already present for the majority of device compatible strings. By doing this, we achieve several advantages at once: - Image names and node names are more consistent with other targets. - SUPPORTED_DEVICES can be set automatically for all but two cases. - Image names and node names are in line with DEVICE_TITLEs. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link TL-WDR4300 v1 (IL)Adrian Schmutzler2019-12-124-1/+23
| | | | | | | | The TL-WDR4300 v1 sold in Israel has a different TPLINK_HWID. Thanks to Josh4300 for testing on device. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: redistribute UBNT variables in Ubiquiti image MakefileAdrian Schmutzler2019-12-121-15/+18
| | | | | | | | | | | | | The variables UBNT_BOARD and UBNT_VERSION are defined in the parent Device/ubnt definition and then overwritten for most of the derived platform definitions (e.g. Device/ubnt-wa). Since this mixed use of inheritance and overwriting can be misleading, this moves the variables to the platform-based definitions. While at it, reorder the definitions to have order consistent, too. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add label MAC address for Mikrotik RBM33GAdrian Schmutzler2019-12-121-1/+4
| | | | | | | | | | | | | | The device label contains: E01: B8:69:F4:xx:xx:07 E02: B8:69:F4:xx:xx:09 The first value corresponds to the address set in hard_config 0x10. That one is taken for the label MAC address. Thanks to Martin Schiller for retrieving the information. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: rt305x: use flash location for wan_mac in 02_networkAdrian Schmutzler2019-12-125-50/+60
| | | | | | | | | | | | | | | | | | | | | | | | | This uses the flash locations instead of eth0 MAC address to calculate MAC address increments for WAN. The change will make the MAC address setup of a particular device more obvious and removes the dependency of 02_network on the eth0 initialization. This removes the wan_mac setup for the following devices as they do not set up a MAC address for ethernet in the first place: - asiarf,awapn2403 - belkin,f7c027 - dlink,dir-615-d - mofinetwork,mofi3500-3gn - prolink,pwh2004 - ralink,v22rw-2x2 - unbranded,wr512-3gn-4m - unbranded,wr512-3gn-8m While at it, make some DT node labels consistent with the label property. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: rt288x: use flash location for wan_mac in 02_networkAdrian Schmutzler2019-12-121-4/+5
| | | | | | | | | | | | | | This uses the flash locations instead of eth0 MAC address to calculate MAC address increments for WAN. The change will make the MAC address setup of a particular device more obvious and removes the dependency of 02_network on the eth0 initialization. This removes the wan_mac setup for ralink,v11st-fe as this device does not set up a MAC address for ethernet in the first place. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: mt76x8: use flash location for wan_mac in 02_networkAdrian Schmutzler2019-12-122-19/+29
| | | | | | | | | | | | | | This uses the flash locations instead of eth0 MAC address to calculate MAC address increments for WAN. The change will make the MAC address setup of a particular device more obvious and removes the dependency of 02_network on the eth0 initialization. While at it, change the partition label for zyxel,keenetic-extra-ii to factory to be consistent with node label and all the other devices. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: mt7621: use flash location for wan_mac in 02_networkAdrian Schmutzler2019-12-121-16/+26
| | | | | | | | | | | This uses the flash locations instead of eth0 MAC address to calculate MAC address increments for WAN. The change will make the MAC address setup of a particular device more obvious and removes the dependency of 02_network on the eth0 initialization. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: mt7620: use flash location for wan_mac in 02_networkAdrian Schmutzler2019-12-121-12/+16
| | | | | | | | | | | This uses the flash locations instead of eth0 MAC address to calculate MAC address increments for WAN. The change will make the MAC address setup of a particular device more obvious and removes the dependency of 02_network on the eth0 initialization. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove wan_mac setup for evaluation boardsAdrian Schmutzler2019-12-123-6/+0
| | | | | | | | The evaluation boards do not set up a MAC address for eth0 in the first place, so it does not make sense to calculate a WAN address from the random MAC used there. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: create common DTSI for TP-Link Archer C20i/C20 v1/C50 v1Adrian Schmutzler2019-12-124-358/+137
| | | | | | | The TP-Link Archer C20i/C20 v1/C50 v1 seem to be almost the same, so creating a common DTSI will reduce duplicate code. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove unused DTS variable from DEVICE_VARSAdrian Schmutzler2019-12-121-1/+1
| | | | | | | | | | | | | The DTS variable has been removed in 402138d12dca ("ramips: Derive DTS name from device name in Makefile"), but the DEVICE_VARS entry has been overlooked. Remove it now since we are not using this variable. This must _not_ be backported to 19.07, where the variable is still in use. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: fix switch port numbering for RT-AC65P/RT-AC85PGabor Varga2019-12-111-2/+2
| | | | | | | | | | | The switch LAN port numbers are in reversed order with original config. With this patch they are fixed. Port order checked on both devices. Signed-off-by: Gabor Varga <vargagab@gmail.com> [merged definitions into appropriate block, extended commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add label MAC address for TP-Link Archer C20iAdrian Schmutzler2019-12-111-0/+4
| | | | | | | | | | | | | | Current OpenWrt MAC setup: eth0 &rom 0xf100 :48 eth0.2 eth0+1 :49 wlan0 (5 GHz) &radio 0x8004 different OUI wlan1 (2.4 GHz) &radio 0x4 same OUI as wlan0 Label MAC address corresponds to eth0 (&ethernet). No additional addresses found in hexdump of rom/radio. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix typos in DTSDENG Qingfang2019-12-114-11/+11
| | | | | | Replace "usb_ochi" with "usb_ohci", and "usb_echi" with "usb_ehci". Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn>
* glibc: update to latest 2.27 commit (BZ #2503, BZ #2504)Hans Dedecker2019-12-111-2/+2
| | | | | | | | bef0b1cb31 libio: Disable vtable validation for pre-2.1 interposed handles [BZ #25203] 4d5cfeb510 rtld: Check __libc_enable_secure before honoring LD_PREFER_MAP_32BIT_EXEC (CVE-2019-19126) [BZ #25204] 92f04eedb5 mips: Force RWX stack for hard-float builds that can run on pre-4.8 kernels Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ath10k-firmware: update Candela Tech firmware imagesKoen Vandeputte2019-12-101-24/+24
| | | | | | | | | | | | | | The release notes since last time for wave-1: * November 29, 2019: Fix IBSS merge issue, related to TSF id leakage bug in firmware code. Thanks for Ahmed Zaki @ Mage-Networks for helping to diagnose and test. The release notes since last time for wave-2: * December 6, 2019: Fix 160Mhz problem caused by logic that did not take into account the fact that 160Mhz has only 1/2 of the NSS of lower bandwidths in the rate table. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.19 to 4.19.88Koen Vandeputte2019-12-1026-358/+57
| | | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 0004-boot-sq201-from-sda1.patch - 500-v4.20-ubifs-Fix-default-compression-selection-in-ubifs.patch - 0003-usb-dwc2-use-a-longer-core-rest-timeout-in-dwc2_core.patch Altered patches: - 0011-ARM-dts-Fix-up-SQ201-flash-access.patch - 400-mtd-add-rootfs-split-support.patch - 0101-pci-mediatek-backport-fix-pcie.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.158Koen Vandeputte2019-12-1021-42/+42
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 400-mtd-add-rootfs-split-support.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.206Koen Vandeputte2019-12-1017-47/+47
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 400-mtd-add-rootfs-split-support.patch Compile-tested on: none Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* malta: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-092-4/+0
| | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* sunxi: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-092-4/+0
| | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* layerscape: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-092-4/+0
| | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kirkwood: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-092-4/+0
| | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* at91: disable legacy PTYs and virtual terminalsDaniel Golle2019-12-091-6/+0
| | | | | | | | | Enabling legacy PTYs causes problems with procd-hotplug. And as this is a headless target, no need to have virtual terminals. Remove corresponding kernel config options, they are disabled in generic kernel config. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mpc85xx: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-092-4/+0
| | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ixp4xx: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-091-2/+0
| | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* uml: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-092-4/+0
| | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* oxnas: disable legacy PTYs and virtual terminalsDaniel Golle2019-12-091-6/+0
| | | | | | | | | Enabling legacy PTYs causes problems with procd-hotplug. And as this is a headless target, no need to have virtual terminals. Remove corresponding kernel config options, they are disabled in generic kernel config. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mac80211: don't call md5sum on non-existing fileDaniel Golle2019-12-081-1/+1
| | | | | | | | | | | | If no AP is configured, hostapd-${phy}.conf is not being created, hence md5sum fails and causes log pollution: netifd: radio1 (3183): md5sum: can't open '/var/run/hostapd-phy1.conf': No such file or directoy Hence make sure the file exists when calling md5sum. Fixes: a5bc9787d4 ("mac80211: add support for dynamically reconfiguring wifi") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* hostapd: re-introduce process trackingDaniel Golle2019-12-082-0/+7
| | | | | | | | | | | Before commit 60fb4c92b6 ("hostapd: add ubus reload") netifd was tracking hostapd/wpa_supplicant and restarting wifi in case of a process crash. Restore this behaviour by tracking the PIDs of hostapd and wpa_supplicant. Also make sure hostapd and/or wpa_supplicant have been started before emmitting ubus calls to them using ubus wait_for. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mac80211: track unmanaged interfacesDaniel Golle2019-12-081-3/+42
| | | | | | | | | In addition to wpa_supplicant and hostapd managed interfaces, also track unmanaged interfaces. This is used to make sure that running 'wifi' always returns into a clean state regardless of what the user did before. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* hostapd: manage instances via procd instead of pidfileFelix Fietkau2019-12-081-9/+41
| | | | | | | | Allows graceful restart of crashing hostapd/wpa_supplicant instances Signed-off-by: Felix Fietkau <nbd@nbd.name> Signed-off-by: Daniel Golle <daniel@makrotopia.org> [daniel@makrotopia.org: attempt to launch only present services]
* hostapd: fix crash regression triggered by mesh modeFelix Fietkau2019-12-081-1/+1
| | | | | | | Fixes: 60fb4c92b6 ("hostapd: add ubus reload") Signed-off-by: Felix Fietkau <nbd@nbd.name> Signed-off-by: Daniel Golle <daniel@makrotopia.org> [daniel@makrotopia.org: polish commit message]
* treewide: remove dts-v1 identifier from DTSI filesAdrian Schmutzler2019-12-0846-49/+0
| | | | | | | | | | | | | | | | The "/dts-v1/;" identifier is supposed to be put once at the beginning of a device tree file. Thus, it makes no sense to provide it a second time in to-be-included DTSI files. This removes the identifier from all DTSI files in /target/linux. Most of the DTS files in OpenWrt do contain the "/dts-v1/;". It is missing for most of the following targets, though: mvebu, ipq806x, mpc85xx, ipq40xx This does not touch ipq806x for now, as the bump to 4.19 is close. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-11 22:22:07 +0000