aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* uqmi: use built-in command for data-link verificationKoen Vandeputte2018-02-131-1/+19
| | | | | | | | | | | uqmi contains a command for directly querying the modem if there is a valid data connection, so let's use it. This avoids the cases were all previous tests are succesful, but the actual data link is not up for some reasons, leading to states were we thought the link was up when it actually wasn't .. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* uqmi: use correct value for connection checkingKoen Vandeputte2018-02-131-4/+8
| | | | | | | | | | | | | | Originally, the implementation only checked if uqmi command execution succeeded properly without actually checking it's returned data. This lead to a pass, even when the returned data was indicating an error. Rework the verification to actually check the returned data, which can only be correct if the uqmi command itself also executed correctly. On command execution success, value "pdh_" is a pure numeric value. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* uqmi: use general method for state cleaningKoen Vandeputte2018-02-131-10/+4
| | | | | | | | | | Debugging shows that using the general method properly cleans on each run, while the method specifying the client-ID shows "No effect" even while in connected state. Fixes several connectivity issues seen on specific modems. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: use new image build code for WHR-G300NINAGAKI Hiroshi2018-02-132-42/+21
| | | | | | | | The tftp.bin image for Buffalo WHR-G300N was not built, so I was fixed it after rewriting to new image build code. And the code for factory-EU.bin was broken, so I deleted it. Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mediatek: remove the CPU_SUBTYPEJohn Crispin2018-02-131-1/+0
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* cns3xxx: remove linux 4.9 supportKoen Vandeputte2018-02-1329-1607/+13
| | | | | | | | - Remove kernel 4.9 support - Apply specific 4.14 changes directly to source - Refreshed all Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* target: Remove nomips16 option.Rosen Penev2018-02-131-3/+1
| | | | | | There is no target with a CPU subtype of nomips16. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* tools/mkimage: copy mkenvimage to bin directoryEvgeniy Didin2018-02-131-0/+2
| | | | | | | | | | | | | | For some boards u-boot binary environment file is required, which is generated by mkenvimage utility. But in OpenWrt there is no separate support for mkenvimage, which is a part of u-boot tools. mkenvimage gets built in u-boot/tools as well as mkimage anyways. So lets just copy mkenvimage to the $(STAGING_DIR_HOST)/bin/ directory. Signed-off-by: Evgeniy Didin <Evgeniy.Didin@synopsys.com> CC: Alexey Brodkin <abrodkin@synopsys.com> CC: Hauke Mehrtens <hauke@hauke-m.de> CC: John Crispin <john@phrozen.org>
* kernel: add missing symbol for v4.14John Crispin2018-02-131-0/+1
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* octeontx: add support for OCTEON TX targetTim Harvey2018-02-138-0/+1049
| | | | | | | | | | | The Cavium OCTEON TX is an ARM 64-bit SoC leveraging CPU cores and periperhals from the Cavium ThunderX SoC. This initial support provides a 4.14 kernel and kernel+initramfs that is bootable on the Gateworks Newport GW630x as well as the Cavium sff8104 reference board. Signed-off-by: Tim Harvey <tharvey@gateworks.com>
* packages: uboot-mxs: override instead of appending u-boot make flagsMichael Heimpold2018-02-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | This prevents passing down the HOSTCC stuff set in u-boot.mk which results in linking errors against openssl: tools/mxsimage.o: In function `sb_aes_reinit': mxsimage.c:(.text+0x202): undefined reference to `EVP_CIPHER_CTX_reset' tools/mxsimage.o: In function `mxsimage_generate': mxsimage.c:(.text+0x110d): undefined reference to `EVP_MD_CTX_new' mxsimage.c:(.text+0x114f): undefined reference to `EVP_MD_CTX_free' mxsimage.c:(.text+0x11c3): undefined reference to `EVP_MD_CTX_new' mxsimage.c:(.text+0x1323): undefined reference to `EVP_MD_CTX_free' mxsimage.c:(.text+0x134a): undefined reference to `EVP_CIPHER_CTX_reset' tools/mxsimage.o: In function `mxsimage_verify_print_header': mxsimage.c:(.text+0x23ce): undefined reference to `EVP_MD_CTX_new' mxsimage.c:(.text+0x242c): undefined reference to `EVP_MD_CTX_new' mxsimage.c:(.text+0x246b): undefined reference to `EVP_MD_CTX_free' mxsimage.c:(.text+0x24ef): undefined reference to `EVP_CIPHER_CTX_reset' mxsimage.c:(.text+0x2e52): undefined reference to `EVP_MD_CTX_free' collect2: error: ld returned 1 exit status Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* packages: uboot-mxs: bump to 2017.11Michael Heimpold2018-02-132-120/+292
| | | | | | Also update the U-Boot BSP patch for I2SE Duckbill devices. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* mxs: rename files to files-4.9Michael Heimpold2018-02-131-0/+0
| | | | | | | | The Device Tree file for I2SE Duckbill boards was updated upstream. Let's use the upstream version for upcoming kernel 4.14 by keeping our current version for v4.9 still around. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* ramips: Add support for the GnuBee Personal Cloud TwoRosen Penev2018-02-137-0/+160
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GnuBee Personal Cloud Two crowdfunded on https://www.crowdsupply.com It is a low-cost, low-power, network-attached storage device. Specifications: - SoC: MediaTek MT7621AT - RAM: DDR3 512 MB - Flash: 32 MB - Six SATA ports for 3.5" Drives - One SDcard - One USB 3.0 - Two USB 2.0 - Gigabit Ethernet: Three Ports - UART 3.5mm Audio Jack or 3 pin header - 57600 8N1 - Three GPIOs available on a pin header Flash instructions: The GnuBee Personal Cloud Two ships with libreCMC installed. libreCMC is a Free Software Foundation approved fork of LEDE/OpenWrt. As such one can upgrade using the webinterface or sysupgrade. Das U-Boot has multiple options for recovery or updates including : - USB - http - tftp Errata: - While there are three ethernet ports, the third requires support for the second GMAC. This will come in kernel 4.14. - The first hard drive slot has a clearance issue with the two fan headers. Workaround is to pull the headers out and connect the pins to jumper wires. - Using this device as a NAS is problematic with the 4.9 kernel as many /dev/sdX reads throw silent errors. The current theory behind this is some kind of unhandled DMA mapping error in the kernel. This is not an issue with kernel 4.4. Signed-off-by: L. D. Pinney <ldpinney@gmail.com> Signed-off-by: Rosen Penev <rosenp@gmail.com>
* iptables: Support building connlabel moduleKristian Evensen2018-02-133-0/+34
| | | | | | | | | | It is currently possible to enable connlabel-support in iptables. However, in order for connlabel to work properly, the kernel module must also be present. This patch adds support for building the connlabel-module, and selects it by default when connlabel-support is enabled. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
* layerscape: fix call trace of pfe module removingYangbo Lu2018-02-131-14/+5
| | | | | | | | Updated pfe kernel patch to clean up iounmap(pfe->ddr_baseaddr). pfe->ddr_baseaddr was got through phys_to_virt() not ioremap(), so iounmap() for pfe->ddr_baseaddr should be removed. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: fix DPAA2 QDMA issueYangbo Lu2018-02-131-0/+134
| | | | | | | This patch is to reverse a upstream dmatest patch for now which is causing DPAA2 QDMA test issue. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add a make menuconfig known issue in READMEYangbo Lu2018-02-131-0/+6
| | | | | | | This patch is to add a known issue of make menuconfig in README file. This is also a common issue for OpenWrt. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: fix type for kernel 4.9 dpaa2_mac_get_stats() functionYangbo Lu2018-02-131-7/+8
| | | | | | | | This patch changes the declarations of ndo_get_stats64 handlers to the previous struct rtnl_link_stats64 * return type instead of the mainline void return. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update READMEYangbo Lu2018-02-131-23/+32
| | | | | | | | Tis patch is to fix up some descriptions in README. Per-device rootfs had been supported, and a known issue had been found. These also should be updated accordingly. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: support ubifs rootfs in u-boot envYangbo Lu2018-02-135-15/+15
| | | | | | | ls1012ardb/ls1012afrdm/ls1046ardb/ls1088ardb firmwares now use ubifs rootfs. So u-boot env should be set accordingly. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: support ubifs rootfsYangbo Lu2018-02-133-10/+37
| | | | | | | | | Some layerscape devices (ls1012ardb/ls1012afrdm/ls1046ardb/ls1088ardb) were using ext4 rootfs because there were issues using squashfs. This patch is to drop using ext4 rootfs and use ubifs rootfs instead which is more proper for SPI-NOR flash. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update u-boot to LSDK1712Yangbo Lu2018-02-134-32/+32
| | | | | | | This patch is to update layerscape u-boot to NXP LSDK1712 release. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update ppfe firmware to LSDK1712Yangbo Lu2018-02-131-5/+5
| | | | | | | | Updated ppfe firmware to NXP LSDK1712 release. Used ppfe firmware git tree on NXP github since it was migrated here from qoriq-open-source github. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: add ls-rcw-bin packageYangbo Lu2018-02-132-28/+103
| | | | | | | | | | | | NXP LSDK1712 release used two rcw git trees. The original rcw git tree was still source code but dropping ls1012a/ls1088a/ls2088a boards in LSDK1712. Instead another new rcw git tree was used to just provided rcw binaries for these boards dropped. So this patch is to update ls-rcw to LSDK1712 release and add a new ls-rcw-bin package. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update PPA firmware to LSDK1712Yangbo Lu2018-02-131-3/+3
| | | | | | | This patch is to update PPA firmware to NXP LSDK1712 release. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: migrate fman-ucode to NXP githubYangbo Lu2018-02-131-1/+1
| | | | | | | | fman-ucode had been migrated from qoriq-open-source github to NXP github. So the Makefile should be fixed accordingly. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update MC firmware to LSDK1712Yangbo Lu2018-02-131-6/+6
| | | | | | | | Updated MC firmware to NXP LSDK1712 release. Used MC firmware git tree on NXP github since it was migrated here from qoriq-open-source github. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: remove USB configs for 64-bitYangbo Lu2018-02-131-46/+2
| | | | | | | Removed USB configs for 64-bit device since they're already in kmod package. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: remove USB and TI specific configs for 32-bitYangbo Lu2018-02-131-155/+2
| | | | | | | | This patch is to remove USB configs for 32-bit device since they're already in kmod package. Also removed TI platform specific configs. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update patches-4.9 to LSDK1712Yangbo Lu2018-02-1333-2062/+5557
| | | | | | | | | | | | | Patches changes - Updated patches-4.9 to NXP LSDK1712 linux-4.9. - Merged changes of patch 303 into integrated patch 201. - Split changes of patch 706 into dpaa part and dpaa2 part, and merged these changes into integrated patches 701 and 705. - Removed patch 819 since ehci-fsl driver could be compiled now. - Refreshed these patches. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update restool to 2017-12-03Yangbo Lu2018-02-1313-759/+3
| | | | | | | Updated restool to 2017-12-03 and removed patches since the new version had involved them. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* layerscape: update build guide in READMEYangbo Lu2018-02-131-0/+4
| | | | | | | Added package feeds updating and installing in build guide of README. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com>
* ar71xx: add support for TP-Link RE355Henryk Heisig2018-02-1315-5/+142
| | | | | | | | | | | | | | | | | | | | | | | | This device is identical as TP-Link RE450 RE355 is a dual-band AC1200 router, based on Qualcomm/Atheros QCA9558+QCA9880. Specification: 720/600/200 MHz (CPU/DDR/AHB) 64/128 MB of RAM (DDR2) 8 MB of FLASH (SPI NOR) 3T3R 2.4 GHz 3T3R 5 GHz 1x 10/100/1000 Mbps Ethernet 7x LED, 3x button UART header on PCB Flash instruction: Web: Download lede-ar71xx-generic-archer-c60-v2-squashfs-factory.bin and use OEM System Tools - Firmware Upgrade site. Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* kmod-sched: add sch_multiq to extra schedulersPhilip Prindeville2018-02-131-0/+1
| | | | | | | For hardware that supports multiple h/w output queues, add a compatible scheduler (NET_SCH_MULTIQ). Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* base-files: don't evaluate block-device ueventDaniel Golle2018-02-131-4/+8
| | | | | | | | | | | | | Current code and also before commit da52dd0c83 was vulnerable to shell injection using volume lables in the GPT partition table of block devices. Given that partition names can be freely defined in GPT tables we really shouldn't evaluate a string which is potentially crafted with evil intentions. Hence rather use `export -n` to absorb the uevent's variables into the environment. Fixes commit da52dd0c83 (base-files: quote values when evaluating uevent) Signed-off-by: Daniel Golle <daniel@makrotopia.org> [mschiffer@universe-factory.net: suggested export -n usage]
* kernel: add IEEE-1284 parallel port supportDaniel Gimpelevich2018-02-121-5/+40
| | | | | | | | | | The kmod-lp package included both lp.ko and ppdev.ko, but ECP device drivers may or may not require lp NOT to be loaded, needing only ppdev. Additionally, There were no packages for any parport interface modules, such as uss720 or parport_pc, provided here. It has not been otherwise possible to use PC-style parport hardware for kmod-lp. Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* brcm63xx: switch to kernel 4.9Jonas Gorski2018-02-121-1/+1
| | | | | | Now that we have support for it, let's switch to kernel 4.9. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* ar7: switch to kernel 4.9Jonas Gorski2018-02-121-1/+1
| | | | | | | With generic run tested and ac49x compile tested, and no complaints so far, let's switch to 4.9. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* ar7: fix ac49x compilation with 4.9Jonas Gorski2018-02-121-1/+1
| | | | | | | | This will introduce a warning on 3.18, but fixes an error when compiling for 4.9. Fixes: cf9e0a59aabd ("ar7: add kernel 4.9 support") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* Revert "mediatek: activate fpu feature flag"John Crispin2018-02-121-1/+1
| | | | | | | | This reverts commit 3594447a7d0398c55ea78f658b52b7d8084ae9f9. This causes the userland to not come up properly Signed-off-by: John Crispin <john@phrozen.org>
* tools: update patch to v2.7.6Russell Senior2018-02-122-27/+2
| | | | | | | Removes a redundant patch with a fix already upstream. Build tested on apm821xx (PPC). Signed-off-by: Russell Senior <russell@personaltelco.net>
* mvebu: fix sysupgrade from 17.04 for clearfog proJonas Gorski2018-02-111-0/+1
| | | | | | | | | When clearfog was renamed to clearfog pro, it broke sysupgrade from 17.04 as the new images now get rejected as incompatible. Fix this by adding the legacy boardname to the compatible devices. Fixes: ec4a8c6dee81 ("mvebu: ClearFog renamed upstream to ClearFog Pro") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: add kernel 4.14 supportJonas Gorski2018-02-11193-0/+23023
| | | | | | | Add support for kernel 4.14. Increases compressed kernel size by ~64k compared to 4.9. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* broadcom-wl: fix compilation with 4.14Jonas Gorski2018-02-111-0/+10
| | | | | | | | The last_rx field was removed from net_device. Since the field wasn't used by the generic subsystem, and the driver only writes to it, just remove the usage. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: add kernel 4.9 supportJonas Gorski2018-02-11204-0/+23683
| | | | | | | | Add support for kernel 4.9 based on the more upstream comformant partition defintions. Increases compressed kernel size by ~95k compared to 4.4. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: switch to new partition layout specificationJonas Gorski2018-02-1187-863/+1407
| | | | | | | Now that we support parsing the expected upstream definition, update the dts files to it. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: enhance dt partitions support to match upstream more closelyJonas Gorski2018-02-111-9/+19
| | | | | | | Partitions are supposed to be enclosed in an extra partitions node. Allow the bcm63xxpart parser to cope with that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: backport latest bcm63xx_enet changes from upstreamJonas Gorski2018-02-1111-19/+201
| | | | | | No functional changes, just simple cleanups. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* brcm63xx: fix ephy reset gpio lookupJonas Gorski2018-02-111-1/+1
| | | | | | | The lookup needs to be called just "reset" for the common code. Fixes: 054c0d4e3193 ("brcm63xx: backport mdio-bus reset gpio support") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>