aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ar71xx: fix TP-Link Archer C7 v5 switch LEDsRinki Kumari2018-11-171-3/+15
| | | | Signed-off-by: Rinki Kumari <rinki13@gmail.com>
* ar71xx: add support for Gainstrong MiniBox V3.2Pau Escrich2018-11-1511-0/+153
| | | | | | | | | | | | Adds MiniBox V3.2 ar71xx target (QCA99531 + QCA9887) Info: http://oolite.cn/minibox-v3-2-qca9531-qca9887-module-pin-specification.html Reference patch: http://oolite.cn/wp-content/uploads/2017/09/minibox_v3_cc15.05_20160325.patch Installation: Upload firmware to uboot via HTTP at 192.168.1.1 (press button for 5 seconds) Signed-off-by: Pau Escrich <p4u@dabax.net> Signed-off-by: Daniel Golle <daniel@makrotopia.org> (daniel@makrotopia.org: rebased and fixed conflicts, fixed LED name, added ath10k eeprom)
* kernel: fix ubifs loosing O_TMPFILE data after power cutRafał Miłecki2018-11-151-0/+89
| | | | | | | | | | | There was a bug in ubifs related to the O_TMPFILE. When reapplying changes after power cut data could be lost. This problem was exposed by overlayfs and the upstream commit 3a1e819b4e80 ("ovl: store file handle of lower inode on copy up"). This fixes a regression introduced when switching from 4.9 to 4.14. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: bump 4.14 to 4.14.81Koen Vandeputte2018-11-1411-73/+26
| | | | | | | | | | | | | | | Refreshed all patches. Removed upstreamed patches: - 081-spi-bcm-qspi-switch-back-to-reading-flash-using-smal.patch Altered patches: - 0054-cpufreq-dt-Handle-OPP-voltage-adjust-events Compile-tested on: cns3xxx, imx6, ipq806x, x86_64 Runtime-tested on: cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.137Koen Vandeputte2018-11-1445-113/+102
| | | | | | | | | | | | Refreshed all patches. Removed upstreamed hunks in: - 703-phy-support-layerscape.patch Compile-tested on: ar71xx, layerscape Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 3.18 to 3.18.125Koen Vandeputte2018-11-143-17/+17
| | | | | | | | | Refreshed all patches. Compile-tested on: adm5120 Compile-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.80Stijn Tintel2018-11-131-1/+1
| | | | | | | | | Refresh patches. Compile-tested: ar71xx, ath79, x86/64 Runtime-tested: ar71xx, ath79, x86/64 Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* bcm53xx: add DT patch describing pins mux controllerRafał Miłecki2018-11-091-0/+73
| | | | | | It's needed to support new devices that use specific pin functions. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: deprecate support for the generic "linux,part-probe" DT bindingRafał Miłecki2018-11-093-8/+19
| | | | | | | | | | | It has been rejected upstream and instead a nice/more generic solution has been implemented. It's possible now to describe partitions format using "compatible" DT string. No OpenWrt target uses "linux,part-probe" anymore, leave it only in case some forks need it. It will be dropped with support for new kernels. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: use separated mtd patch reverting write_page() removalRafał Miłecki2018-11-092-29/+68
| | | | | | | This helps understanding mtd changes needed to get downstream NAND driver working. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: update pinctrl driverRafał Miłecki2018-11-092-0/+39
| | | | | | It's upstream now with a one trivial fix. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* oxnas: remove superseded sysupgrade image checkDaniel Golle2018-11-081-10/+1
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* oxnas: kd20: correct memory size to 256MBDaniel Golle2018-11-081-2/+2
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: fix netgear r6120 factory image generationKoen Vandeputte2018-11-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | as indicated in commit c5bf408ed6bd "(ramips: fix image generation for mt76x8") more rework was needed to fix the other issues. Building on another machine, but using the same arch, showed the application failing again for different reasons. Fix this by completely rewriting the application, fixing following found issues: - buffer overflows, resulting in stack corruption - flaws in memory requirement calculations (too small, too large) - memory leaks - missing bounds checking on string handling - non-reproducable images, by using unitilized memory in checksum calculation - missing error handling, resulting in succes on specific image errors - endianness errors when building on BE machines - various minor build warnings - documentation did not match the code actions (header item locations) - allowing input to be decimal, hex or octal now Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ramips: add missing DTS frequency limit for the 5 GHz radio on Archer C20iFelix Fietkau2018-11-061-0/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* imx6: fix DMA transaction errorsKoen Vandeputte2018-11-063-23/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Following errors were seen in the past on imx6 when using serial: [ 22.617622] imx-uart 2020000.serial: DMA transaction error. [ 22.623228] imx-uart 2020000.serial: DMA transaction error. [ 22.628826] imx-uart 2020000.serial: DMA transaction error. [ 22.648951] imx-uart 2020000.serial: DMA transaction error. [ 22.654558] imx-uart 2020000.serial: DMA transaction error. [ 22.660156] imx-uart 2020000.serial: DMA transaction error. Which is the reason why DMA for the serial ports got disabled in commits: efb362cd93b0 ("imx6: disable dma on uart") 3b4241071dd4 ("imx6: disable UART dma") As indicated on mailinglist discussion, the cause seems to be the usage of very old SDMA firmware which is present in the soc: [ 0.624302] imx-sdma 20ec000.sdma: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2 [ 0.624318] imx-sdma 20ec000.sdma: Falling back to user helper [ 64.531607] imx-sdma 20ec000.sdma: external firmware not found, using ROM firmware This patch adds the new firmware binary. (2196 bytes) It is required to embed the binary into the kernel image, as it gets loaded very early in the boot process where the rootfs is not available yet: [ 0.622966] imx-sdma 20ec000.sdma: loaded firmware 3.3 Extended testing shows that the DMA errors are not seen anymore when using this newer firmware version. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: disable some tiny targets with kernel 4.14Koen Vandeputte2018-11-051-2/+0
| | | | | | | | | | | | | | | | | | | | | The bump to kernel 4.14 caused a massive increase in kernel size. For most targets, switching them to dynamic partitioning allowed to cope with this. On some targets, the kernel partition is located behind the rootfs, which disallows switching to dynamic partitioning as the boot location would be altered, requiring a u-boot change. Also within the tiny section, which disables kernel symbols etc to decrease the image size, the partition size is still too small. Disable these targets for now, fixing image generation: - Buffalo BHR-4GRV2 - Zbtlink ZBT-WE1526 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.79Koen Vandeputte2018-11-0539-68/+68
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ipq40xx: fix NBG6617 LED mappingDavid Bauer2018-11-051-3/+3
| | | | | | | | The NBG6617's LEDs are wrongly identified in the 01_leds boardinit script (board instead of boardname), resulting in referencing non-existent LEDs in UCI. Signed-off-by: David Bauer <mail@david-bauer.net>
* oxnas: add console=ttyS0,115200 argument to bootargsDaniel Golle2018-11-045-4/+15
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* oxnas: enable image metadata by setting SUPPORTED_DEVICESDaniel Golle2018-11-041-0/+5
| | | | | | | For each board, set the legacy name as well as the new based on the compatible-string from devicetree. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* oxnas: remove stray kernel config symbolsDaniel Golle2018-11-041-10/+0
| | | | | | CONFIG_CRYPTO_* shouldn't be set by the target Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* oxnas: switch to generic board detectDaniel Golle2018-11-045-85/+33
| | | | | | | remove /lib/oxnas.sh platform-specific board-detection and use generic which is based on device-tree compatible node instead. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: fix leds on GL.iNet GL-MT300N-V2Martin Weinelt2018-11-022-1/+2
| | | | | | | The WAN LED now shows the link state. It's color is green, not blue. Signed-off-by: Martin Weinelt <hexa@darmstadt.ccc.de>
* ipq-wifi: drop custom board-2.binsChristian Lamparter2018-11-011-2/+1
| | | | | | | | | | | | | The BDFs for all boards were upstreamed to the ath10k-firmware repository and linux-firmware.git. We switched to the upstream board-2.bin, hence the files can be removed here. Keep the ipq-wifi package in case new boards are added. It might take some time till board-2.bins send upstream are merged. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: nbg6617: switch to upstream boardfile variantChristian Lamparter2018-11-011-0/+2
| | | | | | | The NBG6617's boardfile was merged and this device can now switch to the upstream ath10k board-2.bin. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: rt-ac58u: replace ubi auto load hackChristian Lamparter2018-11-012-29/+4
| | | | | | | | | | | | This patch replaces the custom autoload quirk of the RT-AC58U with a bootargs-append overwrite. The vendor's u-boot doesn't leave the bootargs / cmdline alone, so the it can't be overwritten in any other way right now... And of course, this will be a lot of fun to deal with once the device switches to the new spi-nand subsystem. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ar71xx: expand kernel size for ubnt targetsKoen Vandeputte2018-10-291-2/+2
| | | | | | | | | | Kernel 4.14 is pretty large causing a build error as the partition is too small. Expand the kernel partition a bit to make it fit. * ubnt-uap-pro * ubnt-unifi-outdoor-plus Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: disable ap91-5g due to kernel sizeKoen Vandeputte2018-10-291-1/+0
| | | | | | | | | | | | This target causes a build failure as the kernel image does not fit into the kernel partition. As the kernel is located behind the rootfs, it cannot be enlarged as the boot entry location would get altered. Disable this target for now. Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: switch more targets to dynamic partitioningKoen Vandeputte2018-10-291-5/+7
| | | | | | | | | | | | | Targets: - TP-LINK ER355 - TP-LINK C25 V1 - TP-LINK C59 V1 - TP-LINK C7 V4 - TP-LINK C7 V5 Fixes build issues seen due to the kernel being too big Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: switch TP-Link RE450 v1 to dynamic partitioningRadek Dostál2018-10-291-0/+2
| | | | | | | | | | | | | | | | | As mentioned in commit 5f24933 recent changes on ar71xx (switch to 4.14, memory compaction, ...) cause an increase in kernel size, making it too big for RE450. RE450 images were not build due to the following error message: os-image partition too big (more than 1572864 bytes): Success Tested on RE450, device boots and was used to send this patch. Reported-by: Enrico Mioso <mrkiko.rs@gmail.com> Suggested-by: David Bauer <mail@david-bauer.net> Signed-off-by: Radek Dostál <rd@radekdostal.com> [rewrote commit msg keeping it tight + fixed SoB lines] Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx: move OCEDO Koala to generic and use dynamic partitioningDavid Bauer2018-10-294-14/+10
| | | | | | | | | | | This changes the OCEDO Koala flash-layout to a unified firmware partition, thus making the ar71xx-generic kernel fit in flash. Compile and runtested on OCEDO Koala. Signed-off-by: David Bauer <mail@david-bauer.net> [small title reword] Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: fix PQI Air Pen supportMathias Kresin2018-10-281-0/+0
| | | | | | Use the correct dts filename. It has to be <soc>_<manufacturer>_<device>. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ath79: add support for PQI Air PenYuheiOKAWA2018-10-284-0/+160
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SoC: AR9330 (or AR9331 revision?) Ethernet x1, Wireless 2.4G, uSD card slot x1. USB Power, include Li-Po Battery. Flash 8MiB. (factory is dual image) 1. write image is use half 4MiB size from factory. write initramfs image to mtd6 and mtd7. 2. change next boot setting. next is mtd6 boot. echo -ne "\x01" | dd of=/dev/mtdblock8 conv=notrunc bs=1 count=1 seek=0 3. rewrite sysupgrade image. change next boot setting. next is mtd4. echo -ne "\x00" | dd of=/dev/mtdblock8 conv=notrunc bs=1 count=1 seek=0 OEM mtd. dev: size erasesize name mtd0: 00040000 00010000 "u-boot" mtd1: 00010000 00010000 "u-boot-env" mtd2: 00010000 00010000 "ART" mtd3: 00010000 00010000 "NVRAM" mtd4: 00140000 00010000 "uImage" mtd5: 00280000 00010000 "rootfs" mtd6: 00140000 00010000 "uImage2" mtd7: 00280000 00010000 "rootfs2" mtd8: 00010000 00010000 "CONF" Signed-off-by: YuheiOKAWA <tochiro.srchack@gmail.com>
* ath79: Add support for Ubiquiti LiteAP ac (LAP-120)Roger Pueyo Centelles2018-10-284-0/+54
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds support for the Ubiquiti LiteAP ac (LAP-120), an outdoor 5 GHz AC access point with an integrated 120° 16 dBi antenna. The device was previously known as LiteBeam AP ac but was later rebranded. CPU: Atheros AR9342 SoC RAM: 64 MB DDR2 Flash: 16 MB NOR SPI Ports: 1 GbE port (PoE in) WLAN: 5 GHz QCA899X (PCI) The integrated QCA899X is a Ubiquiti branded part with modified vendor and product id (0777:11ac9). It is very similar to the NanoStation loco AC, except for the 2.4 GHz management radio (missing here). Installation procedure is the same as the NanoStation [loco] AC: 1. Connect to serial header on device 2. Power on device and enter uboot console 3. Set up tftp server serving an openwrt initramfs build 4. Load initramfs build using the command tftpboot in the uboot cli 5. Boot the loaded image using the command bootm 6. Copy squashfs openwrt sysupgrade build to the booted device 7. Use mtd to write sysupgrade to partition "firmware" 8. Reboot and enjoy Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net>
* kernel: add missing symbol for target bcm53xxKoen Vandeputte2018-10-231-0/+1
| | | | | | | Fixes: ca88f4153f8f ("kernel: bump 4.14 to 4.14.77") Reported-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* bcm53xx: use upstream SPI controller fixRafał Miłecki2018-10-231-3/+5
| | | | | | This just moves patch to use 0xx prefix and includes maintainer's s-o-b. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: bump 4.14 to 4.14.78Koen Vandeputte2018-10-225-57/+9
| | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 050-net-emac-fix-fixed-link-setup-for-the-RTL8363SB-swit.patch Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.135Koen Vandeputte2018-10-222-11/+11
| | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2018-10883 Compile-tested on: ar71xx, layerscape Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mpc85xx: workaround 4.14 cross compile issueRyan Mounce2018-10-201-0/+10
| | | | | | | | | | | Regression introduced with 4.10 by 43c9127d94d62a232ed33ed2eab8a08657ce5472 Build will fail if system 'ar' does not support deterministic builds. e.g. macOS with Xcode toolchain Appears to be fixed upstream in 4.18 by af3901cbbd3de182aafb8ee553c825c0074df6a2 Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* apm821xx: add disk-activity triggers via DT.Christian Lamparter2018-10-203-5/+2
| | | | | | | | The WNDR4700 and the MBL have a dedicated HDD activity LED. This patch adds the default led triggers to the DTS and removes the entries in 01_leds. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: apm82181.dtsi overhaulChristian Lamparter2018-10-201-135/+139
| | | | | | | | | | | | | | | | | | | - order entries by mmio address where possible - switch to lower-case address values - comment on BSP u-boot behaviour in regards to what it edits and look for - annotate irq lines with the help of interrupt-names - remove deprecated "device_type" properties The pci and network device_type had to stay since they are required by the drivers and u-boot. the cpu and memory device_types will remain as well as they are still part of the DT Spec. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: force WNDR4700 console to 115200n8Christian Lamparter2018-10-201-1/+1
| | | | | | | | | | | | | | | | | | | With the upcoming 4.19 release, the serial console on the Netgear WNDR4700 would no longer work as it is never really set and always relied on the kernel's serial code not to change the baud rate. On the stock firmware, Netgear forced the console setting through a custom CONFIG_CMDLINE in their kernel to 115200. Normally, they should have done it in a different way and just passed the baudrate through a "console=..." kernel parameter via the bootargs in the "/chosen" dt node. But in their default u-boot bootcmd setting, they somehow forgot to add the "run addtty", so there's no easy way to pass the baudrate from u-boot to the kernel. So it has to be forced as otherwise it ends up as 9600 baud. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: set uart compatible to ns16750Christian Lamparter2018-10-201-6/+11
| | | | | | | The APM821XX/PPC460EX datasheet mentions: "Register compatibility with 16750 register set" Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* gemini: Fix up image generationLinus Walleij2018-10-201-6/+10
| | | | | | | | | | | | | | | I noticed that the image generator for the Gemini generates some 10+ MB files for the second (application) partition. This is just wrong. The first 6144K partition named initramfs easily fits OpenWRTs squashfs,jffs2 overlayed partitions with nice headroom for storing configuration files. Generate a blank partition for the hddapp.tgz file and delete it after generating the firmware image - when performing updates manually you just want the "rd.z" file around anyways. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* gemini: Break out USB to packagesLinus Walleij2018-10-203-8/+6
| | | | | | | | | | | | This creates a new kernel package for the fotg210 host controller and uses that with the gemini to shrink the kernel. The SQ201 needs the USB2 PCI package as well. The build system required me to make kernel_oldconfig beofore it would build without errors so some minor unrelated Kconfig entries are changed. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* kernel: Add support for Winbond w25q128jv SPI NOR flashBaptiste Jonglez2018-10-206-9/+77
| | | | | | | | | | | | | | | | | Newer batches of several Mikrotik boards contain this yet-unsupported flash chip, for instance: - rb941-2nd (hAP lite) - rb952ui-5ac2nd (hAP ac lite) - RBM33G and probably other Mikrotik boards need this patch as well. The patch was submitted upstream by Robert Marko: https://patchwork.ozlabs.org/patch/934181/ Closes: FS#1715 Signed-off-by: Baptiste Jonglez <git@bitsofnetworks.org> Cc: Robert Marko <robimarko@gmail.com>
* kernel: bump 4.14 to 4.14.77Koen Vandeputte2018-10-1922-28/+39
| | | | | | | | | | | | | | | Refreshed all patches. Altered patches: - 666-Add-support-for-MAP-E-FMRs-mesh-mode.patch New symbol for arm targets: - HARDEN_BRANCH_PREDICTOR 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.134Koen Vandeputte2018-10-198-33/+33
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx, layerscape Runtime-tested on: ar71xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ar71xx/ath79: fix mtd corruptionFabio Bettoni2018-10-173-3/+131
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In commit fec8fe806963 ("kernel: bump 4.9 to 4.9.116") [1], the following patch for removed: - 403-mtd_fix_cfi_cmdset_0002_status_check.patch This patch contained fixes for both write and erase functions. While the chip-detects for erase got fixed upstream [2], some modifications are still required, even with the fixes applied. While at it, also apply the same fix for target ath79, which suffers the same issue. Not doing so results in following errors seen: Collected errors: * pkg_write_filelist: Failed to open //usr/lib/opkg/info/luci-lib-ip.list: I/O error. * opkg_install_pkg: Failed to extract data files for luci-lib-ip. Package debris may remain! * opkg_install_cmd: Cannot install package luci-ssl. * opkg_conf_write_status_files: Can't open status file //usr/lib/opkg/status: I/O error. [ 0.780920] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 8.406396] jffs2: notice: (415) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. [ 8.423476] mount_root: switching to jffs2 overlay [ 270.902671] jffs2: Write of 1989 bytes at 0x005ce6f8 failed. returned -5, retlen 962 [ 270.931965] jffs2: Write of 1989 bytes at 0x005ceec0 failed. returned -5, retlen 0 [ 270.939631] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero [ 270.950397] jffs2: Write of 68 bytes at 0x005ceec0 failed. returned -5, retlen 0 [ 270.957838] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero [ 270.968584] jffs2: Write of 68 bytes at 0x005ceec0 failed. returned -5, retlen 0 [ 270.976027] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero [ 270.986735] jffs2: Write of 68 bytes at 0x005ceec0 failed. returned -5, retlen 0 [ 270.994225] jffs2: Not marking the space at 0x005ceec0 as dirty because the flash driver returned retlen zero [1] https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=fec8fe806963c96a6506c2aebc3572d3a11f285f [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.9.133&id=a0239d83e1cb60de5e78452d4708c083b9e3dcbe Fixes: fec8fe806963 ("kernel: bump 4.9 to 4.9.116") Signed-off-by: Fabio Bettoni <fbettoni@gmail.com> Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 13:48:59 +0000