aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* archs38: switch to kernel 5.4 by defaultEvgeniy Didin2020-03-291-1/+1
| | | | | | | | Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Petr Štetiar <ynezz@true.cz> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org>
* archs38: Add patch for gcc8 compilanceEvgeniy Didin2020-03-291-0/+21
| | | | | | | | | | | | Building Linux kernel version 5.4.x with GCC8 ends up with internal compiler error. The workaround on this issue can be introdution of additional compiler option "--mmpy-option=2" Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Petr Štetiar <ynezz@true.cz> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org>
* archs38: add kernel 5.4 configEvgeniy Didin2020-03-291-0/+285
| | | | | | | | | | | | Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Petr Štetiar <ynezz@true.cz> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org> [run make kernel_oldconfig CONFIG_TARGET=target] [Do not deactivate CONFIG_NET_VENDOR_*] [Activate CONFIG_HARDENED_USERCOPY] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: update arc-specific patchEvgeniy Didin2020-03-291-11/+11
| | | | | | | | | | | This patch updates arc-specific patch by moving declaration of struct object before it's usage. Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> Cc: Alexey Brodkin <abrodkin@synopsys.com> Cc: Petr Štetiar <ynezz@true.cz> Cc: Hauke Mehrtens <hauke@hauke-m.de> Cc: John Crispin <john@phrozen.org>
* mvebu: cortexa9: correct cpu subtypeTomasz Maciej Nowak2020-03-281-1/+1
| | | | | | | | | | | | | | | Armada 370 processors have only 16 double-precision registers. The change introduced by 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation for gcc 8.x") switched accidentally the toolchain for mvebu cortexa9 subtarget to cpu type with 32 double-precision registers. This stems from gcc defaults which assume "vfpv3-d32" if only "vfpv3" as mfpu is specified. That change resulted in unusable image, in which kernel will kill userspace as soon as it causing "Illegal instruction". Ref: https://forum.openwrt.org/t/gcc-was-broken-on-mvebu-armada-370-device-after-commit-on-2019-03-25/43272 Fixes: 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation for gcc 8.x") Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* tegra: correct cpu subtypeTomasz Maciej Nowak2020-03-281-1/+1
| | | | | | | | | | | | | | | Tegra 2 processors have only 16 double-precision registers. The change introduced by 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation for gcc 8.x") switched accidentally the toolchain for tegra target to cpu type with 32 double-precision registers. This stems from gcc defaults which assume "vfpv3-d32" if only "vfpv3" as mfpu is specified. That change resulted in unusable image, in which kernel will kill userspace as soon as it causing "Illegal instruction". Ref: https://forum.openwrt.org/t/gcc-was-broken-on-mvebu-armada-370-device-after-commit-on-2019-03-25/43272 Fixes: 8dcc1087602e ("toolchain: ARM: Fix toolchain compilation for gcc 8.x") Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* x86: fix missing squashfs and ext4 rootfs imagesPaul Spooren2020-03-281-2/+4
| | | | | | | | | | | | | | | The previous rework of x86 image creation done in commit cb007a7bf619 ("x86: switch image generation to new code") removed images of separate squashfs and ext4 filesystems which are handy for example in testing under QEMU. So this patch adds back creation of those missing rootfs images for ext4 and squashfs based filesystems. Fixes: cb007a7bf619 ("x86: switch image generation to new code") Signed-off-by: Paul Spooren <mail@aparcar.org> [commit subject and description tweaks] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: fix padding in imagesPaul Spooren2020-03-281-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous rework of x86 image creation done in commit cb007a7bf619 ("x86: switch image generation to new code") broke the padding in images. sda: p2 size 212992 extends beyond EOD, enabling native capacity sda: p2 size 212992 extends beyond EOD, truncated sd 0:0:0:0: [sda] Attached SCSI disk SQUASHFS error: squashfs_read_data failed to read block 0x2cc556 unable to read id index table VFS: Cannot open root device "PARTUUID=ac5c9cd8-02" or unknown-block(8,2): error -5 Please append a correct "root=" boot option; here are the available partitions: 0800 19761 sda driver: sd 0801 16384 sda1 ac5c9cd8-01 0802 2865 sda2 ac5c9cd8-02 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2) Tested with x86/64 with Docker (squashfs), qemustart (ext4/squashfs) and virtualbox (ext4/squashfs). Ref: FS#2935 Fixes: cb007a7bf619 ("x86: switch image generation to new code") Suggested-by: Russell Senior <russell@personaltelco.net> Signed-off-by: Paul Spooren <mail@aparcar.org> [commit subject and description tweaks] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ar71xx: Fix gigabit switch support for Mikrotik RB951G-2HnDBaptiste Jonglez2020-03-281-0/+2
| | | | | | | | | | | | | | | | | | | | Without this patch, when using rev 3 of the Atheros AR9344 SoC, the gigabit switch (AR8327) does not work or works very erratically. This is a re-spin of http://patchwork.ozlabs.org/patch/419857/ with a different PLL value, according to the feedback from several users (including myself) as shown here: https://openwrt.org/toh/mikrotik/rb2011uias#tracking_reported_experience_with_suggested_patch_for_the_5_gige_ports Performance is acceptable: testing L3 forwarding without NAT yields a performance of 370 Mbit/s (iperf3 TCP) and 41 Kpps (iperf3 UDP with 64 bytes payload). Both tests show that 100% of CPU time is spent on softirq. A similar fix for a different device (RB2011) was added in e457d22261 ("Make GBit switch work on RB2011"). Signed-off-by: Baptiste Jonglez <git@bitsofnetworks.org>
* kernel: bump 5.4 to 5.4.28Petr Štetiar2020-03-2851-598/+110
| | | | | | | | | | | | | | | | | | | | Changelog since 5.4.24 mentions CVE-2019-19769, CVE-2020-8648, CVE-2020-8649 and CVE-2020-8647. Removed upstreamed: generic: 507-v5.6-iio-chemical-sps30-fix-missing-triggered-buffer-depe.patch generic: 600-ipv6-addrconf-call-ipv6_mc_up-for-non-Ethernet-inter.patch bcm27xx: 950-0435-ASoC-pcm512x-Fix-unbalanced-regulator-enable-call-in.patch ipq806x: 701-stmmac-fix-notifier-registration.patch lantiq: 002-pinctrl-falcon-fix-syntax-error.patch octeontx: 0002-net-thunderx-workaround-BGX-TX-Underflow-issue.patch Run tested: apu2, qemu-x86-64, apalis, a64-olinuxino, nbg6617 Build tested: sunxi/a53, imx6, x86/64, ipq40xx Tested-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> [apu2] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq40xx: switch to 5.4 kernelPetr Štetiar2020-03-281-1/+1
| | | | | | | 5.4.24 seems to be working fine on my zyxel,nbg6617, so let's start wider userbase testing. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq40xx: wpj428: fix missing MDIO GPIO reset and pinmuxLeon M. George2020-03-282-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | The bootloader does not always initialize the MDIO pins before booting Linux. E.g. on version "U-Boot 2012.07 [Chaos Calmer 15.05.1,r35193] (Jul 25 2017 - 11:36:26)" this is the case when booting automatically without activating the U-Boot console. Without this change, the kernel boot will complain about missing PHYs: libphy: ipq40xx_mdio: probed ar40xx c000000.ess-switch: Probe failed - Missing PHYs! libphy: Fixed MDIO Bus: probed With this change it will work as expected: libphy: ipq40xx_mdio: probed ESS reset ok! ESS reset ok! libphy: Fixed MDIO Bus: probed Ref: GH-2835 Tested-by: Fredrik Olofsson <fredrik.olofsson@anyfinetworks.com> Signed-off-by: Leon M. George <leon@georgemail.eu> [commit description from Fredrik, subject facelift] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* sunxi: switch to 5.4 kernelPetr Štetiar2020-03-281-1/+1
| | | | | | | Seems to be working fine on my a64-olinuxino, it's 99.9% upstream stuff anyway. Lets start wider userbase testing. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* sunxi: a53: fix ethernet on a64-olinuxinoPetr Štetiar2020-03-281-0/+1
| | | | | | | a64-olinuxino board has Micrel KSZ9031 Gigabit PHY so add support for this PHY into kernel. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* sunxi: 5.4: dts: a64: olinuxino: add bank supply regulatorsPetr Štetiar2020-03-281-0/+62
| | | | | | | | | | | | | | This is backport of v5.6 patch. Allwinner A64 SoC has separate supplies for PC, PD, PE, PG and PL. This patch adds regulators for them to the pinctrl node. Exception is PL which is used by the RSB bus. To avoid circular dependencies, VCC-PL is omitted. On boards with eMMC, VCC-PC is supplied by ELDO1, instead of DCDC1. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* sunxi: 5.4: a64-olinuxino: use red LED for status signalizationPetr Štetiar2020-03-282-0/+68
| | | | | | | There is a red LED marked as `GPIO_LED1` on the silkscreen and connected to PE17, so use this LED for status signalization. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* sunxi: a53: add support for Olimex A64-Olinuxino eMMCPetr Štetiar2020-03-281-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specifications: SoC: Allwinner A64 (1.2 GHz Quad-Core ARM Cortex-A53 64-bit) RAM: 1GB or 2GB RAM DDR3L @ 672Mhz Flash: 0/4/16GB eMMC flash memory for storage and boot MicroSD card connector for cards up to 32GB Debug: serial UART debug header with 0.1" pins Wired connectivity: 10/100/1000Mbps GbE Ethernet Wireless connectivity: on-board RTL8723BS 1T1R 802.11bgn WiFi and Bluetooth 4.0 module with built-in antenna (only available in the A64-OLinuXino-1G4GW) Flashing instructions: Standard sunxi SD card installation procedure - copy eMMC image to SD card, insert in into SD card slot on the device and boot. You should see something like following if the eMMC is detected correctly: mmcblk2: mmc2:0001 P1XXXX 3.60 GiB mmcblk2boot0: mmc2:0001 P1XXXX partition 1 16.0 MiB mmcblk2boot1: mmc2:0001 P1XXXX partition 2 16.0 MiB Then flash SD card eMMC image straight into the mmcblk2 device: dd if=/mnt/openwrt...a64-olinuxino-emmc-squashfs-sdcard.img of=/dev/mmcblk2 It also possible to boot from boot0 partition[1]: 1. Compile U-Boot with CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x40 otherwise the U-Boot will get stuck in bootloop 2. Configure eMMC to boot from boot0 partition inside U-Boot: mmc bootbus 1 1 0 0; mmc partconf 1 1 1 0 3. echo 0 > /sys/block/mmcblk2boot0/force_ro 4. Write U-Boot from offset 0 (not offset 8k as with SD card) into boot0 partition dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk2boot0 Known issues: Wireless doesn't work properly via netifd. 1. https://linux-sunxi.org/index.php?title=Bootable_eMMC Signed-off-by: Petr Štetiar <ynezz@true.cz>
* sunxi: a53: add support for Olimex A64-OlinuxinoPetr Štetiar2020-03-281-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | Specifications: SoC: Allwinner A64 (1.2 GHz Quad-Core ARM Cortex-A53 64-bit) RAM: 1GB or 2GB RAM DDR3L @ 672Mhz Flash: 0/4/16GB eMMC flash memory for storage and boot MicroSD card connector for cards up to 32GB Debug: serial UART debug header with 0.1" pins Wired connectivity: 10/100/1000Mbps GbE Ethernet Wireless connectivity: on-board RTL8723BS 1T1R 802.11bgn WiFi and Bluetooth 4.0 module with built-in antenna (only available in the A64-OLinuXino-1G4GW) Flashing instructions: Standard sunxi SD card installation procedure - copy image to SD card, insert in into SD card slot on the device and boot. Known issues: Wireless doesn't work properly via netifd. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* sunxi: a53: image: make it DRYPetr Štetiar2020-03-281-24/+22
| | | | | | Replace same copy&pasted lines with the appropriate reusable bits. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* bcm27xx: 5.4: add support for Sensirion SPS30 in i2c-sensor overlayPetr Štetiar2020-03-281-0/+59
| | | | | | | Add support for Sensirion SPS30 particulate matter sensor with fixed address 0x69. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: rename Mikrotik RB 922UAGS-5HPacD mtd partitionThibaut VARÈNE2020-03-272-4/+4
| | | | | | | | | | | | | | | | In RouterBOARD parlance there never was an "art" partition. This partition has always been named 'hard_config' on ar71xx. This partition contains more than just ART (Atheros Radio Test) data. It includes the hardware description (product code, serial, board identifier, name, hardware options, MAC address), as well as other bits affecting the operation of RouterBoot. To avoid confusion with regular ART data, this partition is renamed in line with historical ar71xx and ramips nomenclature as 'hard_config'. Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org> [minor commit title/message adjustments] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix Mikrotik wAP G-5HacT2HnD mtd partitionsThibaut VARÈNE2020-03-273-29/+38
| | | | | | | | | | | | | | | | | | | | | | In RouterBOARD parlance there never was an "art" partition. This partition has always been named 'hard_config' on ar71xx. This partition contains more than just ART (Atheros Radio Test) data. It includes the hardware description (product code, serial, board identifier, name, hardware options, MAC address), as well as other bits affecting the operation of RouterBoot. To avoid confusion with regular ART data, this partition is renamed in line with historical ar71xx and ramips nomenclature as 'hard_config'. This commit fixes the previous support files and implements the nested RouterBoot partition scheme as already used by ramips-based SPI-NOR RouterBOARD DTSes, as previously reviewed and implemented in bbe2cf657ca7 ("ramips: fix RBM11G partitioning"). Tested-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org> [minor commit title/message adjustments] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kirkwood: fix DTS partitions for Pogoplug E02Alberto Bursi2020-03-273-0/+110
| | | | | | | | | | | | | | | | | | | | | The Pogoplug E02 was not using the correct partitions in device tree, but used the ones from upstream and thus could not boot OpenWrt images. In contrast, uboot-kirkwood is using the correct partitions since d3fc4fbd74dc ("uboot-kirkwood: re-add Pogoplug E02 support"). This patch corrects the partitions in DTS for kernels 4.14, 4.19 and 5.4. Fixes: 2b0fa00da8fc ("kirkwood: add Pogoplug E02 Kernel support") Signed-off-by: Alberto Bursi <bobafetthotmail@gmail.com> Reviewed-by: Pawel Dembicki <paweldembicki@gmail.com> Reviewed-by: Sungbo Eo <mans0n@gorani.run> [commit title/message facelift, refresh 4.14 patch] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mediatke: add support for elecom-wrc-2533gentJohn Crispin2020-03-275-1/+1249
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the MT7622-based Elecom WRC-2533gent router, with spi-nand storage and 512MB RAM. The device has the following specifications: * MT7622 (arm64 dual-core) * 512MB RAM (DDR3) * 4GB storage (spi-nand) * 5x 1Gbps Ethernet (RTL8337C switch) * 1x UART header * 1x USB 3.0 port * 5x LEDs * 1x reset button * 1x WPS button * 1x slider switch * 1x DC jack for main power (12V) The following has been tested and is working: * Ethernet switch * 2.4g and 5g wifi * USB 3.0 port * sysupgrade * buttons/leds Not working: * bluetooth firmware does not load even though it is present int he rootfs Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: more v5.4 mtd fixesJohn Crispin2020-03-278-45/+1658
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx: use status led for GL.iNet GL-AR750SJan Alexander2020-03-261-0/+1
| | | | | | | | | | | | Use power led for device status. The status led behavior has already been fixed in af28d8a539fe ("ath79: add support for GL.iNet GL-AR750S") when porting the device to ath79. This fixes it for ar71xx as well. Signed-off-by: Jan Alexander <jan@nalx.net> [minor commit title/message adjustments] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link TL-WA860RE v1Adrian Schmutzler2020-03-264-0/+84
| | | | | | | | | | | | | | | | | | | | | | | | This ports support for the TL-WA860RE v1 range extender from ar71xx to ath79. Specifications: Board: AP123 / AR9341 rev. 3 Flash/RAM: 4/32 MiB CPU: 535 MHz WiFi: 2.4 GHz b/g/n Ethernet: 1 port (100M) Two external antennas Flashing instructions: Upload the factory image via the vendor firmware upgrade option. Recovery: Note that this device does not provide TFTP via ethernet like many other TP-Link devices do. You will have to open the case if you require recovery beyond failsafe. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Tested-by: Sebastian Knapp <sebastian4842@outlook.com>
* ath79: add support for TP-Link TL-WDR4310 v1Adrian Schmutzler2020-03-265-2/+25
| | | | | | | | | This device seems to be identical to the TL-WDR4300, just with different release date/region and TPLINK_HWID. Support is added based on the ar71xx implementation. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* x86/geode: fixup FEATURE inheritancePaul Spooren2020-03-231-1/+1
| | | | | | | | | | | | In the geode subtarget all default x86 features were overwritten via := instead of extending them via +=. This patch fixes the inheritance and thereby the compilation of x86/geode target. Compile tested x86/geode. Signed-off-by: Paul Spooren <mail@aparcar.org>
* x86/geode: add missing include after rebasePaul Spooren2020-03-231-0/+4
| | | | | | | | | | | | | The x86 image generation was refacted via cb007a7bf6 and accidently not included `geode.mk` when selected as subtarget. Now the file is included and image compilation for x86/geode works again. Thanks to Russell Senior <russell@personaltelco.net> for reporting the problem and suggesting a patch! Signed-off-by: Paul Spooren <mail@aparcar.org>
* bcm27xx: refresh linux 5.4 configsÁlvaro Fernández Rojas2020-03-234-66/+0
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: sync 5.4 patches with RPi FoundationÁlvaro Fernández Rojas2020-03-2317-2/+2797
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* apm821xx: switch to 5.4 kernelChristian Lamparter2020-03-221-2/+1
| | | | | | This patch switches the APM821XX target to the linux kernel 5.4 variant. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: wndr4700: add preliminary drivetemp sensorChristian Lamparter2020-03-222-2/+25
| | | | | | | | | | | | | | | | | | This patch prepares the WNDR4700 to use the HDD sensor for the thermal zone. While the kernel's thermal.txt device-tree binding documentation files talks about supporting multiple sensors for a zone. This sadly is NOT the case. Even the most current upstream kernels (5.6-rc) supports just >one< sensor per zone: (driver/base/of-thermal.c:886) | * REVIST: for now, the thermal framework supports only | * one sensor per thermal zone. Thus, we are considering | * only the first two values as slope and offset. I do hope that this warning will prevent others wasteing time on trying to figure out why their multi-sensor thermal-zones definitions are not working as specified. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add drivetemp sensor for the WD MyBook SeriesChristian Lamparter2020-03-222-1/+11
| | | | | | | | | This patch adds the hwmon-drivetemp to the device. It also adds device-tree bindings. This can be useful to automate external fans which can be controlled for example by either an unused sata-port or by the usb-power regulator. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: geode/legacy: fix missing watchdog core dependenciesChristian Lamparter2020-03-224-0/+4
| | | | | | | | | | | | | | | | | This patch follows the other patches that added the watchdog core to various (armvirt, malta, ath79, ...) targets that have been hit by the following build error: Package kmod-hwmon-sch5627 is missing dependencies for the following libraries: watchdog.ko In theory, we could have just added the CONFIG_WATCHDOG_CORE=y to the Kconfig variable of kmod-hwmon-sch5627's package definition. This would have forced the watchdog core to be builtin and less architectures would need to be updated. But we might as well follow through here. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: fix missing return statement in ar934x_nandDavid Bauer2020-03-221-4/+12
| | | | | | | | | | | The reset assert and deassert methods currently miss a return value, leading to a compilation warning. Return the return-value of reset_control_assert and reset_control_deassert to fix these warnings. Suggested-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl> Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: fix NAND driver compilation for kernel 5.4David Bauer2020-03-221-5/+122
| | | | | | | | | | | | | | | This fixes the compilation of the AR934x NAND controller driver for kernel 5.4 while leaving it untouched for kernel 4.19. This change is currently not run-tested, as i do not have such a device at hand. CC: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl> CC: André Valentin <avalentin@marcant.net> CC: WeiDong Jia <jwdsccd@gmail.com> Signed-off-by: David Bauer <mail@david-bauer.net> Tested-by: Michal Cieslakiewicz <michal.cieslakiewicz@wp.pl>
* oxnas: yet another irqchip related patchDaniel Golle2020-03-221-0/+55
| | | | | | | This time DTS fix, again from Sungbo Eo <mans0n@gorani.run> ARM: dts: oxnas: Fix clear-mask property Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ath79: align Ubiquiti AC Pro ethernet map to factoryDavid Bauer2020-03-221-2/+5
| | | | | | | | | | | | | | | | | | | | | | The Uniquiti AC Pro and Ubiquiti AC Mesh Pro currently have the "Primary" and "Secondary" ethernet ports configured to offer LAN as well as WAN. However, Uiquiti describes the following behavior for the devices Ethernet ports: > Secondary UniFi Access Point (UAP) Ethernet ports don't > provide PoE passthrough (to run current to a second powered > device), but they do support data passthrough. > It serves as a bridged interface between main / secondary > Ethernet port. To reduce confusion for users (as LAN and WAN functionality is not visible on the device itself), configure both ports to offer LAN functionality. Users can still configure a WAN interface on a port they are able to choose. CC: Lucian Cristian <lucian.cristian@gmail.com> Reported-by: Florian Klink <flokli@flokli.de> Signed-off-by: David Bauer <mail@david-bauer.net>
* ath79: add support for Ubiquiti NanoBridge M (XM)Roger Pueyo Centelles2020-03-225-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the Ubiquiti NanoBridge M (XM), a 802.11n wireless with a feed+dish form factor, with the same board definition as the Bullet M (XM). Specifications: - Atheros AR7241 SoC - 32 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet port, 24 Vdc PoE-in - Power and LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) Flashing via stock GUI: - WARNING: flashing OpenWrt from AirOS v5.6 or newer will brick your device! Read the wiki for more info. - Downgrade to AirOS v5.5.x (latest available is 5.5.11) first. - Upload the factory image via AirOS web GUI. Flashing via TFTP: - WARNING: flashing OpenWrt from AirOS v5.6 or newer will brick your device! Read the wiki for more info. - Downgrade to AirOS v5.5.x (latest available is 5.5.11) first. - Use a pointy tool (e.g., pen cap, slotted screwdriver) to keep the reset button pressed. - Power on the device (keep reset button pressed). - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button. - The device starts a TFTP server at 192.168.1.20. - Set a static IP on the computer (e.g., 192.168.1.21/24). - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_nanobridge-m-squashfs-factory.bin Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [rebase, fix includes in DTS, add label MAC address, add SOC and fix sorting in generic-ubnt.mk] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm53xx: sysupgrade: optimize building UBI imageRafał Miłecki2020-03-211-3/+3
| | | | | | | | | Use "truncate" to adjust size of existing file instead of "dd" which required creating a copy. This saves space on tmpfs. It may be as low as 2.1 MiB when using OpenWrt default user space and way more (20+ MiB) when flashing vendor firmware. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* treewide: omit IMAGE_SIZE argument from check-sizeSungbo Eo2020-03-2125-146/+146
| | | | | | | | | Now that check-size uses IMAGE_SIZE by default, we can skip the argument from image recipes to reduce redundancy. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: gather DEVICE_VARS into one placeSungbo Eo2020-03-2111-18/+21
| | | | | | | | | | | Place DEVICE_VARS assignments at the top of the file or above Device/Default to make them easier to find. For ramips, remove redundant values already present in parent file. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for ubnt_bullet-m-ar7240 variantRussell Senior2020-03-215-0/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the Ubiquiti Bullet M (AR7240). Specifications: - AR7240 SoC @ 400 MHz - 32 MB RAM - 8 MB SPI flash - 1x 10/100 Mbps Ethernet, 24 Vdc PoE-in - External antenna - POWER/LAN green LEDs - 4x RSSI LEDs (red, orange, green, green) - UART (115200 8N1) on PCB Flashing via WebUI: Upload the factory image via the stock firmware web UI. Attention: airOS firmware versions >= 5.6 have a new bootloader with an incompatible partition table! Please downgrade to <= 5.5 _before_ flashing OpenWrt! Refer to the device's Wiki page for further information. Flashing via TFTP: Same procedure as other Ubiquiti M boards. - Use a pointy tool (e.g., pen cap, paper clip) and keep the reset button on the device or on the PoE supply pressed - Power on the device via PoE (keep reset button pressed) - Keep pressing until LEDs flash alternatively LED1+LED3 => LED2+LED4 => LED1+LED3, etc. - Release reset button - The device starts a TFTP server at 192.168.1.20 - Set a static IP on the computer (e.g., 192.168.1.21/24) - Upload via tftp the factory image: $ tftp 192.168.1.20 tftp> bin tftp> trace tftp> put openwrt-ath79-generic-xxxxx-ubnt_bullet-m-ar7240-squashfs-factory.bin The "fixed-link" section of the device tree is needed to avoid errors like this: Generic PHY mdio.0:1f:04: Master/Slave resolution failed, maybe conflicting manual settings? With "fixed-link", the errors go away and eth0 comes up reliably. Signed-off-by: Russell Senior <russell@personaltelco.net> [fix SUPPORTED_DEVICES] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* gemini: Bump kernel to v5.4Linus Walleij2020-03-211-1/+1
| | | | | | | | The v5.4 kernel already works much better than v4.19 as so many things got upstreamed so let's just bump it to kernel v5.4. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* gemini: Add kernel config for kernel v5.4Linus Walleij2020-03-211-0/+466
| | | | | | | | | | | | | | This adds a kernel config file for the v5.4 gemini kernel. No major changes compared to v4.19, mainly CONFIG_MTD_PHYSMAP_OF_GEMINI was renamed to CONFIG_MTD_PHYSMAP_GEMINI. Signed-off-by: Linus Walleij <linus.walleij@linaro.org> [select UNWINDER_ARM, set CONFIG_DRM_FBDEV_OVERALLOC, drop dropped 4.19 symbols, kernel config refreshed] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* gemini: Add v5.4 kernel patchesLinus Walleij2020-03-214-0/+386
| | | | | | | | | | | | | | This adds the kernel patches needed for the Gemini. Just 7 patches, 5 of them are already upstream. Notably we incorperate the temperature sensor on the hard drive to drive temperature control of the NAS chassis. This is required for the DIR-685 which has no external temperature sensor. Signed-off-by: Linus Walleij <linus.walleij@linaro.org> [use the drivetemp package over the backport] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: 5.4: disable more symbolsChristian Lamparter2020-03-211-0/+8
| | | | | | | These have been discovered by the gemini 5.4 patches. This is because one of the devices uses the FBDEV emulation. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: backport and package drivetemp hwmon from v5.5Christian Lamparter2020-03-213-0/+945
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch backports the hwmon drivetemp sensor module from vanilla linux 5.5 to be available on OpenWrt's 5.4 kernel. Extract from The upstream commit by Guenter Roeck <linux@roeck-us.net>: hwmon: Driver for disk and solid state drives with temperature sensors "Reading the temperature of ATA drives has been supported for years by userspace tools such as smarttools or hddtemp. The downside of such tools is that they need to run with super-user privilege, that the temperatures are not reported by standard tools such as 'sensors' or 'libsensors', and that drive temperatures are not available for use in the kernel's thermal subsystem. This driver solves this problem by adding support for reading the temperature of ATA drives from the kernel using the hwmon API and by adding a temperature zone for each drive. With this driver, the hard disk temperature can be read [...] using sysfs: $ grep . /sys/class/hwmon/hwmon9/{name,temp1_input} /sys/class/hwmon/hwmon9/name:drivetemp /sys/class/hwmon/hwmon9/temp1_input:23000 If the drive supports SCT transport and reports temperature limits, those are reported as well. drivetemp-scsi-0-0 Adapter: SCSI adapter temp1: +27.0<C2><B0>C (low = +0.0<C2><B0>C, high = +60.0<C2><B0>C) (crit low = -41.0<C2><B0>C, crit = +85.0<C2><B0>C) (lowest = +23.0<C2><B0>C, highest = +34.0<C2><B0>C) The driver attempts to use SCT Command Transport to read the drive temperature. If the SCT Command Transport feature set is not available, or if it does not report the drive temperature, drive temperatures may be readable through SMART attributes. Since SMART attributes are not well defined, this method is only used as fallback mechanism." This patch incorperates a patch made by Linus Walleij: 820-libata-Assign-OF-node-to-the-SCSI-device.patch This patch is necessary in order to wire-up the drivetemp sensor into the device tree's thermal-zones. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>