aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 4.19 to 4.19.56Koen Vandeputte2019-06-254-6/+6
| | | | | | | | | 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.130Koen Vandeputte2019-06-257-10/+10
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* x86: fix missing led variable warning during bootPetr Štetiar2019-06-251-0/+2
| | | | | | | | Fixes following warning during the boot: WARNING: Variable 'led' does not exist or is not an array/object Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: generic: add missing 4.19 config symbolPetr Štetiar2019-06-251-0/+1
| | | | | | | | Fixes following kernel build issue on x86/64: PCI PF Stub driver (PCI_PF_STUB) [N/m/y/?] (NEW) Signed-off-by: Petr Štetiar <ynezz@true.cz>
* malta: fix overlay support by updating to f2fs/ext4 based overlaysPetr Štetiar2019-06-252-7/+10
| | | | | | | | | | | | | | | | | Current snapshot images doesn't provide images with usable overlay filesystems: mount_root: no usable overlay filesystem found, using tmpfs overlay So this patch fixes this by updating support to current f2fs/ext4 based overlays and providing squashfs with proper rootfs TARGET_ROOTFS_PARTSIZE size. While at it, I've also added support for optional gzipping of the images, and renamed the output rootfs image filenames to match the more common naming pattern $(IMG_PREFIX)-rootfs-$(FS-TYPE).img. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* malta: configure kernel for f2fs and ext4 based overlaysPetr Štetiar2019-06-251-0/+7
| | | | | | | | jffs2/mtdblock overlays are long time gone, and as we switch to the new f2fs/ext4 based overlays, we need to add missing support for loop block device and f2fs to kernel. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: fix overlay support by updating to f2fs/ext4 based overlaysPetr Štetiar2019-06-252-2/+10
| | | | | | | | | | | | | | | | | | Current snapshot images doesn't provide images with usable overlay filesystems: mount_root: no usable overlay filesystem found, using tmpfs overlay So this patch fixes this by updating support to current f2fs/ext4 based overlays and providing squashfs with proper rootfs TARGET_ROOTFS_PARTSIZE size. While at it, I've also added support for optional gzipping of the images, and renamed the output rootfs image filenames to match the more common naming pattern $(IMG_PREFIX)-rootfs-$(FS-TYPE).img. Cc: Yousong Zhou <yszhou4tech@gmail.com> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* armvirt: configure kernel for f2fs and ext4 based overlaysPetr Štetiar2019-06-251-0/+7
| | | | | | | | jffs2/mtdblock overlays are long time gone, and as we switch to the new f2fs/ext4 based overlays, we need to add missing support for loop block device and f2fs to kernel. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: image: fix small disk space in squashfs overlayPetr Štetiar2019-06-251-12/+1
| | | | | | | | | | | | | Current squashfs snapshot images are improperly padded by just 128k, which doesn't correspond with TARGET_ROOTFS_PARTSIZE=128 default config option, leading to following: Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 85.0K 9.0K 71.0K 11% /overlay overlayfs:/overlay 85.0K 9.0K 71.0K 11% / Signed-off-by: Petr Štetiar <ynezz@true.cz>
* rb532,x86: image: use new IMG_COMBINED and IMG_ROOTFS varsPetr Štetiar2019-06-252-13/+13
| | | | | | | In `build: image: Add IMG_ROOTFS and IMG_COMBINED variables` we've added this new variables so switch to them now. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* tegra: image: remove image paddingPetr Štetiar2019-06-251-1/+0
| | | | | | | Commit "build: Remove TARGET_IMAGES_PAD option" has removed this config option so remove it from this target as well. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* x86: image: remove TARGET_IMAGES_PAD option and force paddingPetr Štetiar2019-06-251-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Currently we're producing unusable x86 combined squashfs images (18.06.1, 18.06.2 and snapshots) as we don't enable TARGET_IMAGES_PAD, thus providing very small space for the overlay filesystem, leading to the following with OpenWrt 18.06.1 r7258-5eb055306f images on x86 QEMU: root@(none):/# mount | egrep 'root|overlay' /dev/root on /rom type squashfs /dev/loop0 on /overlay type ext4 overlayfs:/overlay on / type overlay root@(none):/# df -h | egrep 'root|overlay|Size' Filesystem Size Used Available Use% Mounted on /dev/root 2.5M 2.5M 0 100% /rom /dev/loop0 113.0K 8.0K 97.0K 8% /overlay overlayfs:/overlay 113.0K 8.0K 97.0K 8% / We should rather ensure proper image padding in image generation code and we shouldn't rely on config options in order to generate usable images. So this patch removes TARGET_IMAGES_PAD config option and enforces padding on combined images. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: mt7621: Add new device AsiaRF AP7621-001Daniel Danzberger2019-06-253-0/+141
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware specs: SoC: Mediatek MT7621A CPU: 4x 880Mhz Cache: 32 KB I-Cache and 32 KB D-Cach 256 KB L2 Cache (shared by Dual-Core) RAM: DDR3 512MB 16bits BUS FLASH: 16MB Switch: Mediatek Gigabit Switch (1 x LAN, 1 x WAN) USB: 1x 3.0 PCI: 3x Mini PCIe GPS: Quectel L70B BTN: Reset LED: - Power - Ethernet - Wifi - USB UART: UART is present as Pads with throughholes on the PCB. They are located on left side. 3.3V - RX - GND - TX / 57600-8N1 3.3V is the square pad Installation: The stock image is a modified openwrt and can be overflashed via # sysupgrade -F image.bin Signed-off-by: Daniel Danzberger <daniel@dd-wrt.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [removed unused label, formatting]
* ath79: fix "spi-gpio: convert deprecated binding"Christian Lamparter2019-06-254-8/+8
| | | | | | | | This patch fixes the previous commit that rendered the devices (mostly leds) useless. Fixes: 1fa24de8c29b ("ath79: spi-gpio: convert deprecated binding") Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: Code style improvements in 10_fix_wifi_macAdrian Schmutzler2019-06-251-4/+4
| | | | | | This fixes one comparison and several useless echos. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mpc85xx: Use uncompressed kernel on the HiveAP-330Chris Blake2019-06-241-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It seems that newer builds of OpenWRT have a gzip kernel larger than 2MB~, which for some reason fails to boot on this board. However, we have 8MB of kernel space and currently the uncompressed kernel is 6.5MB~, so we have some space to grow until a better solution is worked out. Before: ## Booting kernel from Legacy Image at ee840000 ... Image Name: Linux-4.19.53 Created: 2019-06-22 11:17:48 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 2315724 Bytes = 2.2 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 02000000 ... Image Name: OpenWrt fake ramdisk Created: 2019-06-22 11:17:48 UTC Image Type: PowerPC Linux RAMDisk Image (uncompressed) Data Size: 0 Bytes = 0 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at ec000000 Booting using the fdt blob at 0xec000000 Uncompressing Kernel Image ... Error: Bad gzipped data GUNZIP: uncompress, out-of-mem or overwrite error - must RESET board to recover Loading Ramdisk to 10000000, end 10000000 ... OK Loading Device Tree to 00ffa000, end 00fffc78 ... OK ft_fixup_l2cache: FDT_ERR_NOTFOUND After: ## Booting kernel from Legacy Image at ee840000 ... Image Name: POWERPC OpenWrt Linux-4.19.53 Created: 2019-06-22 11:17:48 UTC Image Type: PowerPC Linux Kernel Image (uncompressed) Data Size: 6724584 Bytes = 6.4 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 02000000 ... Image Name: OpenWrt fake ramdisk Created: 2019-06-22 11:17:48 UTC Image Type: PowerPC Linux RAMDisk Image (uncompressed) Data Size: 0 Bytes = 0 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at ec000000 Booting using the fdt blob at 0xec000000 Loading Kernel Image ... OK OK Loading Ramdisk to 10000000, end 10000000 ... OK Loading Device Tree to 00ffa000, end 00fffc78 ... OK Signed-off-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [75 cpl limit]
* apm821xx: move to 4.19 kernelsChristian Lamparter2019-06-241-2/+1
| | | | | | | | The 4.19 code has been available for some time now. Since the f2fs / loop issue has been under control I think it's time the target gets to move to it. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* apm821xx: switch out kernel's CRC32 methodChristian Lamparter2019-06-242-0/+4
| | | | | | | | | | | This patch replaces the OpenWrt' favoured CRC32 Sarwate algorithm with the kernel recommended SLICE8 CRC32 version. This change alone lifted btrfs writes from 40 MiB/s to 54 MiB/s on my My Book Live (SLICE4 managed 48 MiB/s). Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: add support for TP-Link CPE610-v1Andrew Cameron2019-06-244-0/+155
| | | | | | | | | | | | | | | | | | | | | TP-Link CPE610-v1 is an outdoor wireless CPE for 5 GHz with one Ethernet port based on Atheros AR9344 Specifications: - Based on the same underlying hardware as the TP-Link CPE510 - Power, LAN, WLAN5G green LEDs - 23dBi high-gain directional 2×2 MIMO antenna and a dedicated metal reflector Flashing instructions: Flash factory image through stock firmware WEB UI or through TFTP To get to TFTP recovery just hold reset button while powering on for around 4-5 seconds and release. Rename factory image to recovery.bin Stock TFTP server IP:192.168.0.100 Stock device TFTP adress:192.168.0.254 Signed-off-by: Andrew Cameron <apcameron@softhome.net>
* ath79: spi-gpio: convert deprecated bindingChristian Lamparter2019-06-244-8/+8
| | | | | | | The old gpio-{sck,miso and mosi} binding is deprecated in favour of {sck,miso and mosi}-gpios. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: spi-gpio: convert deprecated bindingChristian Lamparter2019-06-241-2/+2
| | | | | | | The old gpio-{sck,miso and mosi} binding is deprecated in favour of {sck,miso and mosi}-gpios. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: Remove redundant LED GPIO definitions for Archer C25 v1Adrian Schmutzler2019-06-241-4/+0
| | | | Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* netfilter: fix crash in flow offload by adding netns supportHsiuWen Yen2019-06-242-3/+13
| | | | | | | | | | | | | | | | | | | | Commit fcb41decf6c6 ("config: enable some useful features on !SMALL_FLASH devices") enabled netns, which in turn lead to the crash in the flow offload target. When the flow offloading framework intends to delete a flow from the hardware table, it is necessary to retrieve the namespace from nf_flowtable->ft_net. However, no one ever wrote the namespace into nf_flowtable->ft_net in advance. So the framework will mistakenly use a NULL namespace to execute dev_get_by_index_rcu(net, ifindex), leading to the kernel panic. Ref: FS#2321 Fixes: fcb41decf6c6 ("config: enable some useful features on !SMALL_FLASH devices") Tested-by: Simon Tretter <simon@mediaarchitectu.re> Signed-off-by: HsiuWen Yen <y.hsiuwen@gmail.com> [merged patch into offload patch, fix for 4.19, SOB fix, commit subj/msg touches] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* cns3xxx: switch to kernel 4.19Koen Vandeputte2019-06-241-2/+1
| | | | Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.19 to 4.19.55Koen Vandeputte2019-06-245-34/+7
| | | | | | | | | Refreshed all patches. Compile-tested on: imx6 Runtime-tested on: imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.129Koen Vandeputte2019-06-247-26/+8
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.9 to 4.9.183Koen Vandeputte2019-06-243-6/+6
| | | | | | | | | Refreshed all patches. Compile-tested on: none Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: add promising "fix loop discard errors" hackChristian Lamparter2019-06-221-0/+164
| | | | | | | | | | | This patch adds a promising upstream patch that claims to help for the treated I/O errors happening on f2fs or ext4 on real block devices. |print_req_error: I/O error, dev loop1, sector 1334 Link: <https://patchwork.kernel.org/cover/10931787/> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: update act_ctinfoKevin Darbyshire-Bryant2019-06-202-20/+58
| | | | | | | Follow upstream changes - header file changes no executable difference at all Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* gemini: Fix up DNS-313 compatible stringLinus Walleij2019-06-202-1/+22
| | | | | | | | | It's a simple typo in the DNS file, which was pretty serious. No scripts were working properly. Fix it up. Signed-off-by: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [integrate upstream patch into openwrt target]
* kernel: package Broadcom BNX2X driverPetko Bordjukov2019-06-204-0/+4
| | | | | | | | | | bnx2x driver support for the x86 architecture. Includes module and firmware for Broadcom QLogic 5771x/578xx 10/20-Gigabit ethernet adapters. Signed-off-by: Petko Bordjukov <bordjukov@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [added +kmod-lib-zlib-inflate as well]
* ipq40xx: Linksys: sysupgrade: Ensure OEM volumes are removedJeff Kletsky2019-06-201-20/+22
| | | | | | | | | | | | | | | | | | When OEM volumes are present in the [alt_]firmware partition, sysupgrade will write a new kernel, but will fail to write the root file system. The next boot will hang indefinitely Waiting for root device /dev/ubiblock0_0... Modified ipq40xx/base-files/lib/upgrade/linksys.sh to remove both `squashfs` and `ubifs` if found on the target firmware partition's UBI device. Run-tested-on: Linksys EA8300 Signed-off-by: Jeff Kletsky <git-commits@allycomm.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com> [applied some shellcheck suggestions as well]
* apm821xx: fix bogus key-presses on bootChristian Lamparter2019-06-206-0/+67
| | | | | | | | | | | | | | | | | | | | | | | "There are often transient line events when the system is powered up and initialized and it is often necessary for the gpio_chip driver to clear any interrupt flags in hardware before setting up the gpio chip, especially the irqchip portions of it." <http://lists.infradead.org/pipermail/openwrt-devel/2019-June/017630.html> This patch adds a fix for the APM821XX's interrupt controller to clear any bogus pending toggled interrupts that happens on various APM821XX boards on boot. The patch also changes the debouce-interval from the default 5ms debounce interval to 60ms all around. The default setting caused on occasions that the button state became stuck in a pressed state, even though the button was released. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: bump 4.19 to 4.19.53Koen Vandeputte2019-06-202-5/+5
| | | | | | | | | Refreshed all patches. Compile-tested on: imx6 Runtime-tested on: imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump 4.14 to 4.14.128Koen Vandeputte2019-06-2010-22/+22
| | | | | | | | | Refreshed all patches. Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: generic: fix MIPS build on non-linux hostsKevin Darbyshire-Bryant2019-06-201-0/+62
| | | | | | | | | | | | | | | | | | | | calc_vmlinuz_load_addr.c requires SZ_64K to be defined for alignment purposes. It included "../../../../include/linux/sizes.h" to define that size, however "sizes.h" tries to include <linux/const.h> which assumes linux system headers. These may not exist eg. the following error was encountered when building Linux for OpenWrt under macOS: In file included from arch/mips/boot/compressed/calc_vmlinuz_load_addr.c:16: arch/mips/boot/compressed/../../../../include/linux/sizes.h:11:10: fatal error: 'linux/const.h' file not found Change makefile to force building on local linux headers instead of system headers. Also change eye-watering relative reference in include file spec. Thanks to Jo-Philip Wich & Petr Štetiar for assistance in tracking this down & fixing. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* ramips: fix EW-7478AC model name in DTSPetr Štetiar2019-06-201-1/+1
| | | | | | | | This fixes lower case AC in the DTS model name. Fixes: 88f7a29f99fb ("ramips: add support for Edimax EW-7476RPC / EW-7478AC") Reported-by: Cezary Jackiewicz <cezary@eko.one.pl> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: correct various phy-mode propertiesDavid Bauer2019-06-206-4/+8
| | | | | | | | | | | | | | | | | | | | Upstream commit 6d4cd04 changes how the internal delays of the AR803x based PHYs are enabled. With this commit, all internal delays are disabled on driver probe and enabled based on the 'phy-mode' property in the device-tree. Before this commit, the RX delay was always enabled upon soft-reset while the TX delay retained it's previous state. A hard reset enabled the RX delay while the TX delay was disabled. Because of this inconsistency, wrongly specified PHY-modes were working correctly while the hardware was in a different state. Fix the PHY-modes of some affected devices (and clean up misplaced properties along the way) to keep the devices working flawlessly with kernels >= 5.1. Signed-off-by: David Bauer <mail@david-bauer.net>
* ramips: fix GELAN port in D-Link DWR-118-A2Pawel Dembicki2019-06-202-5/+7
| | | | | | | This patch fix and enable GELAN port in D-LINK DWR-118-A2. Tested-by: Richard Toth <trtk1992@gmail.com> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* ramips: mt7620: add EPHY base mdio address changing possibilityPawel Dembicki2019-06-202-46/+62
| | | | | | | | | | | In some boards is requred to change the ephy mdio base address. This patch add of property "mediatek,ephy-base-address" in gsw part, which allows to change ephy base address. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [fixed indentation in header file] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: mt7620: fix external PHY autopollingPawel Dembicki2019-06-201-4/+6
| | | | | | | | | | | | | | | | | The port initialisation is based on assumption that phy address and port number is the same. SoC allow different numbers and some board have it. Use phy address instead the port number to make sure that correct addresses are polled. In situation when only one PHY with address 0x0 is conected to port 4, autopolling is broken. This patch make autopolling correct when port number and phy address are different. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* ramips: handle mdio address and switch port seperateMathias Kresin2019-06-204-11/+14
| | | | | | | | | | | | | | | The phy handling code forces a phy mdio address and the switch port to which a phy is attached to be the same. Albeit such a configuration is used for most boards, it isn't for all. Pass the switch port number to the ethernet phy connect functions, to ensure the correct list entry is edited and not the list entry that matches th phys mdio address. Use the mdio address with mdiobus_get_phy instead of the port number, to make sure the expected ethernet phy gets connected. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: ignore already handled ethernet physMathias Kresin2019-06-201-2/+8
| | | | | | | | | | | | The whole logic in fe_phy_connect() is based on the asumption that mdio address and switch port id are equal. Albeit it is true for most boards, it doesn't is for all. It isn't yet clear which subtargets/boards require the devicetree less ethernet phy handling. Hence change the code in a way that it doesn't touch ethernet phys which were early attached and are already handled. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for Edimax EW-7478APCBirger Koblitz2019-06-203-1/+216
| | | | | | | | | | | | | | | | | | | | | | | | | | | | SoC: MediaTek MT7620a @ 580MHz RAM: 64M (Winbond W9751G6KB-25) FLASH: 8MB (Macronix) WiFi: SoC-integrated: MediaTek MT7620a bgn WiFi: MediaTek MT7612EN nac Switch: Mediatek MT7530W Gigabit Switch (4 x LAN, 1 x WAN) USB: Yes 1 x 2.0 (+ 1 x 2.0 unpopulated header) BTN: Reset/WPS LED: - Power (white) - Internet (blue) - Wifi (blue) - USB (blue) UART: UART is present as Pads with throughholes on the PCB. They are located in the lower right corner (GbE ports facing up) 3.3V - RX - GND - TX / 57600-8N1 3.3V is the square pad Installation ------------ Update the factory image via the web-interfaces (by default: http://edimax.setup) Signed-off-by: Birger Koblitz <mail@birger-koblitz.de> [merge conflicts in 01_leds and mt7620.mk, dts whitespace issues] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: add support for Edimax EW-7476RPC / EW-7478ACBirger Koblitz2019-06-207-0/+349
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SoC: MediaTek MT7620a @ 580MHz RAM: 64M (Winbond W9751G6KB-25) FLASH: 8MB (Macronix) WiFi: SoC-integrated: MediaTek MT7620a bgn WiFi: MediaTek MT7612EN nac GbE: 1x (RTL8211E) BTN: WPS - RFKILL/RF 50%/RF 100% toggle LED: - Wifi 5g (blue) - Wifi 2g (blue) - Crossband (green) - Power (green) - WPS (green) - LAN (Green) UART: UART is present as Pads with throughholes on the PCB. They are located next to the switch for the wifi configuration 3.3V - RX - GND - TX / 57600-8N1 3.3V is the square pad Installation ------------ Update the factory image via the web-interfaces (by default: 192.168.9.2/24). http://192.168.9.2/index.asp ramips: add Edimax EW-7478AC SoC: MediaTek MT7620a @ 580MHz RAM: 64M (Winbond W9751G6KB-25) FLASH: 8MB (Macronix) WiFi: SoC-integrated: MediaTek MT7620a bgn WiFi: MediaTek MT7612EN nac GbE: 1x (RTL8211E) BTN: WPS - RFKILL/RF 50%/RF 100% toggle LED: - Wifi 5g (blue) - Wifi 2g (blue) - Crossband (green) - Power (green) - WPS (green) - LAN (Green) UART: UART is present as Pads with throughholes on the PCB. They are located next to the switch for the wifi configuration 3.3V - RX - GND - TX / 57600-8N1 3.3V is the square pad Installation ------------ Update the factory image via the web-interfaces (by default: http://edimaxext.setup) Or push wpa button on power on and send firmware via tftp to 192.168.1.6 The EW-7478AC is identical to the EW-7476RPC, except instead of 2 internal antennas it has 2 external ones. Signed-off-by: Birger Koblitz <mail@birger-koblitz.de> [merge conflict in 01_leds] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* mvebu: fix regression for non-generic ESPRESSObin versionsVladimir Vid2019-06-182-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>
* mvebu: image: fix generic-arm64.bootscript mmc selectionVladimir Vid2019-06-181-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>
* treewide: kernel: bump some targets to 4.19Petr Štetiar2019-06-1812-24/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Lets bump kernel to 4.19 on targets which were run tested or got ACKed so we've enough time to make it ready for next release: armvirt/32 (runtested in qemu) armvirt/64 (runtested in qemu) ath79/generic (runtested on Carambola2) gemini/generic (runtested on DIR-685, DNS-313, SQ201, SL93512R) imx6/generic (runtested on Apalis) ipq40xx/generic (runtested on nbg6617) malta/be64 (runtested in qemu) malta/be (runtested in qemu) malta/le (runtested in qemu) malta/le64 (runtested in qemu) mpc85xx/generic (runtested on TL-WDR4900) mpc85xx/p2020 (runtested on P2020RDB) mvebu/cortexa53 mvebu/cortexa72 mvebu/cortexa10 octeon/generic (runtested on EdgeRouter Lite) sunxi/cortexa53 (build tested only) sunxi/cortexa7 (runtested on Lime2-K) sunxi/cortexa8 (build tested only) tegra/generic x86/64 (runtested in qemu) Acked-by: Zoltan HERPAI <wigyori@uid0.hu> [sunxi] Tested-by: Linus Walleij <linus.walleij@linaro.org> [gemini] Tested-by: Tomasz Maciej Nowak <tomek_n@o2.pl> [mvebu, tegra] Tested-by: Daniel Engberg <daniel.engberg.lists@pyret.net> [octeon] Tested-by: Pawel Dembicki <paweldembicki@gmail.com> [mpc85xx/generic mpc85xx/p2020] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: generic: add missing DRM panel 4.19 config symbolsPetr Štetiar2019-06-181-0/+6
| | | | | | | While building tegra/generic on 4.19, I've discovered few missing symbols related to DRM panel symbols. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: generic: add missing 4.19 config symbolPetr Štetiar2019-06-181-0/+1
| | | | | | | | Fixes following kernel build issue on ath79/generic: Enable support for latency based cgroup IO protection (BLK_CGROUP_IOLATENCY) [N/y/?] (NEW) Signed-off-by: Petr Štetiar <ynezz@true.cz>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-19 02:34:48 +0000