aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* zynq: switch to kernel 5.10Luis Araneda2021-10-171-1/+1
| | | | | | | | | Use kernel 5.10 by default compile-tested: all devices from target (wth ALL_KMODS) run-tested: Digilent Zybo Z7-20 Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: kernel: update config for 5.10Luis Araneda2021-10-171-11/+13
| | | | | | Update config with make kernel_oldconfig Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: kernel: copy config from 5.4 to 5.10Luis Araneda2021-10-171-0/+550
| | | | Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: kernel: remove wireless extensions symbolsLuis Araneda2021-10-171-3/+0
| | | | | | | | | | | | This fixes compilation of several wireless drivers that require support for the old wireless extension to work. One example is kmod-hermes. The symbols are set to "y" on generic configuration. But they were wrongly disabled on the target-specific configuration. Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* zynq: kernel: refresh configLuis Araneda2021-10-171-94/+2
| | | | | | | | using "make kernel_oldconfig" Several configs are now part of generic Signed-off-by: Luis Araneda <luaraneda@gmail.com>
* buildsystem: add CONFIG_SECCOMPFlorian Eckert2021-10-163-3/+14
| | | | | | | | | | | | | | | | | | | | | Until now, this feature was switched on via the kernel configuration option KERNEL_SECCOMP. The follwing change a7f794cd2aa104fdbd4c6e38f9b76373bf9b96e1 now requires that the package procd-seccomp must also enabled for buildinmg. However, this is not the case we have no dependency and the imagebuilder cannot build the image, because of the implicit package selection. This change adds a new configuration option CONFIG_SECCOMP. The new option has the same behaviour as the configuration option CONFIG_SELINUX. If the CONFIG_SECCOMP is selected then the package procd-seccomp and KERNEL_SECCOMP is enabled for this build. Signed-off-by: Florian Eckert <fe@dev.tdt.de> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: add EEPROM data for BPi-R64 2.4GHz wmacDaniel Golle2021-10-151-0/+31
| | | | | | | | | | | EEPROM data extracted from vendor image found at http://forum.banana-pi.org/t/bpi-r64-mt7622-mac80211-wifi-driver/10246/77 http://forum.banana-pi.org/uploads/short-url/jworbyBYpvrw9VQ2sx92B9z6DWS.bin MAC address in the EEPROM has been zero'd which results in random address on boot. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: backport a rewrite of the mips eBPF JIT implementationFelix Fietkau2021-10-1422-10/+9497
| | | | | | | This adds support for eBPF JIT for 32 bit targets and significantly improves correctness. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* hostapd: ubus: add BSS transtiton request methodDavid Bauer2021-10-131-40/+112
| | | | | | | | | | | | | | | | | | | | | | | | | | | The existing wnm_disassoc_imminent ubus method only supports issuing a bss transition request with the disassoc imminent flag set. For use-cases, where the client is requested to roam to another BSS without a pending disassoc, this existing method is not suitable. Add a new bss_transition_request ubus method, which provides a more universal way to dispatch a transition request. It takes the following arguments: Required: addr: String - MAC-address of the STA to send the request to (colon-seperated) Optional: abridged - Bool - Indicates if the abridged flag is set disassociation_imminent: Bool - Whether or not the disassoc_imminent flag is set disassociation_timer: I32 - number of TBTTs after which the client will be disassociated validity_period: I32 - number of TBTTs after which the beacon candidate list (if included) will be invalid neighbors: blob-array - Array of strings containing neighbor reports as hex-string Signed-off-by: David Bauer <mail@david-bauer.net>
* hostapd: ubus: add notification for BSS transition responseDavid Bauer2021-10-133-0/+74
| | | | | | | | | To allow steering daemons to be aware of the STA-decided transition target, publish WNM transition responses to ubus. This way, steerings daemons can learn about STA-chosen targets and send a better selection of transition candidates. Signed-off-by: David Bauer <mail@david-bauer.net>
* tools/fakeroot: explicitly pass CPP variableFelix Fietkau2021-10-131-1/+2
| | | | | | | | | For some reason, the generated configure script fails to properly set up the internal preprocessor command variable, causing the host OS check for Darwin to fail after the last update. Explicitly setting CPP fixes this issue Signed-off-by: Felix Fietkau <nbd@nbd.name>
* x86/64: enable MMIO_CMDLINE_DEVICES for firecracker supportPaul Spooren2021-10-121-0/+1
| | | | | | | | | | | | | This Kernel option allows to run OpenWrt witin a `firecracker` micro VM. Firecracker is a KVM-based tool for superfast booting VMs on x86_64 and aarch64. It makes rootfs available to the guest as a virtio-mmio device and passes its address via the kernel cmdline. A kernel without CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES will not recognize the rootfs virtio-mmio device. Suggested-by: Packet Please <pktpls@systemli.org> Signed-off-by: Paul Spooren <mail@aparcar.org>
* armvirt: enable MMIO_CMDLINE_DEVICES for firecracker supportPaul Spooren2021-10-121-0/+1
| | | | | | | | | | | | | This Kernel option allows to run OpenWrt witin a `firecracker` micro VM. Firecracker is a KVM-based tool for superfast booting VMs on x86_64 and aarch64. It makes rootfs available to the guest as a virtio-mmio device and passes its address via the kernel cmdline. A kernel without CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES will not recognize the rootfs virtio-mmio device. Suggested-by: Packet Please <pktpls@systemli.org> Signed-off-by: Paul Spooren <mail@aparcar.org>
* procd: update to git HEADDaniel Golle2021-10-131-4/+4
| | | | | | | | | | | | | | 97bcdcf uxc: fix segfault caused by use-after-free 6398e05 uxc: don't free the stack 324ebd0 jail: fs: add support for asymmetric mount bind c44ab7f jail: netifd: generate netifd uci config and mount it 82dd390 jail: make use of per-container netifd via ubus The new per-jail netifd is now configured by filtering the host network configuration. As libuci is used for that, procd-ujail now depends on libuci. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* netifd: update to git HEADDaniel Golle2021-10-131-3/+3
| | | | | | | be8cd8f interface: don't fork() to start jail interface 7a048bd interface, ubus: rework netns up/down Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mt76: update to the latest versionFelix Fietkau2021-10-121-3/+3
| | | | | | 83598c2e872f mt76: avoid possible infinite loop in mt76_tx_status_check Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mt76: update to the latest versionFelix Fietkau2021-10-111-2/+2
| | | | | | 1af0242d1241 mt76: mt7915: replace a 64 bit divsion with a call to div_u64_rem Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mac80211: remove kcov bits from TWT backport patchFelix Fietkau2021-10-111-5/+1
| | | | | | | Our backports version does not have support for kcov in mac80211 Fixes build errors on some platforms Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mt76: update to the latest versionFelix Fietkau2021-10-112-209/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 74dedf9352c5 mt76: mt7615: fix skb use-after-free on mac reset 7201290eda43 mt76: mt7921: Fix out of order process by invalid event pkt ca1b57e9971a mt76: mt7915: add a missing HT flag for GI parsing 4932c5d80153 of: net: pass the dst buffer to of_get_mac_address() 51d9eb3e6f52 mt76: mt7915: fix endianness warnings in mu radiotap 833ca13014ab mt76: mt7921: Add mt7922 support 8f8ed44d026e mt76: mt7915: add control knobs for thermal throttling 16f18bab6b11 mt76: mt7915: send EAPOL frames at lowest rate affea639c586 mt76: mt7921: send EAPOL frames at lowest rate ac00fed412d4 mt76: mt7915: fix potential overflow of eeprom page index [update] e576ddb76dfa mt76: mt7915: switch proper tx arbiter mode in testmode 222847c3d5eb mt76: mt7915: fix bit fields for HT rate idx d04814366c83 mt76: add support for setting mcast rate 4602acc9271a mt76: mt7921: fix dma hang in rmmod ec2cf3bf96fd mt76: connac: fix GTK rekey offload failure on WPA mixed mode 2fdb9d621431 mt76: connac: add support for limiting to maximum regulatory Tx power 489ace63d42c mt76: mt7921: get rid of monitor_vif 22da8d28fcc8 mt76: mt7921: get rid of mt7921_mac_set_beacon_filter c94130519786 mt76: mt7921: introduce mt7921_mcu_set_beacon_filter utility routine 51cff39d7ad3 mt76: overwrite default reg_ops if necessary da11c1c6edef mt76: mt7615: move mt7615_mcu_set_p2p_oppps in mt76_connac module 47f50b0aa4b8 mt76: mt7921: report HE MU radiotap 4f48ba4b0254 mt76: mt7915: checkpatch cleanup bc7ee7d7bdea mt76: mt7915: add HE-LTF into fixed rate command 6a19e40820aa mt76: mt7921: continue to probe driver when fw already downloaded 8b3d8e2de084 mt76: mt7921: fix firmware usage of RA info using legacy rates 17305a54b166 mt76: mt7921: fix kernel warning from cfg80211_calculate_bitrate 801c15577293 mt76: mt7921: fix endianness warnings in mt7921_mac_decode_he_mu_radiotap 0182a5b99a7a mt76: mt7915: update mac timing settings e2ee9d0a33ed mt76: use IEEE80211_OFFLOAD_ENCAP_ENABLED instead of MT_DRV_AMSDU_OFFLOAD fa6504aceb4f Revert "mt76: mt7915: checkpatch cleanup" 56b842b72a72 mt76: mt7915: fix wmm index on DBDC cards 8044311f5de5 mt76: mt7915: fix potential NPE in TXS processing 28da4baec7c5 mt76: mt7915: fix he_mcs capabilities for 160mhz f7088ebe7452 mt76: mt7915: add LED support ee019046284d mt76: mt7915: introduce bss coloring support 9848094e4bb5 mt76: mt7921: Fix fall-through warning for Clang 5710d0643418 mt76: add a bound check in mt76_calculate_default_rate() a509cf2b654e mt76: mt7921: move mt7921_queue_rx_skb to mac.c 5a0f2382fcfe mt76: mt7915: rework debugfs queue info 62ffc31f4d7b mt76: mt7915: rename debugfs tx-queues 4750b5c918e5 mt76: mt7921: always wake device if necessary in debugfs ac6adf74b3f2 mt76: mt7921: update mib counters dumping phy stats eb75b9266ce6 net:wireless:mt76: fix boolreturn.cocci warnings d7c4698435b3 mt76: mt7921: fix the inconsistent state between bind and unbind 9dcfba3169c4 mt76: switch from 'pci_' to 'dma_' API d8b5e42c9a73 mt76: fill boottime_ns in Rx path 8ee6446075f2 mt76: disable BH around napi_schedule() calls e17d730bf2f6 mt76: mt7915: add LED support [update to v3] 80fe40c9457e mt76: mt7915: enable configured beacon tx rate c8f0d1d81d05 mt76: mt7915: fix hwmon temp sensor mem use-after-free 3b9ba7e02076 mt76: mt7615: fix hwmon temp sensor mem use-after-free 5e82eceb45cb mt76: mt7921: start reworking tx rate reporting eb66b5c9ff77 mt76: mt7921: add support for tx status reporting c8010f170e76 mt76: mt7921: report tx rate directly from tx status 4dc7f3db572b mt76: mt7921: remove mcu rate reporting code db89c6f86724 mt76: mt7921: remove mt7921_sta_stats 6bb8b4267dbe mt76: move spin_lock_bh to spin_lock in tasklet 0eacf41985da mt76: mt7915: honor all possible error conditions in mt7915_mcu_init() 4dfff296ee6e mt76: mt7915: fix possible infinite loop release semaphore 537ed88dd2d0 mt76: mt7921: robustify hardware initialization flow e0b846159221 mt76: mt7921: fix retrying release semaphore without end c55dedcea268 mt76: mt7915: add ethtool stats support d1d5e8cd3a3e mt76: mt7915: add tx stats gathered from tx-status callbacks 1687189d68b7 mt76: mt7915: add some per-station tx stats to ethtool f4dde5f765af mt76: mt7915: add tx mu/su counters to mib 9752bf0643c9 mt76: mt7915: add more MIB registers 4727415017c9 mt76: mt7915: add mib counters to ethtool stats 4ca80a749e7f mt76: connac: set 6G phymode in mt76_connac_get_phy_mode{,v2} 3f2a5d39631e mt76: connac: enable 6GHz band for hw scan 817a41826bd7 mt76: connac: add 6GHz support to mt76_connac_mcu_set_channel_domain a6ab81c21080 mt76: connac: set 6G phymode in single-sku support ca4f47028a44 mt76: connac: add 6GHz support to mt76_connac_mcu_sta_tlv d2e192ea81e2 mt76: connac: add 6GHz support to mt76_connac_mcu_uni_add_bss c3dd12b4c8ae mt76: connac: enable hw amsdu @ 6GHz 91ed2b256c20 mt76: add 6GHz support de8c4f92621f mt76: mt7921: add 6GHz support f143aedc1d57 mt76: introduce packet_id idr bcc8d9e03a5d mt76: remove mt76_wcid pointer from mt76_tx_status_check signature ccbd84763153 mt76: substitute sk_buff_head status_list with spinlock_t status_lock 69bb59df894c mt76: schedule status timeout at dma completion 03a992645310 mt76: support reading EEPROM data embedded in fdt 75615480b3fe mt76: introduce __mt76_mcu_send_firmware routine e8e2eae41f94 mt76: drop MCU header size from buffer size in __mt76_mcu_send_firmware 4c455e8b1a20 mt76: mt7915: introduce __mt7915_get_tsf routine 9d49c611a2d7 mt76: mt7915: introduce mt7915_mcu_twt_agrt_update mcu command f44ca79c9aed mt76: mt7915: introduce mt7915_mac_add_twt_setup routine 2f9555a2f18f mt76: mt7915: enable twt responder capability 440e2db8d541 mt76: mt7915: add twt_stats knob in debugfs eb5f640f8afa mt76: debugfs: improve queue node readability 53d7eb3b4884 mt76: mt7615: fix monitor mode tear down crash 2aa3d4414826 mt76: mt7921: add delay config for sched scan 47e8e96e8e4d mt76: use a separate CCMP PN receive counter for management frames 5560b08f8e2d mt76: do not access 802.11 header in ccmp check for 802.3 rx skbs Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mac80211: backport AP mode TWT supportFelix Fietkau2021-10-113-1/+693
| | | | | | Required for an upcoming mt76 update Signed-off-by: Felix Fietkau <nbd@nbd.name>
* scripts/rstrip.sh: do not strip .o files with STRIP_KMODFelix Fietkau2021-10-111-0/+1
| | | | | | Fixes packaging of eBPF modules Signed-off-by: Felix Fietkau <nbd@nbd.name>
* tools/ccache: update to 4.4.2Rosen Penev2021-10-102-3/+4
| | | | | | | | Refreshed patch. Disable hiredis backend since it seems to default to it now. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* Revert "gpio-cdev: add nu801 userspace driver"Christian Lamparter2021-10-104-58/+2
| | | | | | | | | | | This reverts commit f536f5ebddd9c532a08ac4a9be3ef0c02f7bfeb8. As Hauke commented, this causes builder failures on 5.4 kernels. This revert includes changes to the mx100 kernel modules dependency as well as the uci led definitions. Tested-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* tools/meson: fix usage with SDKRosen Penev2021-10-102-2/+2
| | | | | | | The python path cannot be embedded in the meson binary as it changes with the SDK. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ipq40xx: use zImage for GL.iNet GL-B1300, GL-S1300 to shrink below 4096kSzabolcs Hubai2021-10-101-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | In the "ipq40xx: switch to Kernel 5.10" discussion at GitHub, Adrian noted [0] that these GL.iNet Conexa series devices, GL-B1300 and GL-S1300 failed their image generation [1] as their gzipped uImage kernel went above 4096k. While notifying the vendor about this problem [2], I tested all U-Boot releases from GL.iNet: - they really fail to boot kernel above 4096k - they don't support lzma: "Unimplemented compression type 3" - but they boot zImage Using zImage (xz compression) the kernel is 2909k which is more than a megabyte away from the KERNEL_SIZE := 4096k limit. The gzip compressed version would be 4116k. [0]: https://github.com/openwrt/openwrt/pull/4620#issuecomment-932765776 [1]: commit 7b1fa276f5a2 ("ipq40xx: add testing support for kernel 5.10") [2]: https://forum.gl-inet.com/t/ipq40xx-kernel-size-and-u-boot-v5-10-is-too-big-for-4-mb/17619 Signed-off-by: Szabolcs Hubai <szab.hu@gmail.com>
* x86: add support for Meraki MX100Chris Blake2021-10-106-0/+369
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit will add support for the Meraki MX100 in OpenWRT. Specs: * CPU: Intel Xeon E3-1200 Series 1.5GHz 2C/4T * Memory: 4GB DDR3 1600 ECC * Storage: 1GB USB NAND, 1TB SATA HDD * Wireless: None * Wired: 10x 1Gb RJ45, 2x 1Gb SFP UART: The UART header is named CONN11 and is found in the center of the mainboard. The pinout from Pin 1 (marked with a black triangle) to pin 4 is below: Pin 1: VCC Pin 2: TX Pin 3: RX Pin 4: GND Note that VCC is not required for UART on this device. Booting: 1. Flash/burn one of the images from this repo to a flash drive. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Hook up UART to the MX100, plug in the USB drive, and then power up the device. 4. At the BIOS prompt, quickly press F7 and then scroll to the Save & Exit tab. 5. Scroll down to Boot Override, and select the UEFI entry for your jumpdrive. Note: UEFI booting will fail if the SATA cable for the HDD is plugged in. The issue is explained under the Flashing instructions. Flashing: 1. Ensure the MX100 is powered down, and not plugged into power. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Using the Mini USB female port found by the SATA port on the motherboard, flash one of the images to the system. Example: `dd if=image of=/dev/sdb conv=fdatasync` where sdb is the USB device for the MX100's NAND. 4. Unplug the Mini USB, hook up UART to the MX100, and then power up the device. 5. At the BIOS prompt, quickly press F7 and then scroll to the Boot tab. 6. Change the boot order and set UEFI: USB DISK 2.0 as first, and USB DISK 2.0 as second. Disable the other boot options. 7. Go to Save & Exit, and then select Save Changes and Reset Note that OpenWRT will fail to boot in UEFI mode when the SATA hard drive is plugged in. To fix this, boot with the SATA disk unplugged and then run the following command: `sed -i "s|hd0,gpt1|hd1,gpt1|g" boot/grub/grub.cfg` Once the above is ran, OpenWRT will boot when the HDD is plugged into SATA. The reason this happens is the UEFI implementation for the MX100 will always set anything on SATA to HD0 instead of the onboard USB storage, so we have to accomidate it since OpenWRT's GRUB does not support detecting a boot disk via UUID. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* gpio-cdev: add nu801 userspace driverChris Blake2021-10-102-0/+56
| | | | | | | | | | | This adds a userspace interpretation of the nu801 driver used by Meraki hardware. Previously this was a driver that was added per target, but as multiple targets now have this driver, we should move to something that can be shared by all targets since no driver exists upstream. Co-developed-by: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: disable and move kernel CONFIG_ symbolsChristian Lamparter2021-10-102-31/+17
| | | | | | | | | | | | | | | | | try to reduce the kernel size by disabling and moving options from the common kernel configuration to the SATA target that doesn't have the constraints. For NAND this has become necessary because as with 5.10 some devices outgrew their kernels. Though, in my tests this didn't help much: just a smidgen over 100kib was saved on the uncompressed kernel. ... running make kernel_oldconfig also removed some other config symbols, mostly those that already set from elsewhere or became obsolete in the meantime. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: disable MX60(W) due to kernel sizeChristian Lamparter2021-10-101-0/+1
| | | | | | | | disables the MX60(W) from being built by the builders for now. But there's an effort to bring it back: <https://github.com/openwrt/openwrt/pull/4617> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* gemini: splash banner on framebuffer consoleLinus Walleij2021-10-101-0/+9
| | | | | | | | | The D-Link DIR-685 has a small screen with a framebuffer console, so if we have this, when we start, display the banner on this framebuffer console so the user know they are running OpenWRT as root filesystem. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* apm821xx: WNDAP620 + WNDAP660: reorganize partitions for 5.10Christian Lamparter2021-10-102-6/+9
| | | | | | | | | | | | | | | | | | | | | | Due to 5.10 increased kernel size, the current 4MiB-ish kernel partition got too small. Luckily, netgear's uboot environment is setup to read 0x60000 bytes from the kernel partition location. ... While at it: also do some cleanups in the DTS in there. The original (re-)installation described in commit d82d84694e60 ("apm821xx: add support for the Netgear WNDAP620 and WNDAP660") seemed to be still working for now. What I noticed though is that the bigger initramfs images needed to use a different destination address (1000000) to prevent it overwriting itself during decompression. i.e: # tftp 1000000 openwrt-...-wndap620-initramfs-kernel.bin # bootm However, in case of the WNDAP620+660 the factory.img image can be written directly to the flash through uboot. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: switch to Kernel 5.10Paul Spooren2021-10-101-2/+1
| | | | Signed-off-by: Paul Spooren <mail@aparcar.org>
* apm821xx: move CONFIG_DMA* to the generic apm821xx configChristian Lamparter2021-10-103-31/+8
| | | | | | | | | | | | Both NAND and SATA targets need the DMA engine in one way or another. Due to a kernel config refresh various existing symbols got removed from the apm821xx main config file as well. (That being said, they are still included because the built-in crpyto4xx depends on these.) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* build: prereq detect Python 3.10 for `python3` binaryPaul Spooren2021-10-101-2/+2
| | | | | | | | | | While the binary `python3.10` is correctly detected by the build system the default `python3` binary is currently not detected if pointing to a Python 3.10 installation. Fix this by extending the grep regex. Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: bump 5.4 to 5.4.152John Audia2021-10-102-7/+7
| | | | | | All patches automatically rebased. Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.4 to 5.4.151John Audia2021-10-104-11/+11
| | | | | | All patches automatically rebased. Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.10 to 5.10.72John Audia2021-10-107-23/+23
| | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B Run-tested: bcm2711/RPi4B Signed-off-by: John Audia <graysky@archlinux.us>
* kernel: bump 5.10 to 5.10.71John Audia2021-10-1012-22/+22
| | | | | | | | | | All patches automatically rebased. Build system: x86_64 Build-tested: bcm2711/RPi4B, ipq806x/R7800 Run-tested: bcm2711/RPi4B, ipq806x/R7800 Signed-off-by: John Audia <graysky@archlinux.us>
* rockchip: rename "Rock Pi 4" to "Rock Pi 4A"Adrian Schmutzler2021-10-104-34/+5
| | | | | | | | | | | | Kernel has added the different variants of the Rock Pi 4 in commit b5edb0467370 ("arm64: dts: rockchip: Mark rock-pi-4 as rock-pi-4a dts"). The former Rock Pi 4 is now Rock Pi 4A. For compatibility with kernel 5.4, this rename has been held back so far. Having switched to kernel 5.10 now, we can finally apply it in our tree as well. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* rockchip: switch to kernel 5.10Adrian Schmutzler2021-10-101-2/+1
| | | | | | | This target has testing support for more than half a year now. Time to switch. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: drop support for mtd-mac-addressAnsuel Smith2021-10-096-228/+16
| | | | | | | | Now that we have fully switched to nvmem interface we can drop the use of mtd-mac-address patches as it's not used anymore and the new nvmem implementation should be used for any new device. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* mvebu: mochabin: correct LED labels in DTSRobert Marko2021-10-091-9/+9
| | | | | | | | | | LED labels got reversed by accident, so fix it to the usual color:led_name format. Fixes: 78cf3e53b1f4 ("mvebu: add Globalscale MOCHAbin") Signed-off-by: Robert Marko <robert.marko@sartura.hr> [add Fixes:] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kirkwood: switch to kernel 5.10Adrian Schmutzler2021-10-091-2/+1
| | | | | | | This target has testing support for more than half a year now. Time to switch. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* oxnas: switch to Linux 5.10Daniel Golle2021-10-0913-1356/+1
| | | | | | | Linux 5.10 has been there as testing kernel for a while now. Do the switch and drop config and patches for Linux 5.4. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* mediatek: enable configfs for DT overlay on mt7622 and mt7623Daniel Golle2021-10-092-0/+5
| | | | | | | | | Enable kernel options to allow loading device tree overlay via configfs at runtime. This is useful for devboards like the BPi-R2 and BPi-R64 which got RasbPi-compatible 40-pin GPIO header which allow all sorts of extensions. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* realtek: add legacy realtek GPIO driver for rtl9300 supportBirger Koblitz2021-10-094-0/+507
| | | | | | | The otto GPIO driver does not work with rtl9300 SoCs. Add the legacy driver again and use that by default in the 9300 .dtsi Signed-off-by: Birger Koblitz <git@birger-koblitz.de>
* realtek: enable Aquantia PHY supportBirger Koblitz2021-10-091-0/+1
| | | | | | Enables Aquantia PHY support in the kernel Signed-off-by: Birger Koblitz <git@birger-koblitz.de>
* realtek: Fix bug when accessing external PHYs on SoCs older than Revision CBirger Koblitz2021-10-091-3/+22
| | | | | | | | | | RTL8393 SoCs older than Revision C hang on accesses to PHYs with PHY address larger or equal to the CPU-port (52). This will make scanning the MDIO bus hang forever. Since the RTL8390 platform does not support more than 52 PHYs, return -EIO for phy addresses >= 52. Note that the RTL8390 family of SoCs has a fixed mapping between port number and PHY-address. Signed-off-by: Birger Koblitz <git@birger-koblitz.de>
* realtek: cleanup PHY driverBirger Koblitz2021-10-091-8/+6
| | | | | | Removes unnecessary output from the RTL PHY drivers. Signed-off-by: Birger Koblitz <git@birger-koblitz.de>
* realtek: Add debugfs support for RTL9300Birger Koblitz2021-10-092-1/+130
| | | | | | Adds support for debugfs on RTL9300, in particular the drop counters. Signed-off-by: Birger Koblitz <git@birger-koblitz.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 23:43:55 +0000