aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* mediatek: mt7629: refresh config for linux 5.4Chuanhong Guo2020-03-211-104/+1
| | | | Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* mediatek: mt7629: fix ethernet default configChuanhong Guo2020-03-211-2/+2
| | | | | | | 1. fix typo: ucidef_set_interfaces_wan -> ucidef_set_interface_wan 2. change board name to mt7629-rfb to match upstream dts Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* kernel: rtl8367b: add configuration for extif2Serge Vasilugin2020-03-211-5/+42
| | | | | | | | | | | | | | | | | | | | | | Both rtl8367b and rtl8367s have two extended interface rtl8367rb: 5 port + 2*RGMII/MII rtl8367s: 5 port + SGMII/HSGMI + RGMII/MII (?)rtl8367sb: 5 port + 2*RGMII/MII These interfaces correspond to EXT1 and EXT2 (ports 6 and 7 respectivly). This patch allow to configure EXT2 in dts-file: rtl8367rb { compatible = "realtek,rtl8367b"; cpu_port = <7>; realtek,extif2 = <1 0 1 1 1 1 1 1 2>; mii-bus = <&mdio0>; phy_id = <29>; }; Signed-off-by: Serge Vasilugin <vasilugin@yandex.ru> [fix indent, replace magic value, alter commit message] Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* generic: rtl8367b: add definition of debug regChuanhong Guo2020-03-211-5/+30
| | | | | | | This commit adds definition of DEBUG0 and DEBUG1 registers and replace magic values with proper register modifying. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* oxnas: backport patch fixing hang after rebootDaniel Golle2020-03-191-0/+77
| | | | | | | | | | | Sungbo Eo <mans0n@gorani.run> posted a patch fixing the long-standing reboot problem on the OXNAS OX820 platform: irqchip/versatile-fpga: Handle chained IRQs properly It got queued for 5.7. Import it to oxnas target patches for now. Fixes: b4917fa907 ("oxnas: fix oxnas-rps-timer dt-match") Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ath79: add support for TP-Link Archer D7/D7b v1Davide Fioravanti2020-03-187-0/+390
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer D7 v1 is a dual-band AC1750 router + modem. The router section is based on Qualcomm/Atheros QCA9558 + QCA9880. The "DSL" section is based on BCM6318 but it's currently not supported. The Archer D7b seems to differ from the Archer D7 only in the partition table. Router section - Specification: 775/650/258 MHz (CPU/DDR/AHB) 128 MB of RAM (DDR2) 16 MB of FLASH (SPI NOR) 3T3R 2.4 GHz 3T3R 5 GHz 4x 10/100/1000 Mbps Ethernet 7x LED, 2x button UART header on PCB Known issues: - Broadband LED (missing GPIO - probably driven by the BCM6318) - Internet LED (missing GPIO - probably driven by the BCM6318) - WIFI LED (working only for one interface at a time, while in the OEM firmware works for both wifi interfaces; thus, this patch does not set a trigger by default) - DSL not working (eth0) UART connection --------------- J1 HEADER (Qualcomm CPU) . VCC . GND . RX O TX J41 HEADER (Broadcom CPU) . VCC . GND . RX O TX The following instructions require a connection to the J1 UART header and are tested for the Archer D7 v1. For the Archer D7b v1, names should be changed accordingly. Flash instructions under U-Boot, using UART ------------------------------------------ 1. Press "tpl" to stop autobooting and obtain U-Boot CLI access. 2. Setup ip addresses for U-Boot and your tftp server. 3. Issue below commands: tftpboot 0x81000000 openwrt-ath79-generic-tplink_archer-d7-v1-squashfs-sysupgrade.bin erase 0x9f020000 +f90000 cp.b 0x81000000 0x9f020000 0xf90000 reset Initramfs instructions under U-Boot for testing, using UART ---------------------------------------------------------- 1. Press "tpl" to stop autobooting and obtain U-Boot CLI access. 2. Setup ip addresses for U-Boot and your tftp server. 3. Issue below commands: tftpboot 0x81000000 openwrt-ath79-generic-tplink_archer-d7-v1-initramfs-kernel.bin bootm 0x81000000 4. Here you can backup the original firmware and/or flash the sysupgrade openwrt if you want Restore the original firmware ----------------------------- 0. Backup every partition using the OpenWrt web interface 1. Download the OEM firmware from the TP-Link website 2. Extract the bin file in a folder (eg. Archer_D7v1_1.6.0_0.9.1_up_boot(160216)_2016-02-16_15.55.48.bin) 3. Remove the U-Boot and the Broadcom image part from the file. Issue the following command: dd if="Archer_D7v1_1.6.0_0.9.1_up_boot(160216)_2016-02-16_15.55.48.bin" of="Archer_D7v1_1.6.0_0.9.1_up_boot(160216)_2016-02-16_15.55.48.bin.mod" skip=257 bs=512 count=31872 4. Double check the .mod file size. It must be 16318464 bytes. 5. Flash it using the OpenWrt web interface. Force the update if needed. WARNING: Remember to NOT keep settings. 5b. (Alternative to 5.) Flash it using the U-Boot and UART connection. Issue below commands in the U-Boot: tftpboot 0x81000000 Archer_D7v1_1.6.0_0.9.1_up_boot(160216)_2016-02-16_15.55.48.bin.mod erase 0x9f020000 +f90000 cp.b 0x81000000 0x9f020000 0xf90000 reset Signed-off-by: Davide Fioravanti <pantanastyle@gmail.com> [cosmetic DTS changes, remove TPLINK_HWREVADD := 0, do not use two phyXtpt at once, add missing buttons, minor commit message adjustments] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for TP-Link Archer C60 v3Adrian Schmutzler2020-03-188-12/+109
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TP-Link Archer C60 v3 is a dual-band AC1350 router, based on Qualcomm/Atheros QCA9561 + QCA9886. It seems to be identical to the v2 revision, except that it lacks a WPS LED and has different GPIO for amber WAN LED. Specification: - 775/650/258 MHz (CPU/DDR/AHB) - 64 MB of RAM (DDR2) - 8 MB of FLASH (SPI NOR) - 3T3R 2.4 GHz - 2T2R 5 GHz - 5x 10/100 Mbps Ethernet - 6x LED, 2x button - UART header on PCB Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed IP address 192.168.0.66 2. Download *-factory.bin image and rename it to tp_recovery.bin 3. Start a tftp server with the file tp_recovery.bin in its root directory 4. Turn off the router 5. Press and hold reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery While TFTP works for OpenWrt images, my device didn't accept the only available official firmware "Archer C60(EU)_V3.0_190115.bin". In contrast to earlier revisions (v2), the v3 contains the (same) MAC address twice, once in 0x1fa08 and again in 0x1fb08. While the partition-table on the device refers to the latter, the firmware image contains a different partition-table for that region: name device firmware factory-boot 0x00000-0x1fb00 0x00000-0x1fa00 default-mac 0x1fb00-0x1fd00 0x1fa00-0x1fc00 pin 0x1fd00-0x1fe00 0x1fc00-0x1fd00 product-info 0x1fe00-0x1ff00 0x1fd00-0x1ff00 device-id 0x1ff00-0x20000 0x1ff00-0x20000 While the MAC address is present twice, other data like the PIN isn't, so with the partitioning from the firmware image the PIN on the device would actually be outside of its partition. Consequently, the patch uses the MAC location from the device (which is the same as for the v2). Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: rename ubnt_bullet-m to ubnt_bullet-m-ar7241Russell Senior2020-03-185-9/+10
| | | | | | | | | | | Since there exists another variant of the Bullet M with AR7240 SoC under the same name, this patch introduces the SoC into the device name to be able to distinguish these variants. Signed-off-by: Russell Senior <russell@personaltelco.net> [add commit message, adjust model in DTS, fix 02_network and SUPPORTED_DEVICES] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: generalize ubnt_xm dtsi for ar7240 and ar7241Russell Senior2020-03-189-14/+23
| | | | | | | | | * Prepare to support the AR7240 variant of ubiquiti bullet m, by reorganizing the related dtsi files. * Distribute SOC variable across ubnt-xm devices. Signed-off-by: Russell Senior <russell@personaltelco.net>
* bcm27xx: enable THERMAL_WRITABLE_TRIPS on bcm2710 and bcm2711Bjørn Mork2020-03-184-0/+4
| | | | | | | | | | | | | The PoE hat supported on the RPi 3B+ and 4B comes with a rather loud fan, tripped in two steps by the brcmstb_thermal thermal_zone driver. Enabling writable trip points allow users to adjust the fan trip points according to their preferred temp/noise ratio. This setting is enabled on most other targets with similar thermal_zone controlled cooling devices. Signed-off-by: Bjørn Mork <bjorn@mork.no>
* ramips: do not add metadata to factory imagesMathias Kresin2020-03-171-2/+2
| | | | | | | The image metadata are openwrt specific and not required for factory images. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 5.4: enable JFFS2Mathias Kresin2020-03-171-1/+0
| | | | | | | | We do not build images with a jffs2 rootfs, but jffs2 is still used as filesystem for the rootfs_data. Fixes: e3eaf578082e ("lantiq: kernel 5.4: debloat kernel config") Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath79: fix execute bit for 02_network on mikrotik subtargetAdrian Schmutzler2020-03-171-0/+0
| | | | | | | | | | When creating the mikrotik subtarget, the execute bit on 02_network was not set. Fix it. Fixes: a66eee63368e ("ath79: add mikrotik subtarget") Reported-by: Christopher Hill <ch6574@gmail.com> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: get rid of BOARD_NAME for Mikrotik RouterBOARDAdrian Schmutzler2020-03-172-2/+7
| | | | | | | | | | | | | So far, specifying "BOARD_NAME := routerboard" is required by the upgrade code of Mikrotik NAND devices, as "sysupgrade-routerboard" is hardcoded in platform_do_upgrade_mikrotik_nand(). This patch replaces the latter with a grep for the name like it is already done in nand_upgrade_tar() in /lib/upgrade/nand.sh. By that, BOARD_NAME is obsolete now for this device. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ar71xx: remove hard-coded folder name from Mikrotik RB upgradeAdrian Schmutzler2020-03-171-1/+6
| | | | | | | | | | | | | | So far, specifying "BOARD_NAME := routerboard" is required by the upgrade code of Mikrotik NAND devices, as "sysupgrade-routerboard" is hardcoded in platform_do_upgrade_mikrotik_rb(). This patch replaces the latter with a grep for the name like it is already done in nand_upgrade_tar() in /lib/upgrade/nand.sh. This should enable upgrades from ar71xx to ath79 without setting BOARD_NAME for the latter. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add mikrotik subtargetRoger Pueyo Centelles2020-03-1724-67/+218
| | | | | | | | | | | | | | | | | This commit creates the ath79/mikrotik subtarget in order to support MikroTik devices based on Qualcomm Atheros MIPS SoCs. MikroTik devices need a couple of specific features: the split MiNOR firmware MTD format, which is not used by other devices, and the 4k sector erase size on SPI NOR storage, which can not be added to the ath79/generic and ath79/nand subtargets now. Additionally, the commit moves the two MikroTik devices already in the generic and nand subtargets to this new one. Tested on the RB922 board and the wAP AC router. Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* oxnas: enable sata on Pogoplug V3/ProSungbo Eo2020-03-173-3/+18
| | | | | | | | | Pogoplug V3/Pro has an interanl SATA port. To use it, DTS sata node should be enabled, and kmod-ata-oxnas-sata package needs to be installed. Fixes: FS#2542 Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* tegra: switch to kernel 5.4Tomasz Maciej Nowak2020-03-171-1/+1
| | | | | | | | | Build the latest kernel by default, since testing did not show any regressions. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [fix merge conflict in tegra/Makefile] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* tegra: refresh patches and kernel config for 5.4Tomasz Maciej Nowak2020-03-173-19/+35
| | | | | | | | | This commit also disables Trusted Foundations firmware support as this feature won't be used by any device. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [fix merge conflict in tegra/Makefile] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* tegra: copy kernel config and patches for 5.4Tomasz Maciej Nowak2020-03-173-0/+682
| | | | Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* kernel: move TEO governor to generic configTomasz Maciej Nowak2020-03-1713-12/+1
| | | | | | | | This new symbol popped up in few places. Disable it in generic config. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [fixed merge conflict in generic/config-5.4] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* mxs: fix user led for OLinuXino boardsMichael Heimpold2020-03-171-0/+61
| | | | | | | | | | More testing after kernel upgrade to 5.4 uncovered a regression: the user led is not present anymore due to a pin mux "collision" in device tree. A patch sent to upstream kernel was accepted now. Integrate this pending fix as platform specific patch so that user led is available again. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* zynq: switch to kernel 5.4Luis Araneda2020-03-171-1/+1
| | | | | | | | | Use kernel 5.4 by default compile-tested: all devices from target run-tested: Digilent Zybo Z7-20 Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: refresh kernel 5.4 configLuis Araneda2020-03-171-20/+30
| | | | | | By running make kernel_oldconfig and selecting relevant options Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: copy config from kernel 4.19 to 5.4Luis Araneda2020-03-171-0/+655
| | | | | | Refreshed kernel 4.19 config before copying the file Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* lantiq: kernel 5.4: debloat kernel configMathias Kresin2020-03-165-11/+8
| | | | | | | | | | | | | | | The etop driver is used by all targets except xrx200. Remove the UBIFS compression support for zlib and zstd from the xway subtarget. The hardware is EOL for a long time and it's unlikely to ever see a board shipped with an UBIFS using these compression methods. Remove the JFFS2 support. Support for jjfs2 images was dropped years ago. It shrinks the compressed kernel up to 130 KByte. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add Linux 5.4 support as testing kernel versionMathias Kresin2020-03-1640-366/+884
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Switch to the mainline Lantiq PCIe PHY driver and update the vr9.dtsi accordingly. The Lantiq IRQ SMP support added upstream required changes to the SoC dtsi as well. Following changes are made to the Lantiq kernel patches: 0005-lantiq_etop-pass-struct-device-to-DMA-API-functions.patch 0006-MIPS-lantiq-pass-struct-device-to-DMA-API-functions.patch applied upstream 0008-MIPS-lantiq-backport-old-timer-code.patch access_ok API update because it lost it's type (which was the first) parameter in upstream commit 96d4f267e40f95 ("Remove 'type' argument from access_ok() function") 0024-MIPS-lantiq-autoselect-soc-rev-matching-fw.patch merged into 0026-MIPS-lantiq-Add-GPHY-Firmware-loader.patch 0024-MIPS-lantiq-revert-DSA-switch-driver-PMU-clock-chang.patch revert upstream changes required for upstream xrx200 ethernet and xrx200 (DSA) switch driver but breaking our driver 0026-MIPS-lantiq-Add-GPHY-Firmware-loader.patch required for our driver but dropped upstream, add former upstream version 0028-NET-lantiq-various-etop-fixes.patch now has to use the phy_set_max_speed API instead of modifying phydev->supported. Also call ltq_dma_enable_irq() in ltq_etop_open() based on upstream commit cc973aecf0b054 ("MIPS: lantiq: Do not enable IRQs in dma open") Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: linux 5.4: remove support for the linux,mtd-name OF propertyMartin Blumenstingl2020-03-163-46/+0
| | | | | | | | This is referenced in two .dts but never actually used from userspace. Drop support for this property because it's not used and because it makes updating to Linux 5.4 harder (as the patch doesn't apply anymore). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: copy target to kernel 5.4Mathias Kresin2020-03-16195-0/+27082
| | | | | | | | | Duplicate kernel 4.19 config and patches for kernel 5.4. Duplicate the devicetree source files as well, they need kernel 5.4 specific adjustments. Signed-off-by: Mathias Kresin <dev@kresin.me>
* generic: make all phy drivers kernel 5.0 compatibleMathias Kresin2020-03-163-0/+21
| | | | | | | | It adjusts the code to upstream changes from the commit 3c1bcc8614db ("net: ethernet: Convert phydev advertize and supported from u32 to link mode") Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: vgv7510kw22: fix missing wirelessMathias Kresin2020-03-161-2/+2
| | | | | | | | | | | | | | | | | | | | For some reason pin 7 (gphy0_led1_pins) need to be set to output prior to loading the PCI driver. Otherwise the wireless doesn't appear on the PCI bus. Of course, it doesn't make much sense, since pin 7 is used to drive the LAN1 led. It can either be done by setting the pins function to GPHY or GPIO + direction output. However, the pinctrl driver doesn't provide a way to switch a pin to GPIO. It is done indirectly by the pinctrl driver at the time a GPIO is requested (requesting a GPIO always resets the function to GPIO). Do it via pinmux driver, as it is always loaded first. Use the GPHY function as it's the pins intended purpose for this board. Fixes: FS#2895 Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: remove maintainer variable from targetsPetr Štetiar2020-03-1634-40/+0
| | | | | | | | | | | | | There is no such role as target maintainer anymore, one should always send corresponding changes for the review and anyone from the commiters is allowed to merge them or eventually use the hand break and NACK them. Lets make it clear, that it is solely a community doing the maintenance tasks. Signed-off-by: Petr Štetiar <ynezz@true.cz> Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Piotr Dymacz <pepe2k@gmail.com>
* ipq40xx: 5.4: fix ethernet driverRobert Marko2020-03-161-29/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In 5.4 kernel old u32 array way of setting network features was dropped and linkmode is now the only way. So lets migrate the EDMA driver to support linkmode. Also, old get/set settings API for ethtool is also dropped so lets convert to new ksettings API while at it as it demands linkmode. Now, gigabit works properly as well as ethtool. Previously you would get this in ethtool: root@OpenWrt:/# ethtool eth1 Settings for eth1: Supports Wake-on: d Wake-on: d Current message level: 0x00000000 (0) Link detected: yes Now, features are properly advertised: root@OpenWrt:/# ethtool eth1 Settings for eth1: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: No Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 4 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Supports Wake-on: d Wake-on: d Current message level: 0x00000000 (0) Link detected: yes Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ipq40xx: 5.4: fix networking PHY driverRobert Marko2020-03-162-14/+3
| | | | | | | | In 5.4 kernel old u32 array way of setting network features was dropped and linkmode is now the only way. So lets migrate the PHY driver to support linkmode. Also, now in order for gigabit to work, PHY driver needs to advertise PHY_GBIT_FEATURES instead of PHY_BASIC_FEATURES Signed-off-by: Robert Marko <robert.marko@sartura.hr>
* ipq40xx: 5.4: fix of_get_mac_address obsolete usage OOPsPetr Štetiar2020-03-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of_get_mac_address returns valid pointer or ERR_PTR since 5.2 via commit d01f449c008a ("of_net: add NVMEM support to of_get_mac_address") so the patch fixes following OOPs on nbg6617: Unable to handle kernel paging request at virtual address ffffffed CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.4.24 #0 PC is at edma_axi_probe+0x444/0x1114 LR is at bus_find_device+0x88/0x9c Where the PC can be resolved to: >>> l *edma_axi_probe+0x444 0xc067be5c is in edma_axi_probe (./include/linux/string.h:378). >>> l *edma_axi_probe+0x43f 0xc067be57 is in edma_axi_probe (drivers/net/ethernet/qualcomm/essedma/edma_axi.c:936) Which leads to the following code fragment: 935 mac_addr = of_get_mac_address(pnp); 936 if (mac_addr) 937 memcpy(edma_netdev[idx_mac]->dev_addr, mac_addr, ETH_ALEN); Where using mac_addr=0xffffffed (-ENODEV) as source address in memcpy() is causing the OOPs. Acked-by: John Crispin <john@phrozen.org> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* sunxi: add testing 5.4 kernelAleksander Jan Bajkowski2020-03-161-0/+1
| | | | | | Add 5.4 as testing kernel. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* sunxi: move common options from subtargets into target kconfigAleksander Jan Bajkowski2020-03-164-100/+33
| | | | | | These new options are common for all subtargets and can be moved into target kconfig. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* sunxi: refresh config for all subtargetsAleksander Jan Bajkowski2020-03-163-4/+194
| | | | | | | | This was done by executing these command for all subtargets: $ time make -j9 kernel_oldconfig CONFIG_TARGET=subtarget Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* sunxi: remove old symbols from 5.4 kconfigAleksander Jan Bajkowski2020-03-162-14/+0
| | | | | | These options only exist earlier kernel versions. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* sunxi: remove options that are already in generic kconfigAleksander Jan Bajkowski2020-03-163-10/+0
| | | | | | These options are already definied in generic 5.4 kconfig. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* kernel: move disabled symbols into generic kconfigAleksander Jan Bajkowski2020-03-164-44/+54
| | | | | | Move some disabled kconfig options found in sunxi kconfig into generic. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* sunxi: make patches apply cleanly on 5.4Aleksander Jan Bajkowski2020-03-164-125/+3
| | | | | | | | These patches are already in mainline 5.4 kernel: * 010-v5.3-drivers-ata-ahci_sunxi-Increased-SATA-AHCI-DMA-TX-RX.patch * 101-arm64-dts-allwinner-a64-Enable-A64-timer-workaround.patch Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* sunxi: copy config and patches from 4.19 to 5.4Aleksander Jan Bajkowski2020-03-169-0/+995
| | | | Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* kernel: sort generic configurationAleksander Jan Bajkowski2020-03-162-20/+14
| | | | | | | | | | | | This was done by executing these commands: $ ./scripts/kconfig.pl '+' target/linux/generic/config-4.19 /dev/null > target/linux/generic/config-4.19-new $ mv target/linux/generic/config-4.19-new target/linux/generic/config-4.19 $ ./scripts/kconfig.pl '+' target/linux/generic/config-5.4 /dev/null > target/linux/generic/config-5.4-new $ mv target/linux/generic/config-5.4-new target/linux/generic/config-5.4 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* x86: switch to 5.4 kernelPetr Štetiar2020-03-161-1/+1
| | | | | | | Seems to be working fine on apu2 and QEMU, it's 99.9% upstream stuff anyway. Lets start wider userbase testing. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* imx6: switch to 5.4 kernelPetr Štetiar2020-03-161-1/+1
| | | | | | | | | Seems to be working fine, it's 99.9% upstream stuff anyway. Lets start wider userbase testing. Cc: Tim Harvey <tharvey@gateworks.com> Cc: Koen Vandeputte <koen.vandeputte@ncentric.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* bcm27xx: sync 5.4 patches with RPi FoundationÁlvaro Fernández Rojas2020-03-16288-6603/+5992
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: switch to 5.4 kernelPetr Štetiar2020-03-161-2/+1
| | | | | | | | | Been running it for a few days on RPi0W PMS sensor node and on RPi4. Lets start wider userbase testing. Cc: Stijn Tintel <stijn@linux-ipv6.be> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ipq806x: read both WG2600HP MAC addresses from flashYanase Yuki2020-03-161-1/+1
| | | | | | | | | WG2600HP has its WLAN MAC addresses at PRODUCTDATA 0xc and 0x12, so use them both directly. Signed-off-by: Yanase Yuki <dev@zpc.sakura.ne.jp> [commit title/message clarification] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq806x: remove useless case within default case for upgradeAdrian Schmutzler2020-03-161-1/+0
| | | | | | | The default case will catch anything left, there is no need to explicitly add any device to it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 11:41:48 +0000