aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* brcm2708: add kmod-sound-soc-googlevoicehatStijn Tintel2018-12-181-0/+24
| | | | | | Add kernel module for Google Voice HAT support in kernel 4.14. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: add kmod-sound-soc-audioinjector-octo-soundcardStijn Tintel2018-12-181-0/+26
| | | | | | | Add kernel module for AudioInjector Octo surround sound card support in kernel 4.14. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: add kmod-sound-soc-allo-katana-codecStijn Tintel2018-12-181-0/+29
| | | | | | Add kernel module for Allo Katana DAC support in kernel 4.14. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: add kmod-sound-soc-allo-piano-dac-plusStijn Tintel2018-12-181-0/+27
| | | | | | Add kernel module for the Allo Piano DAC Plus in kernel 4.14. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: add kmod-sound-soc-allo-digioneStijn Tintel2018-12-181-0/+26
| | | | | | Add kernel module for Allo DigiOne support in kernel 4.14. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: add kmod-sound-soc-allo-boss-dacStijn Tintel2018-12-181-0/+27
| | | | | | Add kernel module for Allo Boss DAC support in kernel 4.14. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: add kmod-hwmon-rpi-poe-fanStijn Tintel2018-12-181-0/+17
| | | | | | | Add kernel module for the fan on the PoE HAT for the 3B+ model in kernel 4.14. Without this, the fan will not turn on. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: prepare kmod-drm-vc4 for 4.14Stijn Tintel2018-12-181-2/+7
| | | | | | | It requires sound card support in the new kernel. HDMI CEC support is disabled for now; enabling it turned out to be non-trivial. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: prepare kmod-video-bcm2835 for 4.14Stijn Tintel2018-12-181-2/+4
| | | | | | | | Since kernel 4.12, this driver appeared in staging. The rpi-4.14.y kernel tree uses these as well. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: prepare kmod-sound-raspidac3 for 4.14Stijn Tintel2018-12-181-0/+1
| | | | | | | Support for RaspiDac3 has been removed from the rpi-4.14.y kernel tree. Make the kmod package depend on kernel 4.9. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708: prepare kmod-sound-arm-bcm2835 for 4.14Stijn Tintel2018-12-181-1/+2
| | | | | | | | Since kernel 4.12, this driver appeared in staging. The rpi-4.14.y kernel tree uses these as well. Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ubox: bump to git HEADStijn Tintel2018-12-181-4/+4
| | | | | | 876c7f5 kmodloader: load_modprobe: abort after 2 attempts Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* build: fix build dependency of kmod .ipk with version filtered filesYousong Zhou2018-12-181-1/+1
| | | | | | | | | We need to use resolved file list as prerequisites for repacking kmod .ipk files. Note that currently version_filter uses a Makefile macro KERNEL_PATCHVER that should be available at ipk building time. Reported-by: Rafał Miłecki <zajec5@gmail.com> Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* layerscape: use MKUBIFS_OPTS for per-device ubi parametersYangbo Lu2018-12-182-6/+3
| | | | | | | UBIFS_OPTS couldn't be used for per-device ubi parameters. Let's use MKUBIFS_OPTS instead. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: drop kernel 4.9 supportBiwen Li2018-12-1838-275972/+0
| | | | | | | This patch is to drop kernel 4.9 support. Signed-off-by: Biwen Li <biwen.li@nxp.com> Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add LS1021AIOT board supportBiwen Li2018-12-185-3/+326
| | | | | | | | | | | | | | | | | | | | | | | The LS1021A-IoT gateway reference design based on the QorIQ LS1021A processor is a purpose-built, small footprint hardware platform with a wide array of high-speed connectivity and low-speed serial interfaces to support secure delivery of IoT services for home, business or other commercial location. - Combines standards-based, open source software with a feature-rich IoT gateway design to establish a common, open framework for secured IoT service delivery and management. - Provides a wide assortment of high-speed and serial-based connectivity in a compact, highly secure design. - High efficiency through the use of the Arm-based QorIQ LS1021A embedded processor. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Biwen Li <biwen.li@nxp.com>
* layerscape: upgrade kernel to 4.14Biwen Li2018-12-1845-1/+242886
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch is to upgrade kernel to 4.14 for layerscape. patches-4.14 for layerscape included two categories. - NXP Layerscape SDK kernel-4.14 patches All patches on tag LSDK-18.09-V4.14 were ported to OpenWrt kernel. Since there were hundreds patches, we had to make an all-in-one patch for each IP/feature. See below links for LSDK kernel. https://lsdk.github.io/components.html https://source.codeaurora.org/external/qoriq/qoriq-components/linux - Non-LSDK kernel patches Other patches which were not in LSDK were just put in patches-4.14. Kept below patches from patches-4.9. 303-dts-layerscape-add-traverse-ls1043.patch 821-add-esdhc-vsel-to-ls1043.patch 822-rgmii-fixed-link.patch Renamed and rebase them as below in patches-4.14, 303-add-DTS-for-Traverse-LS1043-Boards.patch 712-sdk-dpaa-rgmii-fixed-link.patch 824-mmc-sdhci-of-esdhc-add-voltage-switch-support-for-ls.patch Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com> Signed-off-by: Biwen Li <biwen.li@nxp.com>
* kernel: Add missing symbols to 4.19Petr Štetiar2018-12-181-0/+4
| | | | | | | | While building 4.19 for ath79 with CONFIG_ALL_KMODS=y with verbose mode enabled I was asked by kernel config about few symbols/modules so I'm adding those missing symbols to the generic config. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: Fix usb-chipidea dependency on ulpi.ko for 4.19Petr Štetiar2018-12-181-1/+2
| | | | | | | | | | | | | | | | | | | It seems, that since Linux 4.18-rc2 ci_hdrc depends on ulpi. commit a930d8bd94d8db7715d1af74299f710b1fb22fc8 Author: Fabio Estevam <fabio.estevam@nxp.com> Date: Wed Jul 4 10:09:58 2018 -0300 usb: chipidea: Always build ULPI code Commit 03e6275ae381 ("usb: chipidea: Fix ULPI on imx51") causes a kernel hang on imx51 systems that use the ULPI interface and do not select the CONFIG_USB_CHIPIDEA_ULPI option. In order to avoid such potential misuse, let's always build the chipidea ULPI code into the final ci_hdrc object. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* uboot-envtools: fix configuration for I2SE DuckbillsMichael Heimpold2018-12-182-2/+2
| | | | | | | | After changing board names to DT compat string, we also need to adjust the script which generates uboot-env configuration files. Fixes: e880a30549b ("mxs: use generic sysinfo board detection") Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* uboot-envtools: ath79: add support for the Buffalo BHR-4GRV2Stefan Lippers-Hollmann2018-12-181-0/+1
| | | | | | | | | | | According to https://github.com/openwrt/openwrt/pull/1527, support for the Buffalo BHR-4GRV2 in ath79 requires repartitioning from an initramfs image, make this easier by supporting uboot-envtools support out of the box. Build tested, but not runtime tested. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* uboot-envtools: ath79: add support for the Buffalo WZR-HP-AG300HStefan Lippers-Hollmann2018-12-181-0/+3
| | | | | | | | | Port support for the Buffalo WZR-HP-AG300H from the ar71xx target to ath79 as well. Build- and runtime tested on the Buffalo WZR-HP-AG300H. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
* dropbear: fix dropbear startup issueHans Dedecker2018-12-182-2/+10
| | | | | | | | | | | | | | | Interface triggers are installed by the dropbear init script in case an interface is configured for a given dropbear uci section. As dropbear is started after network the interface trigger event can be missed during a small window; this is especially the case if lan is specified as interface. Fix this by starting dropbear before network so no interface trigger is missed. As dropbear is started earlier than netifd add a boot function to avoid the usage of network.sh functions as call to such functions will fail at boottime. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> Acked-by: Jo-Philipp Wich <jo@mein.io>
* cns3xxx: fix writing to wrong PCI registersKoen Vandeputte2018-12-183-0/+237
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Originally, cns3xxx used it's own functions for mapping, reading and writing registers. Upstream commit 802b7c06adc7 ("ARM: cns3xxx: Convert PCI to use generic config accessors") removed the internal PCI config write function in favor of the generic one: cns3xxx_pci_write_config() --> pci_generic_config_write() cns3xxx_pci_write_config() expected aligned addresses, being produced by cns3xxx_pci_map_bus() while the generic one pci_generic_config_write() actually expects the real address as both the function and hardware are capable of byte-aligned writes. This currently leads to pci_generic_config_write() writing to the wrong registers on some ocasions. First issue seen due to this: - driver ath9k gets loaded - The driver wants to write value 0xA8 to register PCI_LATENCY_TIMER, located at 0x0D - cns3xxx_pci_map_bus() aligns the address to 0x0C - pci_generic_config_write() effectively writes 0xA8 into register 0x0C (CACHE_LINE_SIZE) This seems to cause some slight instability when certain PCI devices are used. Another issue example caused by this this is the PCI bus numbering, where the primary bus is higher than the secondary, which is impossible. Before: 00:00.0 PCI bridge: Cavium, Inc. Device 3400 (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 255 Bus: primary=02, secondary=01, subordinate=ff, sec-latency=0 After fix: 00:00.0 PCI bridge: Cavium, Inc. Device 3400 (rev 01) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 255 Bus: primary=00, secondary=01, subordinate=02, sec-latency=0 And very likely some more .. Fix all by omitting the alignment being done in the mapping function. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.89Koen Vandeputte2018-12-1822-166/+134
| | | | | | | | | | | | Refreshed all patches. Remove upstreamed patches: - 096-v4.20-netfilter-ipv6-Preserve-link-scope-traffic-original-.patch Compile-tested on: ar71xx, cns3xxx, imx6 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.146Koen Vandeputte2018-12-185-7/+8
| | | | | | | | | | Refreshed all patches. Compile-tested on: brcm2708 Runtime-tested on: brcm2708 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: bump 3.18 to 3.18.130Koen Vandeputte2018-12-183-17/+17
| | | | | | | | | Refreshed all patches. Compile-tested on: adm5120 Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* build: drop cameo-factory recipeMathias Kresin2018-12-171-12/+0
| | | | | | | The cameo factory images are created using existing image build commands, which makes the code obsolete. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath79: replace cameo-factory with existing build commandsMathias Kresin2018-12-171-2/+4
| | | | | | | | Use pad-offset and append-string to create the cameo factory images for the D-LINK DIR-825 C1/DIR-835 A1 factory images. Tested-by: Sebastian Kemper <sebastian_ml@gmx.net> Signed-off-by: Mathias Kresin <dev@kresin.me>
* build: move append-string to image-commands.mkMathias Kresin2018-12-172-4/+4
| | | | | | Move it to image-commands.mk so that it can used by other targets. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ipset: update to 7.1Syrone Wong2018-12-171-2/+2
| | | | Signed-off-by: Syrone Wong <wong.syrone@gmail.com>
* kernel: preserve oif of IPv6 link scope packetsHans Dedecker2018-12-1710-11/+107
| | | | | | | | | | | Backort upstream patch which preserves oif of IPv6 link scoped packets. The outgoing interface of IPv6 link scope packets can be changed by the function ip6_route_me_harder. This is unwanted behavior for link local packets and multicast packets as the outgoing interface is fixed and must not be altered as it can break neighbor discovery and multicast listener discovery. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* netifd: fix ipv6 multicast check in previous commitKevin Darbyshire-Bryant2018-12-171-2/+2
| | | | Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* image: remove duplicate cameo-factorySebastian Kemper2018-12-171-12/+0
| | | | | | The function was accidentally added twice. Remove the duplicate. Signed-off-by: Sebastian Kemper <sebastian_ml@gmx.net>
* ipq40xx: GL-B1300: convert to new partitions layoutChristian Lamparter2018-12-171-52/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | Alberto Bursi reported: >The patch "ipq40xx: specify "firmware" partition format for GL.iNet GL-B1300" >prevents boot on my B1300. I compiled from latest sources. The GL-B1300 was using the discouraged direct subnodes method to declare the partitions on the flash. |The partition table should be a subnode of the flash node and should be named |'partitions'. This node should have the following property: |- compatible : (required) must be "fixed-partitions" |Partitions are then defined in subnodes of the partitions node. | |For backwards compatibility partitions as direct subnodes of the flash device are |supported. This use is discouraged. |NOTE: also for backwards compatibility, direct subnodes that have a compatible |string are not considered partitions, as they may be used for other bindings. <https://www.kernel.org/doc/Documentation/devicetree/bindings/mtd/partition.txt> Hence, this patch converts the device to the "partitions" layout. Fixes: 1cbe457cf94 ("ipq40xx: specify "firmware" partition format for GL.iNet GL-B1300") Reported-by: Alberto Bursi <bobafetthotmail@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: dts: Remove newly added default-state=off propertyChristian Lamparter2018-12-171-10/+0
| | | | | | I'm afraid that this will be "one of many" patches to come. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ar71xx/ath79: switch devices to the -ct driver and firmwareChristian Lamparter2018-12-173-5/+5
| | | | | | | Since commit 61b5b4971e7 ("mac80211: make ath10k-ct the default ath10k") select ath10k-ct and the -ct firmwares by default. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* bcm53xx: include WiFi firmware for devices with 4366C0Rafał Miłecki2018-12-171-1/+1
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* linux-firmware: broadcom: package 4366C0 FullMAC firmwareRafał Miłecki2018-12-171-0/+9
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* linux-firmware: update to the commit from 2018-12-16Rafał Miłecki2018-12-171-3/+3
| | | | | | It includes e.g. new Broadcom FullMAC firmwares for 4366B1 and 4366C0. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: backport ifconfig ioctl support for class e addressesKevin Darbyshire-Bryant2018-12-173-0/+237
| | | | | | | | | | | | | | | | | Backport net: Allow class-e address assignment via ifconfig ioctl While most distributions long ago switched to the iproute2 suite of utilities, which allow class-e (240.0.0.0/4) address assignment, distributions relying on busybox, toybox and other forms of ifconfig cannot assign class-e addresses without this kernel patch. While CIDR has been obsolete for 2 decades, and a survey of all the open source code in the world shows the IN_whatever macros are also obsolete... rather than obsolete CIDR from this ioctl entirely, this patch merely enables class-e assignment, sanely. https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65cab850f0eeaa9180bd2e10a231964f33743edf Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* netifd: support configuring class e 240.0.0.0/4 addressesKevin Darbyshire-Bryant2018-12-171-3/+3
| | | | | | cd089c5 proto: Support class-e addressing in netifd Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* treewide: dts: Remove default-state=off property from all gpio LED nodesPetr Štetiar2018-12-1772-233/+0
| | | | | | | | | | | | | | | | | | >From the Documentation/devicetree/bindings/leds/common.txt: - default-state : The initial state of the LED. Valid values are "on", "off", and "keep". If the LED is already on or off and the default-state property is set the to same value, then no glitch should be produced where the LED momentarily turns off (or on). The "keep" setting will keep the LED at whatever its current state is, without producing a glitch. The default is off if this property is not present. So setting the default-state of the LEDs to `off` is redundant as `off` is default LED state anyway. We should remove it as almost every new PR/patch submission contains this property by default which seems to be just copy&paste from some DTS file already present in the tree. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: add support for TP-Link Archer A7Karl-Felix Glatzer2018-12-177-1/+314
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for TP-Link Archer A7 Specification: - SOC: QCA9563 - Flash: 16 MiB (SPI) - RAM: 128 MiB (DDR2) - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: - 2.4GHz (bgn) SoC internal - 5GHz (ac) QCA988x - USB: 1x USB 2.0 port - Button: 1x power, 1x reset, 1x wps - LED: 10x LEDs - UART: holes in PCB - Vcc, GND, RX, TX from ethernet port side - 115200n8 Flash instructions: Upload openwrt-ath79-generic-tplink_archer-a7-v5-squashfs-factory.bin via the Webinterface. Flash instruction using tftp recovery: 1. Connect the computer to one of the LAN ports of the Archer A7 2. Set the computer IP to 192.168.0.66 3. Start a tftp server with the OpenWrt factory image in the tftp root directory renamed to ArcherC7v5_tp_recovery.bin 2. Connect power cable to Archer A7, press and hold the reset button and turn the router on 3. Keep the reset button pressed for ~5 seconds 4. Wait ~150 seconds to complete flashing Changes since first revision: - Flash instructions using stock image webinterface - Changed "Version 5" in model string to "v5" - Split DTS file in qca9563_tplink_archer-x7-v5.dtsi and qca9563_tplink_archer-a7-v5.dts - Firmware image is now build with dynamic partitioning - Default to ath10k-ct Changes since second revision: - Changed uboot@0 to uboot@20000 in DTS file - Fixed ordering issue in board led script - Specify firmware partition format in DTS file - Rebased Makefile device definition on common Device/tplink-safeloader-uimage definition - Merged switch section in network script (same configuration as tplink,tl-wdr3600 and tplink,tl-wdr4300) Signed-off-by: Karl-Felix Glatzer <karl.glatzer@gmx.de>
* ath79, brcm63xx: Fix debounce-interval properties in gpio-keys-polled nodesPetr Štetiar2018-12-1770-71/+181
| | | | | | | | | | | | | | | | | | | | | | | | | This patch fixes wrong usage of debounce-interval subnode property of gpio-keys-polled nodes, which was used inproperly in parent node, but it belongs to the subnodes, excerpt from the docs: Optional subnode-properties: - debounce-interval: Debouncing interval time in milliseconds. If not specified defaults to 5. And the docs are up to date as the source code matches that description as well: if (fwnode_property_read_u32(child, "debounce-interval", &button->debounce_interval)) button->debounce_interval = 5; While at it, I've also re-formatted gpio-keys-polled nodes, usually just adding new lines after every key subnode. Cc: Tomasz Maciej Nowak <tomek_n@o2.pl> Cc: Matt Merhar <mattmerhar@protonmail.com> Cc: Jonas Gorski <jonas.gorski@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: ag71xx: Fix code formatting in ag71xx_probePetr Štetiar2018-12-171-2/+2
| | | | Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: ag71xx: Unify debug output with ar71xx and make debugging easierPetr Štetiar2018-12-171-16/+32
| | | | | | | | | Currently it's quite hard to diff debugging output between ar71xx and ath79, so this patch tries to improve it by adding the same ag71xx_dump_regs function and placing debugging output from the registers to relatively same places. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ar71xx: ag71xx: Replace duplicate debugging code with simple function callPetr Štetiar2018-12-171-16/+1
| | | | | | | ag71xx_dump_regs is used in code several times, and is providing same output. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* scripts/qemustart: more compact rand_mac()Yousong Zhou2018-12-171-1/+1
| | | | Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* ipq806x: drop kernel/ rootfs partition images for the ZyXEL NBG6817Stefan Lippers-Hollmann2018-12-171-3/+1
| | | | | | | | | | | | | Since commit 8e9a59a6b924469c0061d4bd945ae0c6dbfdecfe (build: add mkrasimage) a proper factory image can be provided for the ZyXEL NBG6817, which can be flashed from the OEM firmware or used for tftp based push-button recovery, therefore the previously used partition images for mmcblk0p5-rootfs.bin and mmcblk0p4-kernel.bin are no longer required (and using them properly has always been slightly difficult and risky) and can now be dropped from the image generation code. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-14 01:49:26 +0000