aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* ar71xx/ath79: ag71xx: get ring_mask consistentKoen Vandeputte2019-08-272-2/+2
| | | | | | | | | All other instances of this identical declaration fetch the value directly from the ring_order. Also do it here. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: ag71xx: add missing register writesKoen Vandeputte2019-08-271-0/+5
| | | | | | These are added in ath79, but were not backported here Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.139Koen Vandeputte2019-08-275-1/+5
| | | | | | | | | | | | Refreshed all patches. Also add a missing symbol for x86 which got used now in this bump. - ISCSI_IBFT Compile-tested on: cns3xxx, x86_64 Runtime-tested on: cns3xxx, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: Fix whitespace errors in 11-ath10k-caldataAdrian Schmutzler2019-08-271-2/+2
| | | | | Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 1174b94bc98db9730cec8501397cf997b6f7b35c)
* imagebuilder: fix `make info` for empty SUPPORTED_DEVICESPaul Spooren2019-08-221-1/+2
| | | | | | | | | | For x86/64 (maybe more) target the SUPPORTED_DEVICES variable is empty which causes the `&&` junction to fail, producing a non zero exit code. Tested-by: Paul Spooren <mail@aparcar.org> Fixed-by: Jo-Philipp Wich <jo@mein.io> Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 07926d7def59e5684b488e9b614342edc19e7eb2)
* kernel: Activate CONFIG_OPTIMIZE_INLININGHauke Mehrtens2019-08-172-9/+104
| | | | | | | | | | | | | | | | | | | | | | | | This will reduce the size of the kernel if CONFIG_CC_OPTIMIZE_FOR_SIZE is set like for all targets with small_flash feature flag. I haven't seen any changes for an ARM64 target which optimizes the kernel for speed instead. On the ath79/tiny target the uncompressed kernel size was reduced by 3.2% and the compressed kernel size by 2.1% kernel size with CONFIG_OPTIMIZE_INLINING=n 4346412 build_dir/target-mips_24kc_musl/linux-ath79_tiny/vmlinux 1391169 build_dir/target-mips_24kc_musl/linux-ath79_tiny/tplink_tl-wr941-v4-kernel.bin Kernel size with CONFIG_OPTIMIZE_INLINING=y 4212396 build_dir/target-mips_24kc_musl/linux-ath79_tiny/vmlinux 1362051 build_dir/target-mips_24kc_musl/linux-ath79_tiny/tplink_tl-wr941-v4-kernel.bin This change is currently pending for kernel 5.2 and already in linux-next, this updates our patch to match the upstream version. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 6dac1c0a9b94b62b6412b74a8997f728570f36be)
* mvebu: sysupgrade: sdcard: fix platform_do_upgrade_sdcardKlaus Kudielka2019-08-171-18/+16
| | | | | | | | | | | | Unconditionally execute the final case statement, even if the disk layout changed. This is necessary, to keep the original Turris Omnia flash instructions working: The disk layout WILL change, when switching from TurrisOS to OpenWRT. Without updating the uboot environment at the same time, the user would end up with an unbootable system. Fixes commit 2e5a0b81ec ("mvebu: sysupgrade: sdcard: keep user added ...") Signed-off-by: Klaus Kudielka <klaus.kudielka@gmail.com>
* mvebu: enable xHCI USB controller connected to PCIeTomasz Maciej Nowak2019-08-171-0/+1
| | | | | | | | | | This commit fixes regression on Linksys WRT1900 (Mamba) where this device doesn't have USB 3.0 controller integrated in SoC, instead it has Etron EJ168 connected to PCIe lane. Previously enabled in kernel 4.4 and 4.9, was lost in transition to 4.14. Fixes: 4ccad92 ("mvebu: Add support for kernel 4.14") Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* lantiq: unify Fritz!Box LED mappingsDavid Bauer2019-08-154-6/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | This commit unifies the LED mapping of the AVM Fritz!Box routers, which have a combined Power/DSL LED. With the stock firmware, the Power LED has the following characteristics: - Blink when DSL sync is being established - Solid when DSL sync is present We can't completely resemble this behavior in OpenWrt. Currently, the Power LED is completely off, when DSL sync is missing. This is not really helpful, as a user might have the impression, that he bricked his device. Instead, map the Info-LED to the state of the DSL connection. There is no consistent behavior for the Info-LED in the stock firmware, as the user can set it's function by himself. The DSL connection state is one possible option for the Info LED there. Also use the red Power LED to indicate a running upgrade, in case the board has a two-color Power LED. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 3032bf7f89e8ad5b69ab2f031287f475e5d2b829)
* Revert "ath79: make target source-only"Jo-Philipp Wich2019-08-141-1/+1
| | | | | | | | | | | | | | This reverts commit 2b074654b0f259518aa56e0975ca8e26c0c12bc9. Due to popular demand, I've decided to revert this commit after deliberating with Petr. This means that 19.07 will ship ath79 binary images after all. We do however consider the ath79 target on Kernel 4.14 in the 19.07 branch to be beta quality at best. Acked-by: Petr Štetiar <ynezz@true.cz> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* kernel: bump 4.14 to 4.14.138Koen Vandeputte2019-08-148-25/+25
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* lantiq: add led-upgrade alias for Fritz!Box 7412David Bauer2019-08-111-0/+1
| | | | | | | | This adds the led-upgrade alias for the AVM Fritz!Box 7412 to indicate a running firmware upgrade. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 920abb9b5865fe0994a5c8115cde616dac63d5ae)
* lantiq: enable second VPE on Fritz!Box 7412David Bauer2019-08-112-2/+2
| | | | | | | | | | The AVM Fritz!Box 7412 does not use the VMMC part of the Lantiq chip but rather a proprietary solution based on the DECT chip for the FXS ports. Therefore, the second VPE can be enabled for use with OpenWrt. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 891a7007598d5d396bf621fcc6ab0cc083b192b6)
* lantiq: correct Fritz!Box 7412 button logic levelDavid Bauer2019-08-111-2/+2
| | | | | | | | | | The AVM FRITZ!Box 7412 buttons are both active low, which is currently incorrectly defined in the device-tree. This leads to the device booting directly into failsafe. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit c12947b39e96c82974cbe0fc3557259713f37770)
* lantiq: use wpad-basic for boards with enough storageJohann Neuhauser2019-08-111-2/+2
| | | | | | | | | | This commit selects wpad-basic for the FRITZ!Box 7312 and 7412 as wpad-mini is only selected on boards with small flash. Signed-off-by: Johann Neuhauser <johann@it-neuhauser.de> [add short description] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit c3c3cd5e4a86acfc83449c47c5f87779a800bdc7)
* ar71xx: ag71xx: init rings with GFP_KERNELKoen Vandeputte2019-08-091-1/+1
| | | | | | | ar71xx got lost during final rebase .. Fixes: c8a6ce71e49c ("ar71xx/ath79: ag71xx: init rings with GFP_KERNEL") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx/ath79: ag71xx: init rings with GFP_KERNELKoen Vandeputte2019-08-091-1/+1
| | | | | | | | | | | | | | | Upstream commit 246902bdf562d45ea3475fac64c93048a7a39f01 Which contains following explanation: -- There is no need to use GFP_ATOMIC here, GFP_KERNEL should be enough. The 'kcalloc()' just a few lines above, already uses GFP_KERNEL. -- Looking at the code, all other descriptors also use plain GFP_KERNEL Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx/ath79: ag71xx: fix sleep in atomicKoen Vandeputte2019-08-092-12/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When enabling atomic-sleep-debugging options in the kernel, following splat is seen when disabling the interface (which happens on boot): [ 10.892878] eth0: link down [ 10.896788] BUG: sleeping function called from invalid context at net/core/dev.c:5563 [ 10.904730] in_atomic(): 1, irqs_disabled(): 1, pid: 425, name: ip [ 10.911004] 2 locks held by ip/425: [ 10.914539] #0: (rtnl_mutex){....}, at: [<80377474>] rtnetlink_rcv_msg+0x2d8/0x380 [ 10.922441] #1: (&(&ag->lock)->rlock){....}, at: [<80330158>] ag71xx_hw_disable+0x24/0x94 [ 10.930976] CPU: 0 PID: 425 Comm: ip Not tainted 4.14.136 #0 [ 10.936716] Stack : 805e0000 80589228 80557404 876998ec 80610000 80610000 87cdcafc 805b5327 [ 10.945233] 80551534 000001a9 8061386c 87699ccc 87cfb180 00000001 876998a0 84f70903 [ 10.953751] 00000000 00000000 80b00000 8769979c 6a7407fa 00000000 00000007 00000000 [ 10.962270] 000000b7 16d0954a 000000b6 00000000 80000000 87cb658c 87cb65b0 00000001 [ 10.970787] 8046f97c 87699ccc 87cfb180 87ff2810 00000003 802ce724 0806e098 80610000 [ 10.979306] ... [ 10.981797] Call Trace: [ 10.984287] [<8006cb0c>] show_stack+0x58/0x100 [ 10.988814] [<800aab34>] ___might_sleep+0x100/0x120 [ 10.993774] [<8035c434>] napi_disable+0x30/0xd8 [ 10.998377] [<80330198>] ag71xx_hw_disable+0x64/0x94 [ 11.003418] [<8033069c>] ag71xx_stop+0x24/0x38 [ 11.007959] [<80359e30>] __dev_close_many+0xcc/0x104 [ 11.013009] [<80362eac>] __dev_change_flags+0xc8/0x1ac [ 11.018227] [<80362fb8>] dev_change_flags+0x28/0x70 [ 11.023182] [<80376890>] do_setlink+0x31c/0x91c [ 11.027786] [<80379360>] rtnl_newlink+0x3ec/0x7f8 [ 11.032563] [<80377498>] rtnetlink_rcv_msg+0x2fc/0x380 [ 11.037799] [<8039a734>] netlink_rcv_skb+0xd4/0x178 [ 11.042754] [<80399d10>] netlink_unicast+0x168/0x250 [ 11.047796] [<8039a2d4>] netlink_sendmsg+0x3d8/0x434 [ 11.052841] [<8033f0e4>] ___sys_sendmsg+0x1dc/0x290 [ 11.057794] [<80340140>] __sys_sendmsg+0x54/0x84 [ 11.062495] [<8007212c>] syscall_common+0x34/0x58 This is caused by calling napi_disable() while holding the spinlock. Fix it by omitting the spinlock, which is not required here Extensively tested on GL-MiFi, RB-912 and RB-922 hardware Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.137Koen Vandeputte2019-08-096-10/+10
| | | | | | | | | 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.136Koen Vandeputte2019-08-0627-172/+59
| | | | | | | | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 306-v4.16-netfilter-remove-saveroute-indirection-in-struct-nf_.patch Remove upstreamed: - 100-powerpc-4xx-uic-clear-pending-interrupt-after-irq-ty.patch - 088-0002-i2c-qup-fixed-releasing-dma-without-flush-operation.patch - 500-arm64-dts-marvell-Fix-A37xx-UART0-register-size.patch Fixes: - CVE-2019-13648 - CVE-2019-10207 Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mpc85xx: correct OCEDO Panda LED definitionDavid Bauer2019-08-051-2/+2
| | | | | | | | WLAN0 and the unused LED are currently swapped. Fix this, so the LED behavior matches the other OCEDo devices. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit a3a2b4857eb9c926bdbce7809bf5bd92f777e967)
* ar71xx: fix HiveAP 121 PLL for 1000MDavid Bauer2019-08-011-1/+1
| | | | | | | | | | | | | The Aerohive HiveAP 121 has the wrong PLL value set for Gigabit speeds, leading to packet-loss. 10M and 100M work fine. This commit sets the Gigabit Ethernet PLL value to the correct value, fixing packet loss. Confirmed with iperf and floodping. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit cb49e46a8a4526d86270ced3ba3aa90225ca82d7)
* ar71xx: really fix Mikrotik board detectionKoen Vandeputte2019-08-011-0/+1
| | | | | | | | | | | | | | | | | | commit e09da0169a08 ("ar71xx: fix Mikrotik board detection") was generated based on testing a rb-912 board, on which detection failed. Testing on more hardware shows something fun: machine : MikroTik RouterBOARD 922UAGS-5HPacD machine : Mikrotik RouterBOARD 912UAG-5HPnD Both lowercase and uppercase are used. So ensure we support both now .. Fixes: e09da0169a08 ("ar71xx: fix Mikrotik board detection") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> (cherry picked from commit 845b2a1cfe307394f3f2144cce085bbb5e171ecc)
* kernel: bump 4.14 to 4.14.134Koen Vandeputte2019-07-314-50/+3
| | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 049-v4.20-mips-remove-superfluous-check-for-linux.patch Fixes: - CVE-2019-3846 - CVE-2019-3900 Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* imx6: bump SDMA firmware to 3.5Koen Vandeputte2019-07-311-0/+0
| | | | | | | | | | | - add uart rom script address in header of sdma firmware to support the uart driver of latest kernel working well while old firmware assume ram script used for uart driver as NXP internal legacy kernel. - add multi-fifo SAI/PDM scripts. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> (cherry picked from commit 819b6345a206ad182dd3c2d786a3d7f04e33f751)
* ath79: make target source-onlyPetr Štetiar2019-07-291-1/+1
| | | | | | | In order to prevent build of images for this release as ath79 is going to deprecate ar71xx in the next release. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ar71xx: fix Mikrotik board detectionKoen Vandeputte2019-07-291-1/+1
| | | | | | | | | | | Fix a typo in the machine type being extracted from /proc/cpuinfo which causes all Mikrotik board to be undetected properly. This lead to sysupgrade issues and probably some others too. Fixes: 76c963bb01fb ("ar71xx: base-files: fix board detect on new MikroTik devices") Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: fix WLAN LED names for Archer C7Tomislav Požega2019-07-281-2/+2
| | | | | | | Update WLAN LED colour identifier for both interfaces on Archer C7 Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com> (cherry picked from commit 65762cdd2223d759f5836214143888e32ce5766b)
* ar71xx: fix system LED names on Archer C5/C7Tomislav Požega2019-07-281-2/+2
| | | | | | | | Move system LED board definitions of Archer C5/C7 to reflect actual system LED colour used Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com> (cherry picked from commit a73934fc9ad05207e79a3e58abc3d14eee28b6f2)
* ar71xx: Archer C7 v1 LED names and RFKILL fixesTomislav Požega2019-07-281-10/+10
| | | | | | | | | | | All leds on these boards are green. v1 has RFKILL GPIO 23 for production units (it had GPIO 13 only for test phase units, and these are rather very rare to find). As for the previous attempt to fix this and revert due to WDR boards have blue leds, it was wrong: WDR board does not use common setup (false). Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com> (cherry picked from commit c79c001b593bd826d51722f2c83ad8770255f3b3)
* ar71xx: update qca-usb-quirks patchTomislav Požega2019-07-281-1/+1
| | | | | | | | Base address for USB0 has changed from 0x18116c94 on AR934X to 0x18116d94 on QCA9558. CP Typo remained for years here... Signed-off-by: Tomislav Požega <pozega.tomislav@gmail.com> (cherry picked from commit fd5aa19480b92045db224a2d2450680e9fe66385)
* ramips: add support for ASUS RT-AC57UDavid Bauer2019-07-213-4/+167
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SoC: MediaTek MT7621AT RAM: 128M (Winbond W631GG6KB-15) FLASH: 16MB (Spansion S25FL128SA) WiFi: MediaTek MT7603EN bgn 2SS WiFi: MediaTek MT7612EN nac 2SS BTN: Reset - WPS LED: - Power - LAN {1-4} - WAN - WiFi 2.4 GHz - WiFi 5 GHz - USB UART: UART is present next to the Power LED. TX - RX - GND - 3V3 / 57600-8N1 3V3 is the nearest one to the Power LED. Installation ------------ Via TFTP: 1. Set your computers IP-Address to 192.168.1.75. 2. Power up the Router with the Reset button pressed. 3. Release the Reset button after 5 seconds. 4. Upload OpenWRT sysupgrade image via TFTP: > tftp -4 -v -m binary 192.168.1.1 -c put <IMAGE> Via SSH: Note: User/password for SSH is identical with the one used in the Web-interface. 1. Complete the initial setup wizard. 2. Activate SSH under "Administration" -> "System". 3. Transfer the OpenWrt sysupgrade image via scp: > scp owrt.bin admin@192.168.1.1:/tmp 4. Connect via SSH to the router. > ssh admin@192.168.1.1 5. Write the OpenWrt image to flash. > mtd-write -i /tmp/owrt.bin -d linux 6. Reboot the router > reboot Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 14e0e4f138e35c3e2a15cc3a836c939547ee053b)
* ath79: add support for devolo WiFi pro 1750xDavid Bauer2019-07-214-1/+64
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- CPU: Qualcomm Atheros QCA9558 RAM: 128M DDR2 FLASH: 16MiB ETH: 1x Atheros AR8035 (PoE in) WiFi2: QCA9558 3T3R WiFi5: QCA9880 3T3R BTN: 1x Reset LED: 1x LED Power (non-controllable) 1x LED Status (internal) 1x LED LAN (controlled by PHY) 1x LED WLAN BEEP: 1x GPIO attached piezo beeper UART: 3.3V GND TX RX (115200-N-8) (3.3V is square pad) Header is located next to external-LED header. Installation ------------ Make sure you set a password for the root user as prompted on first setup! 1. Upload OpenWRT sysupgrade image via SSH to the device. Use /tmp as the destination folder on the device. User is root, password the one set in the web interface. 2. Install OpenWRT with > sysupgrade -n -F /tmp/<openwrt-image-name> Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit cb3cd526948af3f69da1af18e035177a0a8f58e3)
* ar71xx: enable SGMII fixup on Mikrotik wAP ACEtienne Champetier2019-07-211-0/+16
| | | | | | | | | | | | | | | | | fixes intermittent loss of connectivity on 1Gbit port, with log message: > 803x_aneg_done: SGMII link is not ok Thanks to David Bauer for pointing me in the right direction. I just had to figure out the right bus_id, which you find in this log: > ag71xx ag71xx.1: connected to PHY at gpio-1:00 [uid=004dd074, driver=Atheros 8031 ethernet] Fixes FS#2236 Signed-off-by: Etienne Champetier <champetier.etienne@gmail.com> [Wrapped commit message - Fixed whitespace erors] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 2a7519e29d6cbbe1eb73623ef35add0ef596fb5f)
* mt7620: disable image generation for Netgear EX2700Petr Štetiar2019-07-201-1/+1
| | | | | | | | | Image generation is currently failing on builbots due to the following error: WARNING: Image file [...] mt7620-ex2700-squashfs-factory.bin is too big Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: add modern network modules to Generic targetAlberto Bursi2019-07-201-1/+2
| | | | | | | | | | | | | | | | Many Atom-based embedded/industrial x86 boards can't run 64bit operating systems due to either processor or board firmware limitations, but they have modern interfaces (PCIe) or have modern Intel gigabit controllers onboard. With the current default package selection for x86 Generic target their network won't work. Add the modern gigabit network modules needed or most likely going to be used as add-in cards, similar to what is the list on x86_64 target. Signed-off-by: Alberto Bursi <alberto.bursi@outlook.it> [fixed whitespace issue] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit bb27cde2579b0273c464e5ccd3dda7d14e84fd23)
* ath25: disable image generation for ubnt2 and ubnt5 devicesPetr Štetiar2019-07-201-2/+2
| | | | | | | | | | | | | | | | Image generations is currently failing on builbots due to the following errors: mkfwimage -B XS2 -v XS2 [...] ath25-ubnt2-squashfs-sysupgrade.bin ERROR: Failed creating firmware layout description - error code: -2 mkfwimage -B XS5 -v XS5 [...] ath25-ubnt5-squashfs-sysupgrade.bin ERROR: Failed creating firmware layout description - error code: -2 That cryptic -2 error simply means, that kernel+rootfs doesn't fit into the firmware partition. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: Use -v1 suffix for TP-Link WDR3600/4300Adrian Schmutzler2019-07-175-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>
* ath79: ar9330: add missing watchdog nodePetr Štetiar2019-07-171-0/+10
| | | | | | | | | It was reported in FS#2385, that Carambola2 doesn't currently have working watchdog so fix it by adding watchdog node. Ref: FS#2385 Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 0893f28e19afbd9d4081f59df10631d6ef02e0d7)
* ar71xx: fix nand init issues on some rb2011 devicesKoen Vandeputte2019-07-121-1/+5
| | | | | | | | | | | | | | | | | | | | While flashing lots of RB2011 devices, I noticed that some of them refused to boot properly, failing over the NAND parameters. Checking in detail shows that some device seem to use another NAND flash which only support standard 2048-byte pages, without 512-byte subpage support. This commit disables usage of these small subpage completely. Advantages: - Both NAND's with(out) subpage support are working now - The nand speed increases a bit (measured roughly 1%) in typical usecases Disadvantages: - The maximum storage capacity decreases by ~0.2% as small changes can consume a full page (2048 bytes) now. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.133Koen Vandeputte2019-07-121-5/+5
| | | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2019-3900 Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: cherry pick patch removing __linux__ checkFredrik Olofsson2019-07-101-0/+47
| | | | | | | | | | | This is already included in newer upstream. Needed to build BPF programs using the MIPS kernel include files. Without this patch, clang fails with "#error Use a Linux compiler or give up." in sgidefs.h when building BPF programs. Signed-off-by: Fredrik Olofsson <fredrik.olofsson@anyfinetworks.com> (cherry-picked from commit 7d96c301d6afc9f360c26b404e435e8e03c1e207)
* kernel: bump 4.14 to 4.14.132Koen Vandeputte2019-07-094-7/+7
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mpc85xx: Use gzip compressed kernel on HiveAP-330Pawel Dembicki2019-07-051-1/+1
| | | | | | | | | | | | | | | | | | | After commit 1e41de2f48 ("mpc85xx: convert TL-WDR4900 v1 to simpleImage") XZ compression of zImage was enabled. This change exposed a problem with the HiveAP-330 images, which was fixed by foregoing the compression on the kernel altogether with commit 98089bb8ba8 ("mpc85xx: Use uncompressed kernel on the HiveAP-330"). This patch adds back the gzip compression of the kernel image by utilizing the generic OpenWRT uImage method instead of relying on the PowerPC bootwrapper script that did it previously. Compile-tested: p1020/hiveap-330 Tested-by: Chris Blake <chrisrblake93@gmail.com> [run-tested] Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [filled in even more text]
* lantiq: enable STP where referencedMathias Kresin2019-07-032-0/+2
| | | | | | | | | | | While moving common used parts to dtsi files, the was disabled by default but not enabled for all boards using the STP. Fixes: f519fea4c6db ("lantiq: kernel 4.14: cleanup dts files") Reported-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me> Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* 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> (cherry picked from commit 8c7d6c47a7893db689e50e1917479ad07a96547a)
* 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> (cherry picked from commit 95c1dc5e8678a1fd87234a4d77c8c6643703023c)
* mvebu: fix regression for non-generic ESPRESSObin versionsVladimir Vid2019-06-282-2/+6
| | | | | | | | | | | | | | When targets for multiple ESPRESSObin devices were added, not all files were updated which means any ESPRESSObin version beside generic won't have proper networking, sysupgrade and uboot-env. This patch fixes the issue. * fixup network detection * fixup uboot-env * fixup platform.sh for sysupgrade Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr> (cherry picked from commit bc47285cb3c0125424e628521f905f1f0d7b4cef)
* mvebu: image: fix generic-arm64.bootscript mmc selectionVladimir Vid2019-06-281-2/+8
| | | | | | | | | | | Not all versions of ESPRESSObin require SD card, but can be booted from the internal emmc flash (mmc dev 1) instead. Add a simple check in the bootscript to see which mmc device is detected and boot from it using mmcdev variable. Tested-by: Tomasz Maciej Nowak <tomek_n@o2.pl> Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr> (cherry picked from commit 008b41b9b0ddd4c5c877a769a85d27eb9c4e21a4)
* ramips: mt7621: add IRQ for GPIO nodeChuanhong Guo2019-06-271-0/+3
| | | | | | | This makes interrupt-based gpio-keys working. Signed-off-by: Chuanhong Guo <gch981213@gmail.com> (cherry picked from commit 110daa16e44bb53941a18396ab6a7d9fdd1fa362)
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 13:26:09 +0000