aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/apm821xx
Commit message (Collapse)AuthorAgeFilesLines
* kernel: Update to version 4.4.182Hauke Mehrtens2019-06-183-7/+7
| | | | | | | | | | | | | | | | | | | | | | | Fixes: - CVE-2019-11479 - CVE-2019-11478 - CVE-2019-11477 - CVE-2019-11833 - CVE-2019-11091 - CVE-2018-12126 - CVE-2018-12130 - CVE-2018-12127 - CVE-2019-3882 - CVE-2019-6974 - CVE-2019-3819 - CVE-2019-7221 - CVE-2019-7222 - CVE-2019-3701 - CVE-2018-19985 - CVE-2018-1120 And probably more Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* apm821xx: switch MX60(W)'s recovery images to multi-image methodChristian Lamparter2019-01-011-5/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In the past, the MX60(W)'s recovery images always had problems with the size restriction and never really worked without manual intervention. This patch reworks the initramfs, which allows the device to ease up on the impossible tight kernel size requirements for the initramfs image. This new initramfs can be loaded through the MX60(W) U-boot in the following way: => setenv bootargs console=ttyS0,$baudrate => tftpboot $meraki_loadaddr meraki_mx60-initramfs-kernel.bin [...] Load address: 0x800000 Loading: ################################################ [...] done [...] => bootm $fileaddr \## Booting kernel from Legacy Image at 00800000 ... ... For more information and the latest flashing guide: please visit the OpenWrt Wiki Page for the MX60(W): <https://openwrt.org/toh/meraki/mx60#flashing> Signed-off-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 36c19c9f0be23ad327085aa762e95de638e19b4a)
* apm821xx: MBL: load kernel/dtb from SATA 0:1 firstFreddy Leitner2018-12-271-3/+3
| | | | | | | | | | | | | | | | | | | | | This remedies an issue with the MBL Duo if both disks are inserted and contain OpenWrt. kernel and dtb would be loaded from SATA 1:1 while rootfs (/dev/sda2) would be mounted on SATA 0:1. Such a mix&match would obviously only work if both OpenWrt versions/ builds are identical, and especially fail after sysupgrade upgraded the system disk on SATA 0:1. The fallback to SATA 1:1 needs to be kept for MBL Single (only has SATA 1:1) and MBL Duo with one disk inserted on SATA 1:1. To speed up booting in those cases, the unneccesarily doubled "sata init" will only be called once. (In theory it could be omitted completely since the on-flash boot script already initializes SATA to load the on-disk boot script.) Tested on MBL Duo (all possible combination of disks) and MBL Single Signed-off-by: Freddy Leitner <hello@square.wf>
* kernel: bump 4.4 to 4.4.167Koen Vandeputte2018-12-182-4/+4
| | | | | | | | | | | | | | | | | | | | Refreshed all patches. Removed upstreamed: - 203-MIPS-ath79-fix-restart.patch - 330-Revert-MIPS-BCM47XX-Enable-74K-Core-ExternalSync-for.patch - 051-0001-ovl-rename-is_merge-to-is_lowest.patch - 051-0002-ovl-override-creds-with-the-ones-from-the-superblock.patch - 051-0005-ovl-proper-cleanup-of-workdir.patch Altered patches: - 201-extra_optimization.patch - 304-mips_disable_fpu.patch Compile-tested on: ar71xx, cns3xxx, imx6, mpc85xx Runtime-tested on: ar71xx, cns3xxx, imx6, mpc85xx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump kernel 4.4 to version 4.4.147Matthias Schiffer2018-08-093-5/+5
| | | | | | | | target/linux/ar71xx/patches-4.4/103-MIPS-ath79-fix-register-address-in-ath79_ddr_wb_flus.patch has been applied upstream; the two deleted brcm2708 patches have been useless even before (as the second one only reverted the first one). Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* apm821xx: fix sata access freezesChristian Lamparter2018-07-191-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original vendor's driver programmed the dma controller's AHB HPROT values to enable bufferable, privileged mode. This along with the "same priorty for both channels" fixes the freezes according to @takimata, @And.short, that have been reported on the forum by @ticerex. Furtheremore, @takimata reported that the patch also improved the performance of the HDDs considerably: |<https://forum.lede-project.org/t/wd-mybook-live-duo-two-disks/16195/55> |It seems your patch unleashed the full power of the SATA port. |Where I was previously hitting a really hard limit at around |82 MB/s for reading and 27 MB/s for writing, I am now getting this: | |root@OpenWrt:/mnt# time dd if=/dev/zero of=tempfile bs=1M count=1024 |1024+0 records in |1024+0 records out |real 0m 13.65s |user 0m 0.01s |sys 0m 11.89s | |root@OpenWrt:/mnt# time dd if=tempfile of=/dev/null bs=1M count=1024 |1024+0 records in |1024+0 records out |real 0m 8.41s |user 0m 0.01s |sys 0m 4.70s | |This means: 121 MB/s reading and 75 MB/s writing! | |[...] | |The drive is a WD Green WD10EARX taken from an older MBL Single. |I repeated the test a few times with even larger files to rule out |any caching, I'm still seeing the same great performance. OpenWrt is |now completely on par with the original MBL firmware's performance. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: bump kernel 4.4 to version 4.4.139Hauke Mehrtens2018-07-031-1/+1
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump kernel 4.4 to version 4.4.137Hauke Mehrtens2018-06-151-0/+1
| | | | | | | | | | | | The new option CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE was added, in this commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.4.y&id=ffe4bf3eb3cfa10f9ef295c08c21f4fe3bb07e21 Handle it by setting it to the opposite value CONFIG_CC_OPTIMIZE_FOR_SIZE is set to. Tested on lantiq Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump kernel 4.4 to 4.4.135 for 17.01Hauke Mehrtens2018-06-023-6/+6
| | | | | | * Refreshed patches Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* apm821xx: Add default packages to NAND targetChris Blake2018-05-273-8/+9
| | | | | | | | | | This moves core router packages to the NAND target, to ensure they are applied to all images. This change is being done due to an issue found when flashing the MX60W image, which came without these when built as a multi image. Signed-off-by: Chris Blake <chrisrblake93@gmail.com> (cherry picked from commit d1c3a9485a90fff9bf7083faba4138e14dcdae7d)
* kernel: bump kernel 4.4 to 4.4.132 for 17.01Etienne Haarsma2018-05-221-1/+1
| | | | | | | | | * Refreshed patches Compile-tested: ar71xx Run-tested: ar71xx Signed-off-by: Etienne Haarsma <bladeoner112@gmail.com>
* kernel: bump kernel 4.4 to 4.4.129 for 17.01Etienne Haarsma2018-04-302-6/+6
| | | | | | | | | * Refreshed patches Compile-tested: ar71xx Run-tested: ar71xx Signed-off-by: Etienne Haarsma <bladeoner112@gmail.com>
* kernel: bump kernel 4.4 to 4.4.126 for 17.01Stijn Segers2018-04-141-1/+1
| | | | | | | | | * Refreshed patches Compile-tested: ar71xx, ramips/mt7621, x86/64 Run-tested: ar71xx Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* kernel: update 17.01 kernel to 4.4.116Stijn Segers2018-02-201-1/+1
| | | | | | | | | | | | | | | | | | This bumps the 4.4. kernel in LEDE 17.01 to 4.4.116. More Meltdown & Spectre mitigation. * Refresh patches. * Refresh x86/config for RETPOLINE. * Deleted 8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch (accepted upstream) * Deleted 8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch (accepted upstream) * 650-pppoe_header_pad.patch does not apply anymore (code was replaced). Bumps from 4.4.113 to 4.4.115 were handled by Kevin Darbyshire-Bryant. Compile-tested on: ar71xx, ramips/mt7621, x86/64 Run-tested on: ar71xx, ramips/mt7621, x86/64 Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* kernel: update kernel 4.4 to version 4.4.110Hauke Mehrtens2018-01-072-5/+5
| | | | | | This fixes: CVE-2017-5754 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: update 4.4 to 4.4.86Kevin Darbyshire-Bryant2017-09-041-1/+1
| | | | | | Refresh patches Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: update kernel 4.4 to 4.4.74Stijn Tintel2017-06-271-3/+3
| | | | | | | | Refresh patches. Compile-tested on ar71xx, octeon. Runtime-tested on ar71xx, octeon. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: update kernel 4.4 to 4.4.70Hauke Mehrtens2017-05-272-4/+4
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: update 4.4 kernel to 4.4.42Hauke Mehrtens2017-01-133-6/+6
| | | | | | | Refresh patches on all 4.4 supported platforms. Compile & run tested: lantiq/xrx200 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* image: when using the new image build code, gzip ext4 images by defaultFelix Fietkau2017-01-131-1/+0
| | | | | | | | | This reduces the amount of hacks in the makefile code. Remove the apm821xx code to do the same - it was broken and left both compressed and uncompressed images in $(BIN_DIR) Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: remove ubifs xz decompression supportFelix Fietkau2017-01-091-2/+0
| | | | | | | It has been unused, and less useful than squashfs for cases where flash space usage matters. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: bump to 4.4.35Kevin Darbyshire-Bryant2016-11-291-3/+3
| | | | | | | | | | | Refresh patches on all 4.4 supported platforms. 077-0005-bgmac-stop-clearing-DMA-receive-control-register-rig.patch removed as now upstream. Compile & run tested: ar71xx - Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
* apm821xx: make it possible to update the dtb partition on the WNDR4700Christian Lamparter2016-11-242-6/+6
| | | | | | | | | | | | | | | | | | | | Currently, the device-tree partition is marked as read-only. Hence, userspace tools like mtd can't write into the partition. This however will be necessary in case the DTB needs to be updated. This patch also adds the kernel.dtb image, so the compiled DTB is exported as a file and available in the binary directory along the firmware images. Note: the u-boot does expects the dtb to be a uimage. To update the dtb manually: 1. copy the generated dtb to the router. 2. mtd erase /dev/mtd2 3. mtd write wndr4700.dtb /dev/mtd2 Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: Add support for the Cisco Meraki MX60/MX60WChris Blake2016-11-2111-16/+283
| | | | | | | | | | | | | | | | | | | This patch adds support for the Cisco Meraki MX60/MX60W Security Appliance. Flashing information can be found at https://github.com/riptidewave93/LEDE-MX60 Specs are as follows: AppliedMicro APM82181 SoC at 800MHz 1GiB NAND - Samsung K9K8G08U0D 512MB DDR RAM - 4x Nanya NT5TU128M8GE-AC Atheros AR8327-BL1A Gigabit Ethernet Switch 1x USB 2.0 Port More info can be found at https://wiki.openwrt.org/toh/meraki/mx60 Cc: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* kernel: update kernel 4.4 to version 4.4.32Stijn Tintel2016-11-163-5/+9
| | | | | | | | Refresh patches for all targets that support kernel 4.4. Compile-tested on all targets that use kernel 4.4 and aren't marked broken. Runtime-tested on ar71xx, octeon. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* apm821xx: remove replaced netgear, wndr4700-usb dwc2 definitonChristian Lamparter2016-11-121-48/+0
| | | | | | | This special dwc2 device definition for the Netgear WNDR4700 has been replaced by amcc,usb-otg-405ex. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: consolidate apm821xx device trees filesChristian Lamparter2016-11-126-1472/+990
| | | | | | | | | | | | | This patch moves the common SoC device tree entries from the currently four supported platforms into a common apm82181.dtsi. Furthermore, this patch also changes the GPIO, IRQ and input definitions of the supported platforms to use the defined dt-bindings macros for GPIO_ACTIVE_LOW|HIGH, KEY_WPS|RESTART|*, IRQ_TYPE_* when it's appropriate. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add amcc, usb-otg-405ex devicetree definitionChristian Lamparter2016-11-121-0/+44
| | | | | | | | | | | This patch adds support for the amcc,usb-otg-405ex device which is found in all APM82181 SoCs. Note: The system can't use the generic "snps,dwc2" compatible because of the special ahbcfg configuration. The default GAHBCFG_HBSTLEN_INCR4 of snps,dwc2 can cause a system hang when the USB and SATA is used concurrently. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: redo WAN green and yellow LEDsChristian Lamparter2016-11-082-1/+4
| | | | | | | | | Because the WAN port is handled by the internal AR8327N switch, the device should use swconfig_leds trigger to handle the link activity of the WAN LED. This has the added bonus that the WAN LED will now go dark if there's no ethernet cable connected to the WAN port. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add back end-of-UBI marker for the WNDR4700 and MR24Christian Lamparter2016-11-041-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch "build: drop UBI EOF marker from images by default" (commit d27bce8d28eb129af0abd9c80a7756301b7d588a) removed the end-of-UBI marker. Without this marker, the boards will panic during boot: [ 1.683458] ubi0: attaching mtd4 [ 1.696181] ubi0 warning: scan_peb: valid VID header but corrupted EC header at PEB 31 [ 1.704367] ubi0 error: scan_peb: bad image sequence number 549886691 in PEB 32, expected 184585623 [ 1.713377] Erase counter header dump: [ 1.717110] magic 0x55424923 [ 1.720843] version 1 [ 1.723797] ec 0 [ 1.726752] vid_hdr_offset 512 [ 1.729880] data_offset 2048 [ 1.733094] image_seq 549886691 [ 1.736740] hdr_crc 0x92ba8130 [ 1.740472] erase counter header hexdump: [ 1.744493] ubi0 error: ubi_attach_mtd_dev: failed to attach mtd4, error -22 [ 1.751528] UBI error: cannot attach mtd4 [ 1.755373] hctosys: unable to open rtc device (rtc0) [ 1.761130] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 1.768604] Please append a correct "root=" boot option; here are the available partitions: [...] [ 1.856992] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 1.866519] Rebooting in 1 seconds..Auto calibration --- Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: fix USB LED trigger for WNDR4700Rafał Miłecki2016-10-281-2/+1
| | | | | | | | | The old usbdev trigger never supported assigning more than 1 USB port. This code we got was never working as expected and it was missing 2 more ports. Switch to usbport to have LED working with all ports. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Tested-by: Christian Lamparter <chunkeey@gmail.com>
* switch to the new usbport LED triggerRafał Miłecki2016-10-193-4/+4
| | | | | | | This makes init.d script handle existing UCI entries using the new trigger. It also switches all targets to use its package. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* apm821xx: replace recovery image for the MBL with initramfsChristian Lamparter2016-10-134-118/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The patch "images: bump default rootfs size to 256 MB" a1f83bad606411a561e8e60110c71232b1a28aa2 caused a crash during boot for the recovery images. This is because both variants of the MyBook Live only have 256MB of RAM and for the recovery option, the ext4 rootfs was simply stored in the RAMDISK. This patch replaces recovery image for the MBL with an initramfs kernel. In order to boot the initramfs (for recovery or development): 0. copy the initramfs and device tree into tftp's server directory # cp *-initramfs-kernel.bin to /tftp-server/mbl.bin # cp *-ext4-kernel.dtb to /tftp-server/fdt.bin 1. Connect the MyBook Live (Duo) serial port. (Warning! Use a 3.3v level shifter). 2. Hit Enter during u-boot and insert these three lines: # setenv serverip 192.168.1.254; setenv ipaddr 192.168.1.1; # tftp ${kernel_addr_r} mbl.bin; tftp ${fdt_addr_r} fdt.bin # run addtty addmisc; bootm ${kernel_addr_r} - ${fdt_addr_r} Where 192.168.1.254 is your TFTP server. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: update kernel 4.4 to version 4.4.20Álvaro Fernández Rojas2016-09-151-29/+10
| | | | | | | Refresh patches for all targets that support kernel 4.4. Compile-tested on brcm2708 only. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* image: specify max image size in Kilobyte/MegabyteMathias Kresin2016-09-041-2/+2
| | | | | | Use the k and m unit suffix to be consistent with the blocksize. Signed-off-by: Mathias Kresin <dev@kresin.me>
* image: use k as unit suffix for blocksizeMathias Kresin2016-09-041-2/+2
| | | | | | | Use k as unit suffix for kilobyte to have a the same unit regardless of the used filesystem. Signed-off-by: Mathias Kresin <dev@kresin.me>
* apm821xx: image: add support for k unit suffix to boot-imgMathias Kresin2016-09-081-1/+1
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* apm821xx: backport generic HDD led-triggers for WNDR4700 and MBLChristian Lamparter2016-09-084-0/+232
| | | | | | | This patch backports the new generic HDD/SDD led-trigger from 4.8-rc1. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: detect sd-card media changes for the WNDR4700Christian Lamparter2016-09-082-1/+20
| | | | | | | | | The insertion or removal of the sd-card cannot be detected by the hardware itself. This is by design. To workaround this, for the WNDR4700 unload/load the dwc2 module in case the the special SD CARD GPIO line is low/high. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: add size check for initramfs kernel for the Meraki MR24Christian Lamparter2016-09-051-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | Russell Senior reported an issue with the MR24 initramfs kernels: > ## Booting kernel from Legacy Image at 00c10000 ... > Image Name: POWERPC LEDE Linux-4.4.19 > Created: 2016-08-31 11:57:05 UTC > Image Type: PowerPC Linux Kernel Image (gzip compressed) > Data Size: 2155723 Bytes = 2.1 MiB > Load Address: 00000000 > Entry Point: 00000000 > Verifying Checksum ... OK >Wrong Ramdisk Image Format >Ramdisk image is corrupt or invalid For the MR24, the kernel is uploaded to 0x10000. The ramdisk starts at 0x200000. This leaves the kernel with just 0x1f0000 bytes = 1984kb. This patch adds a size check so the image creation script will abort instead of producing a unbootable initramfs image. A separate patch "apm821xx: Fix initramfs image for the Meraki MR24" which fixed the reported issue was submitted earlier. Cc: Russell Senior <russell@personaltelco.net> Cc: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: Fix initramfs image for the Meraki MR24riptidewave932016-09-051-1/+1
| | | | | | | When gzip is used, our kernel is too large and this causes the ramdisk to be at the wrong offset. Fix by moving to lzma. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* build: fix subtarget descriptionsFelix Fietkau2016-09-041-4/+4
| | | | | | Move Target/Description above the target.mk include Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: update kernel 4.4 to version 4.4.19Stijn Tintel2016-08-2321-393/+191
| | | | | | | | Refresh patches for all targets that support kernel 4.4. Compile-tested on all targets that use kernel 4.4 and aren't marked broken. Runtime-tested on ar71xx, octeon and x86/64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* apm821xx: fix IB image buildingJo-Philipp Wich2016-08-011-6/+10
| | | | | | | Change the image build code to generate the DTB files as part of the kernel build phase in order to fix the image build in the ImageBuilder environment. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* image: add a helper variable for getting kernel/rootfs from within image ↵Felix Fietkau2016-07-311-4/+4
| | | | | | Build/* templates Signed-off-by: Felix Fietkau <nbd@nbd.name>
* build: rename sysupgrade-nand to sysupgrade-tarJo-Philipp Wich2016-07-291-2/+2
| | | | | | | Now that the "sysupgrade-nand" step is used by non-NAND targets as well, rename it to "sysupgrade-tar" to make it more generic. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* apm821xx: only attempt to mount /boot on MyBook LiveFelix Fietkau2016-07-291-0/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* apm821xx: fix atheros PCIe cards on the MR24Christian Lamparter2016-07-251-9/+12
| | | | | | | | | | | | | | | The consolidation of the MR24 and WNDR4700 subtargets into the nand subtarget broke MR24's atheros wlan. This was because the wndr4700's board code used a pci_fixup routines to supply the ath9k module with the calibration data. This is not necessary on the MR24 as it has standard mini-pcie ports. Hence the two AR9380 mini-pcie cards do not need any calibration data overrides. Cc: chrisrblake93@gmail.com Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: use lzma compression for the initramfs imagesChristian Lamparter2016-07-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | The MR24's u-boot takes it sweet time decompressing the LZMA-packed initramfs image. A user reported that compared to the old gzip method in v2: it "takes a ton longer to decompress like 4\x the old boot time for decompression". This patch also fixes a issue with the WNDR4700's initramfs image getting to big and causing the following u-boot crash during the decompression: "Uncompressing Multi-File Image ... Error: inflate() returned -5 out-of-mem or overwrite error - must RESET board to recover" This patch fixes both issues by reverting the MR24's initramfs compression method back to gzip. And choosing to compress the initramfs within the initramfs image as LZMA by default. Cc: chrisrblake93@gmail.com Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* tools: bring back genext2fs for apm821xxFelix Fietkau2016-07-231-4/+0
| | | | | | | | This reverts commit 8c68c104eaba65273280c7a4727fbb10ab10f5af. It is used for apm821xx, which needs ext2 (not ext4) images for some devices. Signed-off-by: Felix Fietkau <nbd@nbd.name>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 17:49:15 +0000