aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu
Commit message (Collapse)AuthorAgeFilesLines
* mvebu: reduce speed to gen1 for espressobin pcieTomasz Maciej Nowak2018-06-192-0/+116
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the beginning there's been an issue with initializing the Atheros based MiniPCIe wireless cards. Here's an example of kerenel log: OF: PCI: host bridge /soc/pcie@d0070000 ranges: OF: PCI: MEM 0xe8000000..0xe8ffffff -> 0xe8000000 OF: PCI: IO 0xe9000000..0xe900ffff -> 0xe9000000 advk-pcie d0070000.pcie: link up advk-pcie d0070000.pcie: PCI host bridge to bus 0000:00 pci_bus 0000:00: root bus resource [bus 00-ff] pci_bus 0000:00: root bus resource [mem0xe8000000-0xe8ffffff] pci_bus 0000:00: root bus resource [io 0x0000-0xffff](bus address[0xe9000000-0xe900ffff]) pci 0000:00:00.0: BAR 0: assigned [mem0xe8000000-0xe801ffff 64bit] pci 0000:00:00.0: BAR 6: assigned [mem0xe8020000-0xe802ffff pref] [...] advk-pcie d0070000.pcie: Posted PIO Response Status: CA,0xe00 @ 0x3c advk-pcie d0070000.pcie: Posted PIO Response Status: CA,0xe00 @ 0x44 advk-pcie d0070000.pcie: Posted PIO Response Status: CA,0xe00 @ 0x4 ath9k 0000:00:00.0: enabling device (0000 -> 0002) advk-pcie d0070000.pcie: Posted PIO Response Status: CA,0xe00 @ 0x3c advk-pcie d0070000.pcie: Posted PIO Response Status: CA,0xe00 @ 0xc advk-pcie d0070000.pcie: Posted PIO Response Status: CA,0xe00 @ 0x4 advk-pcie d0070000.pcie: Posted PIO Response Status: CA,0xe00 @ 0x40 ath9k 0000:00:00.0: request_irq failed advk-pcie d0070000.pcie: Posted PIO Response Status: CA,0xe00 @ 0x4 ath9k: probe of 0000:00:00.0 failed with error -22 The same happens for ath5k cards, while ath10k card didn't appear at all (not detected): OF: PCI: host bridge /soc/pcie@d0070000 ranges: OF: PCI: MEM 0xe8000000..0xe8ffffff -> 0xe8000000 OF: PCI: IO 0xe9000000..0xe900ffff -> 0xe9000000 advk-pcie d0070000.pcie: link never came up advk-pcie d0070000.pcie: PCI host bridge to bus 0000:00 pci_bus 0000:00: root bus resource [bus 00-ff] pci_bus 0000:00: root bus resource [mem0xe8000000-0xe8ffffff] pci_bus 0000:00: root bus resource [io 0x0000-0xffff](bus address[0xe9000000-0xe900ffff]) advk-pcie d0070000.pcie: config read/write timed out Following the issue on esppressobin.net forum [1] the workaround seems to be limiting the speed of PCIe bridge to 1st generation. This fixed the initialisation of all tested Atheros wireless cards. The change shouldn't affect the performance for wireless cards, it could reduce the performance of storage controller cards but since OpenWrt focuses on wireless connectivity, fixing compatibility with wireless cards should be a priority. For the record, the iwlwifi and mt76 cards were not affected by this issue. 1. http://espressobin.net/forums/topic/which-pcie-wlan-cards-are-supported Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (cherry picked from commit 772258044b48036699302840abf96cd34c4e5078)
* mvebu: add fix for armada 37xx cpufreq driverTomasz Maciej Nowak2018-06-191-0/+35
| | | | | | | Backport from stable kernel tree fixing clock leak. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl> (cherry picked from commit 4ec8c8c23ed50dbe9cabbfc544ae2780f0287fd0)
* mvebu: backport ahci_mvebu errata patchsetJeremiah McConnell2018-06-182-0/+334
| | | | | | | | | | | | | Marvell ahci hardware requires a workaround to prevent eSATA failures on hotplug/reset when used with multi-bay external enclosures. Errata Ref#226 - SATA Disk HOT swap issue when connected through Port Multiplier in FIS-based Switching mode. These patches backport the workaround from 4.17. Signed-off-by: Jeremiah McConnell <miah@miah.com> (cherry picked from commit e820455198aa50cc32f9a108a4696f0cc23023c3)
* mvebu: enable SATA port multiplier supportJeremiah McConnell2018-06-181-0/+1
| | | | | | | | | | | Some of the Marvell targets have functional SATA port multiplier support, which is required for multi-bay eSATA enclosures. Enable kernel support by setting CONFIG_SATA_PMP. Closes: FS#1232 and FS#547 Signed-off-by: Jeremiah McConnell <miah@miah.com> (cherry picked from commit 390c4df2c0b2e7b31c52eca3dcba139b0d745a97)
* kernel: bump 4.14 to 4.14.48 for 18.06Stijn Segers2018-06-077-45/+45
| | | | | | | | | | | | | | Refreshed patches. The following patches were upstreamed and have been deleted: * target/linux/lantiq/patches-4.14/0025-MIPS-lantiq-gphy-Remove-reboot-remove-reset-asserts.patch * target/linux/generic/pending-4.14/101-clocksource-mips-gic-timer-fix-clocksource-counter-w.patch * target/linux/generic/pending-4.14/103-MIPS-c-r4k-fix-data-corruption-related-to-cache-coherence.patch * target/linux/generic/pending-4.14/181-net-usb-add-lte-modem-wistron-neweb-d18q1.patch Compile-tested: ramips/mt7621, x86/64 Run-tested: ramips/mt7621 Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: fix broken console on WRT32X (venom)Michael Gray2018-06-013-0/+208
| | | | | | | | | | | | | | | | The console bootarg is being corrupted on boot, causing various issues including broken sysupgrade. Utilising the bootargs mangle patch from other targets, hardcode the console arguments and fetch the rootfs from the bootloader. Kernel command line: console=ttyS0,115200 root=/dev/mtdblock8 Bootloader command line (ignored): console= root=/dev/mtdblock8 Please cherry pick to 18.06 too Signed-off-by: Michael Gray <michael.gray@lantisproject.com> (cherry picked from commit 4fdc6ca31bda4aad2a65b8460b0caa5c60f87f41)
* kernel: enable THIN_ARCHIVES by defaultSergey Ryazanov2018-05-241-1/+0
| | | | | | | | | THIN_ARCHIVES option is enabled by default in the kernel configuration and no one target config disables it. So enable it by default and remove this symbol from target specific configs to keep them light. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 67a3cdcbb05559549985a189eabaf2df92559ed7)
* kernel: enable FUTEX_PI by defaultSergey Ryazanov2018-05-241-1/+0
| | | | | | | | | | New FUTEX_PI configuration symbol enabled if FUTEX and RT_MUTEX symbols are enabled. Both of these symbols are enabled by default in the generic config, so enable FUTEX_PI by default too to keep platform specific configs minimal. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit bdc2b58c4bccb50242af853dc80b50f9324b841c)
* kernel: enable EXPORTFS by defaultSergey Ryazanov2018-05-241-1/+0
| | | | | | | | | OVERLAY_FS config symbol selects EXPORTFS since 4.12 kernel, we have OVERLAY_FS enabled by default, so enable EXPORTFS in the generic config of 4.14 and remove this option from platform specific configs. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit a08b0d0c3149060f1585ad3ea2ea3edfde71bce4)
* kernel: disable DRM_LIB_RANDOM by defaultSergey Ryazanov2018-05-241-1/+0
| | | | | | | | DRM_LIB_RANDOM config symbol selected only by DRM_DEBUG_MM_SELFTEST which is disable by default, so disable DRM_LIB_RANDOM by default too. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit 978543a246c6badb5e5e1c2430211e01f005af27)
* kernel: disable DMA_{NOOP|VIRT}_OPS by defaultSergey Ryazanov2018-05-241-2/+0
| | | | | | | | These options do not used by any supported arch, so disable them by default to make arch configs a bit more clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit ead26e9db649a508ba93e7e8193ada70322620b1)
* kernel: disable ARCH_WANTS_THP_SWAP by defaultSergey Ryazanov2018-05-241-1/+0
| | | | | | | | | Only one arch (x86_64) enables this option. So disable ARCH_WANTS_THP_SWAP by default and remove referencies to it from all configs (except x86_64) to make them clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com> (cherry picked from commit f928c338ad6c8215a5fe280473e37786157a2d05)
* kernel: bump 4.14 to 4.14.43 for 18.06Koen Vandeputte2018-05-245-330/+6
| | | | | | | | | | | | | | | | | | | | | Refreshed all patches Dropped upstreamed patches: 522-PCI-aardvark-fix-logic-in-PCI-configuration-read-write-functions.patch 523-PCI-aardvark-set-PIO_ADDR_LS-correctly-in-advk_pcie_rd_conf.patch 525-PCI-aardvark-use-isr1-instead-of-isr0-interrupt-in-legacy-irq-mode.patch 527-PCI-aardvark-fix-PCIe-max-read-request-size-setting.patch updated patches: 524-PCI-aardvark-set-host-and-device-to-the-same-MAX-payload-size.patch 030-USB-serial-option-fix-dwm-158-3g-modem-interface.patch Added new ARM64 symbol: CONFIG_ARM64_ERRATUM_1024718 Compile-tested on: cns3xxx, imx6, mvebu (arm64), x86_64 Runtime-tested on: cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mvebu: add support for WRT32X (venom)Michael Gray2018-05-1413-7/+241
| | | | | | | | | | | | | | | | | | Linksys WRT32X (Venom) is identical in hardware to the WRT3200ACM with a different flash layout and boots zImage rather than uImage. Specification: - Marvell Armada 385 88F6820 (2x 1.8GHz) - 256MB of Flash - 512MB of RAM - 2.4GHz (bgn) and 5GHz (an+ac wave 2) - 4x 1Gbps LAN + 1x 1Gbps WAN - 1x USB 3.0 and 1x USB 2.0/eSATA (combo port) Flash instruction: Apply factory image via web-gui. Signed-off-by: Michael Gray <michael.gray@lantisproject.com>
* arm64: enable harden branch predictorMathias Kresin2018-04-272-0/+4
| | | | | | Enable the harden branch predictor for arm64 as it is recommend. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: cortexa72: enable Marvell 10G PHY by defaultDamir Samardzic2018-04-251-0/+1
| | | | | | This one enables 10 GbE ports on MACCHIATObin. Signed-off-by: Damir Samardzic <damir.samardzic@sartura.hr>
* mvebu: drop linux 4.4 and 4.9 supportFelix Fietkau2018-04-19147-26085/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: bump 4.14 to 4.14.34Stijn Tintel2018-04-161-1/+1
| | | | | | | | | | | | | Refresh patches. Update patches that no longer apply: - backport/313-netfilter-remove-defensive-check-on-malformed-packet.patch - pending/642-net-8021q-support-hardware-flow-table-offload.patch Compile-tested: x86/64. Runtime-tested: x86/64. Signed-off-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: update kernel 4.14 to 4.14.32Hauke Mehrtens2018-04-032-11/+7
| | | | | | | | | | | | | The following patches are now included upstream: * 0052-MIPS-lantiq-fix-usb-clocks.patch * 0053-MIPS-lantiq-enable-AHB-Bus-for-USB.patch * 0060-lantiq-ase-enable-MFD-SYSCON.patch Closes: FS#1466 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mvebu: add support for MACCHIATObin (cortex-a72)Damir Samardzic2018-03-319-3/+171
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add initial support for Marvell MACCHIATObin, cortex-a72 based Marvell ARMADA 8040 Community board. Comes in two forms: Single Shot and Double Shot. Specifications: - Quad core Cortex-A72 (up to 2GHz) - DDR4 DIMM slot with optional ECC and single/dual chip select support - Dual 10GbE (1/2.5/10GbE) via copper or SFP 2.5GbE (1/2.5GbE) via SFP 1GbE via copper - SPI Flash - 3 X SATA 3.0 connectors - MicroSD connector - eMMC - PCI x4 3.0 slot - USB 2.0 Headers (Internal) - USB 3.0 connector - Console port (UART) over microUSB connector - 20-pin Connector for CPU JTAG debugger - 2 X UART Headers - 12V input via DC Jack - ATX type power connector - Form Factor: Mini-ITX (170 mm x 170 mm) More details at http://macchiatobin.net Booting from micro SD card: 1. reset U-Boot environment: env default -a saveenv 2. prepare U-Boot with boot script: setenv bootcmd "load mmc 1:1 0x4d00000 boot.scr; source 0x4d00000" saveenv or manually: setenv fdt_name armada-8040-mcbin.dtb setenv image_name Image setenv bootcmd 'mmc dev 1; ext4load mmc 1:1 $kernel_addr $image_name;ext4load mmc 1:1 $fdt_addr $fdt_name;setenv bootargs $console root=/dev/mmcblk1p2 rw rootwait; booti $kernel_addr - $fdt_addr' saveenv Signed-off-by: Damir Samardzic <damir.samardzic@sartura.hr>
* mvebu: clearfog-pro: set new DTB name in boot-scriptJosua Mayer2018-03-311-0/+4
| | | | | | | The DTB for Clearfog Pro has been renamed in mainline. However U-Boot hasn't picked up that change yet :(, so we need to hardcode it for now. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: Add support for WRT3200ACM with new NAND flashImre Kaloz2018-03-315-2/+23
| | | | | | | | Newer Linksys boards might come with a Winbond W29N02GV which can be configured in different ways. Make sure we configure it the same way as the older chips so everything keeps working. Signed-off-by: Imre Kaloz <kaloz@openwrt.org>
* mvebu: Get rid of RTC hack for Turris Omnia.Rosen Penev2018-03-311-1/+1
| | | | | | As Solidrun's RTC patch got merged, this hack is no longer needed. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* mvebu: disable cpu idle on WRT1900ACv1Felix Fietkau2018-03-191-0/+10
| | | | | | | | | | | | | | | A regression seriously affecting the Linksys WRT1900ACv1 (Mamba) was introduced some time between the OpenWrt/LEDE v4.4 and v4.9 kernels. The root cause has not yet been identified, despite many attempts for more than a year. Disabling the SoC specific CPU idle support should mitigate this issue. The symptoms on an affected system are unwanted reboots at a variable frequency. In many cases almost immediately after boot, causing a bootloop. This effectively disables support for Mamba on OpenWrt with kernels > v4.4. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* mvebu: Disable internal RTC on Linksys devicesHauke Mehrtens2018-03-171-0/+28
| | | | | | | | | | The internal RTC does not work correctly on these Linksys boards based on Marvell SoCs. It is off by 3 minutes in 10 minutes running, this was reported by multiple users. On the Linksys Mamba device the device tree comment says that no crystal is connected to the internal RTC, this is probably also true for the other devices. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: Add Solidrun RTC init patch.Rosen Penev2018-03-171-0/+74
| | | | | | | | Some boards like the Turris Omnia have an RTC chip that does not get initialized. Initializing the RTC at the driver level helps get rid of bootloader hacks that write special register values. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* mvebu: Backport RTC trimming support.Rosen Penev2018-03-171-0/+143
| | | | | | This enables a higher precision mode for the RTC. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* mvebu: unset uboot build by defaultMathias Kresin2018-03-152-1/+2
| | | | | | | | Initialise the UBOOT variable by default. Otherwise it will be unintended inherit to following images if set and causes an uboot build where not required. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: make mtd patches apply againHauke Mehrtens2018-03-152-10/+10
| | | | | | | | | This makes some of the mtd patches apply again after some generic patches were changed. These problems where found by build bot. Fixes: ac9bcefa3b044 ("kernel: use V10 of mtd patchset adding support for "compatible" string") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: new subtarget cortex A53Tomasz Maciej Nowak2018-03-1026-6/+1806
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit introduces new subtarget for Marvell EBU Armada Cortex A53 processor based devices. The first device is Globalscale ESPRESSObin. Some hardware specs: SoC: Marvell Armada 3700LP (88F3720) dual core ARM Cortex A53 processor up to 1.2GHz RAM: 512MB, 1GB or 2GB DDR3 Storage: SATA interface µSD card slot with footprint for an optional 4GB EMMC 4MB SPI NOR flash for bootloader Ethernet: Topaz Networking Switch (88E6341) with 3x GbE ports Connectors: USB 3.0 USB 2.0 µUSB port connected to PL2303SA (USB to serial bridge controller) for UART access Expansion: 2x 46-pin GPIO headers for accessories and shields with I2C, GPIOs, PWM, UART, SPI, MMC, etc MiniPCIe slot Misc: Reset button, JTAG interface Currently booting only from µSD card is supported. The boards depending on date of dispatch can come with various U-Boot versions. For the newest version 2017.03-armada-17.10 no manual intervention should be needed to boot OpenWrt image. For the older ones it's necessary to modify default U-Boot environment: 1. Interrupt boot process to run U-Boot command line, 2. Run following commands: (for version 2017.03-armada-17.06 and 2017.03-armada-17.08) setenv bootcmd "load mmc 0:1 0x4d00000 boot.scr; source 0x4d00000" saveenv (for version 2015.01-armada-17.02 and 2015.01-armada-17.04) setenv bootargs "console=ttyMV0,115200 root=/dev/mmcblk0p2 rw rootwait" setenv bootcmd "ext4load mmc 0:1 ${fdt_addr} armada-3720-espressobin.dtb; ext4load mmc 0:1 ${kernel_addr} Image; booti ${kernel_addr} - ${fdt_addr}" saveenv 3. Poweroff, insert SD card with OpenWrt image, boot and enjoy. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: Add subtarget for Cortex A9 buildHauke Mehrtens2018-03-104-158/+181
| | | | | | This is in preparation for adding a subtarget for the Cortex A53 later. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: add support for Turris OmniaRyan Mounce2018-03-106-3/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds support for the Turris Omnia and builds an eMMC sysupgrade image in the same format as the SolidRun ClearFog. An initramfs image in the simple yet Omnia-specific 'medkit' image format is also built in order to ease the initial flashing process. Notable hardware support omissions are support for switching between SFP cage and copper PHY, and RGB LED control. Due to a current limitation of DSA, only 1/2 CPU switch uplinks are used. Specifications: - Marvell Armada 385 1.6GHz dual-core ARMv7 CPU - 1GB DDR3 RAM - 8GB eMMC Flash - 5x Gigabit LAN via Marvell 88E6176 Switch (2x RGMII CPU ports) - 1x switchable RJ45 (88E1514 PHY) / SFP SGMII WAN - 2x USB 3.0 - 12x dimmable RGB LEDs controlled by independent MCU - 3x Mini PCIe slots - Optional Compex WLE200N2 Mini PCIe AR9287 2x2 802.11b/g/n (2.4GHz) - Optional Compex WLE900VX Mini PCIe QCA9880 3x3 802.11ac (2.4 / 5GHz) - Optional Quectel EC20 Mini PCIe LTE modem Flash instructions: If the U-Boot environment has been modified previously (likely manually via serial console), first use serial to reset the default environment. => env default -a => saveenv Method 1 - USB 'medkit' image w/o serial - Copy openwrt-mvebu-turris-omnia-sysupgrade.img.gz and omnia-medkit-openwrt-mvebu-turris-omnia-initramfs.tar.gz to the root of a USB flash drive formatted with FAT32 / ext2/3/4 / btrfs / XFS. Note that the medkit MUST be named omnia-medkit*.tar.gz - Disconnect other USB devices from the Omnia and connect the flash drive to either USB port. - Power on the Omnia and hold down the rear reset button until 4 LEDs are illuminated, then release. - Wait approximately 2 minutes for the Turris Omnia to flash itself with the temporary image, during which LEDs will change multiple times. - Connect a computer to a LAN port of the Turris Omnia with a DHCP client - (if necessary) ssh-keygen -R 192.168.1.1 - ssh root@192.168.1.1 $ mount /dev/sda1 /mnt $ sysupgrade /mnt/openwrt-mvebu-turris-omnia-sysupgrade.img.gz - Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself and you can remove the flash drive. Method 2 - TFTP w/ serial - Extract omnia-medkit-openwrt-mvebu-turris-omnia-initramfs.tar.gz and copy dtb + zImage to your TFTP server (rename if desired) - Connect Turris Omnia WAN port to DHCP-enabled network with TFTP server - Connect serial console and interrupt U-Boot => dhcp => setenv serverip <tftp_server_ip_here> => tftpboot 0x01000000 zImage => tftpboot 0x02000000 dtb => bootz 0x01000000 - 0x02000000 - OpenWrt will now boot from ramdisk - Download openwrt-mvebu-turris-omnia-sysupgrade.img.gz to /tmp/ $ sysupgrade /tmp/openwrt-mvebu-turris-omnia-sysupgrade.img.gz - Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* mvebu: generate ramdisk image by defaultRyan Mounce2018-03-091-1/+1
| | | | | | | ramdisk images must be used in the installation process for upcoming Turris Omnia support. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* mvebu: disable DSA DT nodes for boards using mvsw61xxRyan Mounce2018-03-092-1/+31
| | | | | | | | As at this commit, DSA is not enabled in the kernel config for mvebu, so these nodes have been ignored. In preparation for the first mvebu board using DSA, disable these nodes for existing boards to avoid issues. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* kernel: bump 4.14 to 4.14.23Stijn Segers2018-03-023-4/+4
| | | | | | | | | | | | | This patch bumps the 4.14 kernel to .23. - Refreshed patches. - Deleted bcm53xx/patches-4.14/089-PCI-iproc-Fix-NULL-pointer-dereference-for-BCMA.patch. Has been accepted upstream. - Deleted generic/pending-4.14/821-usb-Remove-annoying-warning-about-bogus-URB.patch. The upstream URB code was changed, the patch no longer applies. I discussed this with the patch author and removed it for now, we'll see how it goes. Compile-tested on: ramips/mt7621, x86/64 Run-tested on: ramips/mt7621, x86/64 Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: base-files: moving on from net-toolsTomasz Maciej Nowak2018-03-021-4/+4
| | | | | | | Remove dependency on net-tools, replacing calls to ifconfig with iproute equivalent, in functions changing interface MAC addresses. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: rename clearfog sysupgrade script and functionsTomasz Maciej Nowak2018-03-022-5/+5
| | | | | | | | Cosmetic name change of ClearFog sysupgrade script and its functions to more generic sdcard. This way it won't be confusing for other future device additions. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: remove fs declaration in mount commandsTomasz Maciej Nowak2018-03-022-2/+3
| | | | | | | Allows to have other file system for boot partition without breaking sysupgrade. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: unify boot.scr creationTomasz Maciej Nowak2018-03-023-13/+8
| | | | | | | Unify boot.scr generation so Makefile for device image generation won't grow without a reason. Also make boot-scr step optional. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: make sdcard bootloader option configurableTomasz Maciej Nowak2018-03-022-10/+21
| | | | | | | Remove the necessity for boot loader from SD card image creation process and make it configurable. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: fix partition type and signature for sdcardTomasz Maciej Nowak2018-03-022-4/+7
| | | | | | | | | | | Previously the partition signature was assigned from provided type. Now both are corrected wherein signature is always generated from SOURCE_DATE_EPOCH. With that the root file system can be identified by PARTUUID string, without relying on static declaration of device node. This commit also does some cosmetics, removing trailing whitespace and replacing spaces with tab. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: remove redefinition of image name for clearfogTomasz Maciej Nowak2018-03-021-2/+0
| | | | | | | | The IMAGE_NAME redefinition causes overwriting of generated SD card image when multiple root file system types are selected. In result only single SD card image is generated. This commit fixes this behaviour. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: clearfog: use partition uuid for root= bootargJosua Mayer2018-03-022-12/+14
| | | | | | | | | | | U-Boot already knows where it found the boot.scr, and figuring out the partition UUID becomes trivial at this point. This change allows booting OpenWrt from whatever storage it has been flashed to: SD card, eMMC, USB disk or SATA disk. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> [replace lede with openwrt, redact commit message] Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: Use kernel 4.14 by defaultHauke Mehrtens2018-03-021-1/+1
| | | | | | I am not aware of any regressions in kernel 4.14 compared to kernel 4.9. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: activate more workarounds for ARM erratasHauke Mehrtens2018-03-022-0/+2
| | | | | | | | | The Armada XP uses a Marvell PJ4Bv7 Processor for which already one workaround for an errata is activated. The Armada 285 uses a Cortex A9 r4p1 for which the Linux kernel provides a workaround for ERRATA_764369, activate this. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mwlwifi: add and use individual firmware packagesJohnny S. Lee2018-02-262-2/+7
| | | | | | | | | | | | | | | | | | | | | | | | As each mvebu device only uses one of the firmwares provided by mwlwifi package, it makes sense to put them in separate packages and only install the one that is needed. Current mwlwifi version's firmware sizes and usages by devices: 88W8864.bin 118776 caiman, mamba, cobra, shelby 88W8897.bin 489932 (none) 88W8964.bin 449420 rango Changes by this commit: * indicate in title that mwlwifi also is driver for 88W8897 and 88W8964 * remove mwlwifi package's firmware installation rules * add 3 new individual firmware packages (all depends on kmod-mwlwifi): - mwlwifi-firmware-88w8864 - mwlwifi-firmware-88w8897 - mwlwifi-firmware-88w8964 * add firmware package to mvebu devices' DEVICE_PACKAGES accordingly Signed-off-by: Johnny S. Lee <_@jsl.io> [Add the used FW files to the PACKAGES of default image] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: add missing patch for reprobing SFP phys for 4.14Jonas Gorski2018-02-251-0/+98
| | | | | | | Add the patch for reprobing phys also for 4.14, as it is still needed. Fixes: 4ccad922293a ("mvebu: Add support for kernel 4.14") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* mvebu: fix SFP insert detection GPIO name on 4.14Jonas Gorski2018-02-251-1/+1
| | | | | | | | | When SFP support was accepted upstream, the expected GPIO names were slightly changed, breaking SFP insert detection. Update the DTS file to the expected name to make SFP work again. Fixes: 4ccad922293a ("mvebu: Add support for kernel 4.14") Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* kernel: refresh patchesKoen Vandeputte2018-02-221-1/+1
| | | | | | Some fuzz was introduced due to the netfilter-offload series Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* treewide: remove obsolete sysupgrade watchdog killMathias Kresin2018-02-161-10/+0
| | | | | | | | | The watchdog kill command was meant for busybox watchdog. Busybox watchdog was replaced by the procd watchdog mid 2013 with commit df7ce9301a25 ("busybox: disable the watchdog utility by default"), which makes the kill command obsolete since quite some time. Signed-off-by: Mathias Kresin <dev@kresin.me>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 02:52:22 +0000