aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ar71xx: fix ath79/rb4xx IRQ initialization on kernel 4.14W. Michael Petullo2019-07-031-1/+1
| | | | | | | | | | | | Apply the same approach as in commit 3b53d6fdbc24 ("ar71xx: fix pci irq init on kernel 4.14") to fix IRQ initialization for ath79-based chipsets on rb4xx. Ref: PR#2182 Acked-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Signed-off-by: W. Michael Petullo <mike@flyn.org> [commit ref fix] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: Use -v1 suffix for TP-Link WDR3600/4300Adrian Schmutzler2019-07-035-14/+14
| | | | | | | | | | | | | | | In ath79, identifiers tplink_tl-wdr3600 and tplink_tl-wdr4300 have been used while most other TP-Link devices include the revision. Although there actually is only one major revision of these devices, they bear the revision on their bottom (v1.x). TP-Link also refers to the devices as V1 on its web page. This patch thus adds -v1 to both so it is more consistent with other devices and with what you would expect from reading the on-device sticker and the support pages. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* scripts: time.pl: Don't print the time on stderrAlban Bedel2019-07-031-1/+1
| | | | | | | | | Having the build time written on stderr make it appear with V=w although it is not an error or warning. Just write the time on stdout to have it part of the build log like all the rest, but not clutter the output when only warnings and errors should be shown. Signed-off-by: Alban Bedel <albeu@free.fr>
* lua5.3: stage Lua headers in proper locationJo-Philipp Wich2019-07-031-4/+5
| | | | | | | | | | Fix wrong paths in InstallDev which cause Lua 5.3 headers to be staged in /usr/include/, overwriting Lua 5.1 headers and leading to widespread build failures in all Lua related packages. Fixes: FS#2348 Fixes: 6b161bb8d5 ("lua5.3: package Lua 5.3 version") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* wireguard: bump to 0.0.20190702Jason A. Donenfeld2019-07-021-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * curve25519: not all linkers support bmi2 and adx This should allow WireGuard to build on older toolchains. * global: switch to coarse ktime Our prior use of fast ktime before meant that sometimes, depending on how broken the motherboard was, we'd wind up calling into the HPET slow path. Here we move to coarse ktime which is always super speedy. In the process we had to fix the resolution of the clock, as well as introduce a new interface for it, landing in 5.3. Older kernels fall back to a fast-enough mechanism based on jiffies. https://lore.kernel.org/lkml/tip-e3ff9c3678b4d80e22d2557b68726174578eaf52@git.kernel.org/ https://lore.kernel.org/lkml/20190621203249.3909-3-Jason@zx2c4.com/ * netlink: cast struct over cb->args for type safety This follow recent upstream changes such as: https://lore.kernel.org/lkml/20190628144022.31376-1-Jason@zx2c4.com/ * peer: use LIST_HEAD macro Style nit. * receive: queue dead packets to napi queue instead of empty rx_queue This mitigates a WARN_ON being triggered by the workqueue code. It was quite hard to trigger, except sporadically, or reliably with a PC Engines ALIX, an extremely slow board with an AMD LX800 that Ryan Whelan of Axatrax was kind enough to mail me. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* iptables: update to 1.8.3Deng Qingfang2019-07-028-170/+28
| | | | | | | | | | | | | | | | | | | | | Update iptables to 1.8.3 ChangeLog: https://netfilter.org/projects/iptables/files/changes-iptables-1.8.3.txt Removed upstream patches: - 001-extensions_format-security_fixes_in_libip.patch - 002-include_fix_build_with_kernel_headers_before_4_2.patch - 003-ebtables-vlan-fix_userspace_kernel_headers_collision.patch Altered patches: - 200-configurable_builtin.patch - 600-shared-libext.patch No notable size changes Signed-off-by: Deng Qingfang <dengqf6@mail2.sysu.edu.cn> Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> [lipibtc ABI_VERSION fix]
* Make linux kernel builds reproducible when BUILDBOT selectedAlexander Couzens2019-07-021-0/+2
| | | | | | | | | | | The linux kernel is not reproducible because the build user and domain is included into the kernel. Set the build user to `builder` and build domain to buildhost. It's also possible to build reproducible builds by setting KERNEL_BUILD_USER KERNEL_BUILD_DOMAIN to static values. Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* ramips: add support for TP-Link TL-WR841n v14Alexander Müller2019-07-024-0/+155
| | | | | | | | | | | | | | | | | | | | | | TP-Link TL-WR841n v14 is a router based on MediaTek MT7628N. - MediaTek MT7628NN - 32 MB of RAM - 4 MB of FLASH - 2T2R 2.4 GHz - 5x 10/100 Mbps Ethernet Installation: - copy the 'openwrt-ramips-mt76x8-tl-wr841n-v14-squashfs-tftp-recovery.bin' file to your tftp server root and rename it to 'tp_recovery.bin'. - configure your PC running the TFTP server with the static IP address 192.168.0.66/24 - push the reset button and plug in the power connector. Wait until the orange led starts blinking (~6sec) Signed-off-by: Alexander Müller <donothingloop@gmail.com> Signed-off-by: Alexander Couzens <lynxis@fe80.eu> [small modifications gpio-hog]
* ramips/leds: use devicetree alias led_wlanAlexander Couzens2019-07-021-0/+4
| | | | | | | | | | | | | | | | | | | | | | Similiar to the lantiq target use a dts alias to define the wlan led instead of static mapping in /etc/board.d/01_leds. Reduce code duplication. A device tree must define the alias "led-wlan" similiar to "led-boot". / { aliases { led-wlan = &led_wlan; }; [..] led_wlan: wlan { label = "tl-wr841n-v14:green:wlan"; gpios = <&gpio1 9 GPIO_ACTIVE_LOW>; }; }; Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* scripts/feeds: add src-include methodBjørn Mork2019-07-011-11/+26
| | | | | | | | | | | | The src-include method allows recursive inclusion of feeds.conf snippets. This can for example be used for adding static local feeds to feeds.conf.default without ever having to update the local feeds.conf: src-include defaults feeds.conf.default src-link custom /usr/local/src/lede/custom Signed-off-by: Bjørn Mork <bjorn@mork.no>
* gemini: Add StorLink SL93512r imagesLinus Walleij2019-07-011-7/+17
| | | | | | | | | | | This adds image generation for the StorLink reference design SL93512r. This board is now supported upstream in kernel v4.19. As this image structure is identical to SQ201 and Raidsonic, we simply refer to this as "storlink-reference" from now on. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* gemini: Drop switch kmod and swconfigLinus Walleij2019-07-011-1/+0
| | | | | | | | | The DIR-685 needs this module compiled in for safety (it is facing the LAN ports) and it is now (as of kernel v4.19) using the DSA switch architecture so swconfig is not needed. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* lua5.3: drop unwanted & unneeded PROVIDESRafał Miłecki2019-06-301-2/+0
| | | | | | | | | | The plan for packaging Lua is to have "lua5.1" and "lua5.3" packages with only the first one having "lua" alias (PROVIDES) for backward compatibility with existing packages. Putting PROVIDES in lua5.3 was a copy & paste mistake. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* base-files: add network_get_uptime() to /lib/functions/network.shFlorian Eckert2019-06-292-1/+6
| | | | | | Add missing ubus api call for uptime value. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* mvebu: add initial support for uDPU boardVladimir Vid2019-06-284-0/+188
| | | | | | | | | | | | | | | | | | | This adds initial support for micro-DPU (uDPU) board which is based on Armada-3720 SoC. micro-DPU is the single-port FTTdp distribution point unit made by Methode Electronics which offers complete modularity with replaceable SFP modules both for uplink and downlink (G.hn over twisted-pair, G.hn over coax, 1G and 2.5G Ethernet over Cat-5e cable). On-board features: - 512 MiB DDR3 - 2 x 2.5G SFP via HSGMII SERDES interface to the A3720 SoC - USB 2.0 Type-C connector - 4GB eMMC - ETSI TS 101548 reverse powering via twisted pair (RJ45) or coax (F Type) uDPU is intented to run on kernel 4.19 on newer due to the SFP and hardware support. Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
* mvebu: Fix platform.sh for non-generic espressobin versionsBrett Mastbergen2019-06-281-2/+4
| | | | | | | | When the non-generic espressobin targets were added these board checks were not updated. One side effect of this is that config is not saved during an upgrade of -emmc,-v7, or -v7-emmc devices. Signed-off-by: Brett Mastbergen <bmastbergen@untangle.com>
* u-boot-mvebu: bump to 2019.04Vladimir Vid2019-06-281-2/+2
| | | | | | | | | Some devices and packages require newer version of u-boot to work properly, update u-boot to keep up with 4.19 kernel. Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr> [re-added missing commit message] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* lua5.3: fix build with MacOS's makeRafał Miłecki2019-06-282-0/+18
| | | | | | | It apparently requires passing V variable explicitly. Fixes: 6b161bb8d528 ("lua5.3: package Lua 5.3 version") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* lua: fix build with MacOS's makeRafał Miłecki2019-06-282-0/+18
| | | | | | | | It apparently requires passing V variable explicitly. Fixes: fe59b46ca7e0 ("lua: include version number in installed files") Reported-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* lua5.3: package Lua 5.3 versionRafał Miłecki2019-06-285-0/+369
| | | | | | | | | | | | | | | | | | | | This package provides an interpreter and compiler for Lua 5.3.5. It has been decided to use separated package due to a backward incompatibility of Lua 5.2 and 5.3. This package/version: 1) Does not include lnum patch as its author didn't decide to port it to the new version. 2) Does not provide shared library as the old patch doesn't apply anymore. It can be added later if needed. 3) Does not come with examples package as tests were dropped by upstream developers. That said there is definitely a room for improvement and any further work is highly appreciated. It works however and can be safely pushed as a basic/early package release. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* lua: include version number in installed filesRafał Miłecki2019-06-285-10/+108
| | | | | | This will allow installing Lua 5.1 and newer versions at the same time. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* lua: clean up host patch fuzzRafał Miłecki2019-06-282-25/+26
| | | | | | | Refresh host patches to match target changes from the commit 4e800716ac97 ("lua: clean up patch fuzz"). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* build: image: make image padding OS agnosticPetr Štetiar2019-06-271-4/+4
| | | | | | | | | | Image padding with dd needs to be done in an OS independent way as not all dd understand capital letter unit specifiers, and not all understand lowercase either. Fixes: 97833a57eff1 ("build: image: add pad-to and pad-rootfs-squashfs helpers") Reported-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: generic: add missing 4.19 config symbolPetr Štetiar2019-06-271-0/+2
| | | | | | | | | | | | | | Fixes following kernel build issue on ath79 with CONFIG_KERNEL_FTRACE=y enabled: Tracers (FTRACE) [Y/n/?] y Kernel Function Tracer (FUNCTION_TRACER) [Y/n/?] y Kernel Function Graph Tracer (FUNCTION_GRAPH_TRACER) [Y/n/?] y Enable trace events for preempt and irq disable/enable (PREEMPTIRQ_EVENTS) [N/y/?] (NEW) ... Preempt / IRQ disable delay thread to test latency tracers (PREEMPTIRQ_DELAY_TEST) [N/m/?] (NEW) Signed-off-by: Petr Štetiar <ynezz@true.cz>
* uqmi: bump to latest git HEADKoen Vandeputte2019-06-271-4/+4
| | | | | | | 1965c7139374 uqmi: add explicit check for message type when expecting a response 01944dd7089b uqmi_add_command: fixed command argument assignment Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.131Koen Vandeputte2019-06-271-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.184Koen Vandeputte2019-06-271-2/+2
| | | | | | | | | Refreshed all patches. Compile-tested on: none Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: add support for TOTOLINK A7000RChuanhong Guo2019-06-263-0/+133
| | | | | | | | | | | | | | | Specifications: - SoC: MT7621AT - RAM: 128MB - Flash: 16M SPI NOR - Ethernet: 5x GE ports - WiFi: 2.4G: MT7615N 5G: MT7615N Flash instruction: Upload generated sysupgrade firmware through factory web interface. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: mt7621: add IRQ for GPIO nodeChuanhong Guo2019-06-261-0/+3
| | | | | | This makes interrupt-based gpio-keys working. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* layerscape: drop pause frame support for aquantia phyYangbo Lu2019-06-261-52/+10
| | | | | | | | | | | | An aquantia phy patch which dropped pause frame support was missing when integrated LSDK-19.03 kernel patches into OpenWrt. Without this patch, LS1043A 10G port would not work. So apply it. Patch link https://source.codeaurora.org/external/qoriq/qoriq-components/ linux/commit/?h=linux-4.14&id=66346b115818365cfaf99d292871b19f0a1d2850 Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* upgs: update to latest git HEADPetr Štetiar2019-06-261-3/+3
| | | | | | | | cd7eabcd8c9d ugps: Fix compilation under 64-bit 198c06051dd0 Fix build error caused by enabled extra compiler warnings fc2ab8756b3b Enable extra compiler warnings Signed-off-by: Petr Štetiar <ynezz@true.cz>
* base-files: use OPENWRT prefix for os-release variablesBjørn Mork2019-06-261-8/+8
| | | | | | | | | | Just stumbled across this LEDE legacy, without finding any real reason to keep it. There is a single LEDE_DEVICE_MANUFACTURER_URL dependency in the luci feed repo which needs to be syncronized. Signed-off-by: Bjørn Mork <bjorn@mork.no> [re-added missing commit message] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: bump 4.19 to 4.19.56Koen Vandeputte2019-06-255-8/+8
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.130Koen Vandeputte2019-06-258-12/+12
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* x86: fix missing led variable warning during bootPetr Štetiar2019-06-251-0/+2
| | | | | | | | Fixes following warning during the boot: WARNING: Variable 'led' does not exist or is not an array/object Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: generic: add missing 4.19 config symbolPetr Štetiar2019-06-251-0/+1
| | | | | | | | Fixes following kernel build issue on x86/64: PCI PF Stub driver (PCI_PF_STUB) [N/m/y/?] (NEW) Signed-off-by: Petr Štetiar <ynezz@true.cz>
* malta: fix overlay support by updating to f2fs/ext4 based overlaysPetr Štetiar2019-06-252-7/+10
| | | | | | | | | | | | | | | | | Current snapshot images doesn't provide images with usable overlay filesystems: mount_root: no usable overlay filesystem found, using tmpfs overlay So this patch fixes this by updating support to current f2fs/ext4 based overlays and providing squashfs with proper rootfs TARGET_ROOTFS_PARTSIZE size. While at it, I've also added support for optional gzipping of the images, and renamed the output rootfs image filenames to match the more common naming pattern $(IMG_PREFIX)-rootfs-$(FS-TYPE).img. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* malta: configure kernel for f2fs and ext4 based overlaysPetr Štetiar2019-06-251-0/+7
| | | | | | | | jffs2/mtdblock overlays are long time gone, and as we switch to the new f2fs/ext4 based overlays, we need to add missing support for loop block device and f2fs to kernel. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: fix overlay support by updating to f2fs/ext4 based overlaysPetr Štetiar2019-06-252-2/+10
| | | | | | | | | | | | | | | | | | Current snapshot images doesn't provide images with usable overlay filesystems: mount_root: no usable overlay filesystem found, using tmpfs overlay So this patch fixes this by updating support to current f2fs/ext4 based overlays and providing squashfs with proper rootfs TARGET_ROOTFS_PARTSIZE size. While at it, I've also added support for optional gzipping of the images, and renamed the output rootfs image filenames to match the more common naming pattern $(IMG_PREFIX)-rootfs-$(FS-TYPE).img. Cc: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: configure kernel for f2fs and ext4 based overlaysPetr Štetiar2019-06-251-0/+7
| | | | | | | | jffs2/mtdblock overlays are long time gone, and as we switch to the new f2fs/ext4 based overlays, we need to add missing support for loop block device and f2fs to kernel. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: image: fix small disk space in squashfs overlayPetr Štetiar2019-06-251-12/+1
| | | | | | | | | | | | | Current squashfs snapshot images are improperly padded by just 128k, which doesn't correspond with TARGET_ROOTFS_PARTSIZE=128 default config option, leading to following: Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 85.0K 9.0K 71.0K 11% /overlay overlayfs:/overlay 85.0K 9.0K 71.0K 11% / Signed-off-by: Petr Štetiar <ynezz@true.cz>
* rb532,x86: image: use new IMG_COMBINED and IMG_ROOTFS varsPetr Štetiar2019-06-252-13/+13
| | | | | | | In `build: image: Add IMG_ROOTFS and IMG_COMBINED variables` we've added this new variables so switch to them now. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: image: add IMG_ROOTFS and IMG_COMBINED variablesPetr Štetiar2019-06-251-1/+3
| | | | | | Adding those two variables in order to share them across the tree. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: image: add variable for gzip-ext4-padded-squashfsPetr Štetiar2019-06-251-0/+17
| | | | | | | This common code could be shared by at least 3 targets (malta, armvirt and x86) so let's factor it out to separate variable. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: image: add pad-to and pad-rootfs-squashfs helpersPetr Štetiar2019-06-252-2/+10
| | | | | | For better reusability. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: enable gzipped images for armvirt and maltaPetr Štetiar2019-06-251-1/+1
| | | | | | | | As we're now going to pad all images by default to 128MiB let's enable compression of the images for armvirt and malta in order to save some space and bandwidth. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: make TARGET_ROOTFS_PARTSIZE 128MiB by defaultPetr Štetiar2019-06-251-1/+1
| | | | | | | | | | | As we're now going to pad all images by default, lets decrease the default rootfs partition size from 256MiB to 128MiB in order to save some space. I'm keeping it above 100MiB in order to keep current behavior, where overlay filesystem is using F2FS. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* tegra: image: remove image paddingPetr Štetiar2019-06-251-1/+0
| | | | | | | Commit "build: Remove TARGET_IMAGES_PAD option" has removed this config option so remove it from this target as well. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: image: remove TARGET_IMAGES_PAD option and force paddingPetr Štetiar2019-06-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Currently we're producing unusable x86 combined squashfs images (18.06.1, 18.06.2 and snapshots) as we don't enable TARGET_IMAGES_PAD, thus providing very small space for the overlay filesystem, leading to the following with OpenWrt 18.06.1 r7258-5eb055306f images on x86 QEMU: root@(none):/# mount | egrep 'root|overlay' /dev/root on /rom type squashfs /dev/loop0 on /overlay type ext4 overlayfs:/overlay on / type overlay root@(none):/# df -h | egrep 'root|overlay|Size' Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 113.0K 8.0K 97.0K 8% /overlay overlayfs:/overlay 113.0K 8.0K 97.0K 8% / We should rather ensure proper image padding in image generation code and we shouldn't rely on config options in order to generate usable images. So this patch removes TARGET_IMAGES_PAD config option and enforces padding on combined images. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* build: remove TARGET_IMAGES_PAD optionPetr Štetiar2019-06-251-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | It's being used only in x86 target to produce combined images, where it's mandatory to have padded images in order to produce working squashfs combined images usable in QEMU. Currently we're producing unusable x86 combined squashfs images (18.06.1, 18.06.2 and snapshots) as we don't enable TARGET_IMAGES_PAD, thus providing very small space for the overlay filesystem, leading to the following with OpenWrt 18.06.1 r7258-5eb055306f images on x86 QEMU: root@(none):/# mount | egrep 'root|overlay' /dev/root on /rom type squashfs /dev/loop0 on /overlay type ext4 overlayfs:/overlay on / type overlay root@(none):/# df -h | egrep 'root|overlay|Size' Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 113.0K 8.0K 97.0K 8% /overlay overlayfs:/overlay 113.0K 8.0K 97.0K 8% / So we should rather ensure proper image padding in image generation code and we shouldn't rely on config options in order to generate usable images. Signed-off-by: Petr Štetiar <ynezz@true.cz>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-16 10:00:49 +0000