aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ath79: airtight c-75: use second flash chipTomasz Maciej Nowak2020-12-192-6/+23
| | | | | | | | | | | The flash capacity is divided in two flash chips and currently only first is used. Increase available space for OpenWrt by additional 16 MiB using mtd-concat driver. Because U-Boot might not be able to load kernel image spanned through two flash chips, the size of kernel is limited to space available on first first chip. Cc: Vladimir Georgievsky <vladimir.georgievsky@yahoo.com> Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* ath79: add support for AirTight C-75Tomasz Maciej Nowak2020-12-193-0/+186
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | AirTight Networks (later renamed to Mojo Networks) C-75 is a dual-band access point, also sold by WatchGuard under name AP320. Specification SoC: Qualcomm Atheros QCA9550 RAM: 128 MiB DDR2 Flash: 2x 16 MiB SPI NOR WIFI: 2.4 GHz 3T3R integrated 5 GHz 3T3R QCA9890 oversized Mini PCIe card Ethernet: 2x 10/100/1000 Mbps QCA8334 port labeled LAN1 is PoE capable (802.3at) USB: 1x 2.0 LEDs: 7x which two are GPIO controlled, four switch controlled, one controlled by wireless driver Buttons: 1x GPIO controlled Serial: RJ-45 port, Cisco pinout baud: 115200, parity: none, flow control: none JTAG: Yes, pins marked J1 on PCB Installation 1. Prepare TFTP server with OpenWrt initramfs-kernel image. 2. Connect to one of LAN ports. 3. Connect to serial port. 4. Power on the device and when prompted to stop autoboot, hit any key. 5. Adjust "ipaddr" and "serverip" addresses in U-Boot environment, use 'setenv' to do that, then run following commands: tftpboot 0x81000000 <openwrt_initramfs-kernel_image_name> bootm 0x81000000 6. Wait about 1 minute for OpenWrt to boot. 7. Transfer OpenWrt sysupgrade image to /tmp directory and flash it with: sysupgrade -n /tmp/<openwrt_sysupgrade_image_name> 8. After flashing, the access point will reboot to OpenWrt. Wait few minutes, until the Power LED stops blinking, then it's ready for configuration. Known issues Green power LED does not work. Additional information The U-Boot fails to initialise ethernet ports correctly when a UART adapter is attached to UART pins (marked J3 on PCB). Cc: Vladimir Georgievsky <vladimir.georgievsky@yahoo.com> Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* bcm53xx: use correct case for TP-Link in DEVICE_VENDORMoritz Warning2020-12-191-2/+2
| | | | | | | | Adjust spelling of vendor names to what is used in other places. Signed-off-by: Moritz Warning <moritzwarning@web.de> [improve commit title/message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: use upper case for NETGEAR in DEVICE_VENDORMoritz Warning2020-12-191-2/+1
| | | | | | | | | | Adjust spelling of vendor name to what is used in other places. Also move definition in shared section. Signed-off-by: Moritz Warning <moritzwarning@web.de> [improve commit title/message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: xrx200: remove redundant stp parametersAleksander Jan Bajkowski2020-12-193-10/+0
| | | | | | | These parameters are the same as in vr9.dtsi. This patch removes redundant parameters. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* kernel: improve skb hash on the mtk ethernet driverFelix Fietkau2020-12-185-25/+35
| | | | | | | | The PPE only provides a 14 bit hash, however many uses of the skb hash expect the hash to use the full 32 bit range. Use jhash to extend the hash to the full size Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: do not enable unused GPIO controllersAdrian Schmutzler2020-12-1727-132/+0
| | | | | | | | Several devices enable GPIO controllers not used in the DTS files. Drop them. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: qca955x: remove redundant phy-modeAdrian Schmutzler2020-12-175-7/+0
| | | | | | | phy-mode is already set to rgmii for eth0 and sgmii for eth1 in qca955x.dtsi, no need to do that again in the device DTS files. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add support for GL.iNet GL-MT1300Xinfa Deng2020-12-174-0/+165
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The GL-MT1300 is a high-performance new generation pocket-sized router that offers a powerful hardware and first-class cybersecurity protocol with unique and modern design. Specifications: - SoC: MT7621A, Dual-Core @880MHz - RAM: 256 MB DDR3 - Flash: 32 MB - Ethernet: 3 x 10/100/1000: 2 x LAN + 1 x WAN - Wireless: 1 x MT7615D Dual-Band 2.4GHz(400Mbps) + 5GHz(867Mbps) - USB: 1 x USB 3.0 port - Slot: 1 x MicroSD card slot - Button: 1 x Reset button - Switch: 1 x Mode switch - LED: 1 x Blue LED + 1 x White LED MAC addresses based on vendor firmware: WAN : factory 0x4000 LAN : Mac from factory 0x4000 + 1 2.4GHz : factory 0x4 5GHz : Mac form factory 0x4 + 1 Flashing instructions: 1.Connect to one of LAN ports. 2.Set the static IP on the PC to 192.168.1.2. 3.Press the Reset button and power the device (do not release the button). After waiting for the blue led to flash 5 times, the white led will come on and release the button. 4.Browse the 192.168.1.1 web page and update firmware according to web tips. 5.The blue led will flash when the firmware is being upgraded. 6.The blue led stops blinking to indicate that the firmware upgrade is complete and U-Boot automatically starts the firmware. For more information on GL-MT1300, see the OFFICIAL GL.iNet website: https://www.gl-inet.com/products/gl-mt1300/ Signed-off-by: Xinfa Deng <xinfa.deng@gl-inet.com> [add input-type for switch, wrap long line in 10_fix_wifi_mac] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: falcon: mark as source only sub targetHauke Mehrtens2020-12-161-1/+1
| | | | | | | | | | The sub target does not support network and there are not so many users out there, just mark it as source only, so we do jot have to build it. The quality is not worse than before, it just does not make much sense to build this automatically. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 5.4 to 5.4.83John Audia2020-12-1518-47/+44
| | | | | | | | | | | | | | | | | | | Manually merged: layerscape/808-i2c-0011-i2c-imx-support-slave-mode-for-imx-I2C-driver.patch layerscape/808-i2c-0012-i2c-imx-correct-code-of-errata-A-010650-for-layersca.patch Remaining modifications made by update_kernel.sh Build system: x86_64 Build-tested: ipq806x/R7800, ath79/generic, bcm27xx/bcm2711, x86/64 [*], ramips/mt7621 [*], ath79/tiny [*], ipq40xx [*], octeon [*], realtek [*] Run-tested: ipq806x/R7800, ramips/mt7621 [*], octeon [*], realtek [*] No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us> Tested-by: Stijn Segers <foss@volatilesystems.org> [*]
* armvirt: README: rename it from LEDE to OpenWrtJosef Schlehofer2020-12-141-1/+1
| | | | Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* armvirt/64: change it to cortex-a53 instead of genericJosef Schlehofer2020-12-141-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Package architecture aarch64_generic [1] can be used just with three devices. One is NanoPI R2S and then there are two development boards from NXP. Let's change armvirt/64 to Cortex A53 (aarch64_cortex-a53) [2]. It has wider support by multiple devices like NanoPI Neo Plus2/Core2, ESPRESSObin, Pine64, and Raspberry Pi 2&3. While looking at ARMvirt/32 it has set CPU_TYPE and CPU_SUBTYPE to be arm_cortex-a15_neon-vfpv4 [3]. It has support to devices like Linksys EA8500 v1, Linksys EA7500 v1, Netgear D7800, Netgear R7500 and so on. Tested with: qemu-system-aarch64 -m 1024 -smp 2 -cpu cortex-a57 -M virt -nographic \ -kernel openwrt-armvirt-64-Image-initramfs Successfully compiled and booted. Here goes the output: root@OpenWrt:/# uname -a Linux OpenWrt 5.4.82 #0 SMP Sun Dec 13 12:52:10 2020 aarch64 GNU/Linux root@OpenWrt:/# cat /etc/openwrt_release DISTRIB_ID='OpenWrt' DISTRIB_RELEASE='SNAPSHOT' DISTRIB_REVISION='r15207-96fca0f807' DISTRIB_TARGET='armvirt/64' DISTRIB_ARCH='aarch64_cortex-a53' DISTRIB_DESCRIPTION='OpenWrt SNAPSHOT r15207-96fca0f807' DISTRIB_TAINTS='no-all' Also, change BOARDNAME to be the same as it is in armvirt/32. [1] https://openwrt.org/docs/techref/instructionset/aarch64_generic [2] https://openwrt.org/docs/techref/instructionset/aarch64_cortex-a53 [3] https://openwrt.org/docs/techref/instructionset/arm_cortex-a15_neon-vfpv4 Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* lantiq: xrx200: remove unused lan/wan labels from dtsAleksander Jan Bajkowski2020-12-1412-13/+13
| | | | | | These labels are not used anywhere and can be removed. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* ath79: add support for the Belkin F9K1115 v2 (AC1750 DB Wi-Fi)Martin Blumenstingl2020-12-143-0/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This device has (almost?) identical hardware to the F9J1108 v2 but uses a different firmware magic and model number. Specifications: SoC: QCA9558 CPU: 720 MHz Flash: 16 MiB NOR RAM: 128 MiB WiFi 2.4 GHz: QCA9558-AT4A 3x3 MIMO 802.11b/g/n WiFi 5 GHz: QCA9880-2R4E 3x3 MIMO 802.11a/n/ac Ethernet: 4x LAN and 1x WAN (all 1Gbit/s ports) USB: 1 x USB 2.0 (lower), 1 x USB 3.0 (upper) MAC addresses based on OEM firmware: Interface Address Location --------- ------- -------- lan *:5A sometimes in 0x6 wan *:5B 0x0 2.4Ghz *:5A 0x1002 5Ghz As per mini PCIe EEPROM Flashing instructions: The factory.bin can be flashed via the Belkin web UI or via the uboot HTTP upgrade page (which is by default listening on 192.168.2.1). Once the factory.bin has been written, sysupgrade.bin will work as usual. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* ath79: create shared DTSI/definition for Belkin F9J1108/F9K1115 v2Martin Blumenstingl2020-12-143-225/+238
| | | | | | | | | | | | | | | Belkin F9J1108 v2 and F9K1115 v2 are (seemingly) identical hardware with different model numbers. Extract all non-device specific code to a common .dtsi so it can be re-used when adding support for the F9K1115 v2. Similar to the .dtsi most of the image building recipe code can be re-used. Move everything except the device model, edimax header magic and edimax header model into a shared build recipe. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> [drop duplicate TARGET_DEVICES, add EDIMAX_* to DEVICE_VARS, edit title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: revert usage of VLAN S-TAGDavid Bauer2020-12-142-37/+9
| | | | | | | | | | | This reverts the usage of the S-Tag for separating LAN and WAN port on the embedded switch. Many users complained about not being able to manage C-Tag addition / removal on the switch as well as degraded performance. Fixes: commit 9da2b567605b ("ipq40xx: fix ethernet vlan double tagging") Signed-off-by: David Bauer <mail@david-bauer.net>
* bcm53xx: MR32: fix DEVICE_VENODR typoChristian Lamparter2020-12-131-1/+1
| | | | | | DEVICE_VENDOR was misspelled as DEVICE_VENODR. Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: fix 5Ghz tx/rx power on the ASUS MAP-AC2200Yushi Nishida2020-12-131-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | The ASUS MAP-AC2200 suffers from a lower transmit/receive signal power as compared to the stock firmware. Upon investigation, it was discovered that stock firmware from the GPL_MAP-AC2200_3.0.0.4.384.46249-g97d05bb.tar archive. set the following GPIOs in "release/src/router/rc/init.c". GPIO 44 and 46 have to be set to output high GPIO 45 and 47 have to be set to output low Here are some results, after activating the relevant gpios through cmdline: <https://forum.openwrt.org/t/asus-map-ac2200-low-transmit-receive-signal-5ghz/69005/12> THX @ slh Fixes: 9ad3967f140 ("ipq40xx: add support for ASUS Lyra") Signed-off-by: Yushi Nishida <kyro2man@gmx.net> [slightly rewritten commit, added missing <>) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* mvebu: fix initramfs/kernel image for CZNIC Turris OmniaKarel Kočí2020-12-111-2/+1
| | | | | | | | | | | | | | | | | This adds DTB to kernel and that way makes it possible to easily boot initramfs image and also kernel. The sequence to boot initramfs on Omnia is then just: env set bootargs earlyprintk console=ttyS0,115200 dhcp 0x1000000 192.168.1.1:openwrt-mvebu-cortexa9-cznic_turris-omnia-initramfs-kernel.bin bootz 0x1000000 Without this change kernel boot won't proceed and is stuck on "Starting kernel". Signed-off-by: Karel Kočí <karel.koci@nic.cz> [fixed From: to match with SoB:] Signed-off-by: Petr Štetiar <ynezz@true.cz>
* realtek: Add missing case in switch statementRafał Mikrut2020-12-111-0/+1
| | | | | | | | | | | | Cppcheck shows here duplicated break. Code `state->speed = SPEED_1000;` will be never executed because above it there is break statement. Almost identical statement is placed in another realtek driver https://github.com/openwrt/openwrt/blob/18a53d43d646290053eff4736ec852efcf6bf510/target/linux/realtek/files-5.4/drivers/net/dsa/rtl83xx/dsa.c#L286-L294 Signed-off-by: Rafał Mikrut <mikrutrafal@protonmail.com>
* realtek: Fix self assignmentRafał Mikrut2020-12-111-1/+1
| | | | | | | | | Cppcheck shows self initialization error, which is an obvious bug. Basing on logic of similar fragment below I assigned to this variable, value `RTL838X_LED_GLB_CTRL` which I think is proper. Signed-off-by: Rafał Mikrut <mikrutrafal@protonmail.com>
* bcm63xx: DGND3700v1: use the real board nameDaniel González Cabanelas2020-12-111-1/+1
| | | | | | | | | | The Netgear DGND3700v1/DGND3800B shows kernel redundant info at the board message, already provided by the machine info message. Use the real board name which is silkscreened on the PCB and used in the stock firmware header. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* kernel: bump 5.4 to 5.4.82John Audia2020-12-093-46/+2
| | | | | | | | | | | | | | | | Removed since included upstream and could be reverse-applied by quilt: backport-5.4/315-v5.10-usbnet-ipeth-fix-connectivity-with-ios-14.patch Remaining modifications made by update_kernel.sh Build system: x86_64 Build-tested: ipq806x/R7800, ath79/generic, bcm27xx/bcm2711 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us> Tested-by: Curtis Deptuck <curtdept@me.com> [build/run x86_64]
* bcm63xx: add support for Innacomm W3400V6Sieng Piaw Liew2020-12-0912-26/+199
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Innacomm W3400V6 is an xDSL B/G wireless router based on Broadcom BCM6328 SoC. Hardware: SoC: Broadcom BCM6328 CPU: BMIPS4350 V8.0, 320 MHz, 1 core Flash: SPI-NOR 8MB, MX25L6406E RAM: 64 MB Ethernet: 4x 10/100 Mbps Switch: Integrated Wireless: 802.11b/g, BCM4312 LEDs/Buttons: 9x / 2x Flash instruction, web UI: 1) Set a static IP on your computer compatible with 192.168.1.1, i.e 192.168.1.100 2) Connect the ethernet cable from your computer to the router. 3) Make sure the router is powered off. 4) Press the reset button, don't release it yet! 5) While pressing reset, power on the router. 6) Wait 10 seconds or more. Note: The power LED is red at first then turns to solid green when ready. 8) Release the reset button. 9) Browse to 192.168.1.1 10) Select .bin file. 10) Upgrade the image. 11) Wait for it to reboot. Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> [Ammend commit description, merge patches, DT improvements] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: unlock MX25L6406E with 4 bit Block ProtectSieng Piaw Liew2020-12-091-0/+69
| | | | | | | | | | Hacked in basic support for 4 bit Block Protection register, copied from linux-master. Needed to unlock Innacomm W3400V's SPI flash MX25L6406E, compatible with MX25L6405D. Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> [Amend commit description, refresh patch] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ramips: use full names for Xiaomi Mi Router devicesAdrian Schmutzler2020-12-089-28/+30
| | | | | | | | | | This aligns the device/image names of the older Xiaomi Mi Router devices with their "friendly" model and DEVICE_MODEL properties. This also reintroduces consistency with the newer devices already following that scheme. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: mt7628: create shared DTSI for Xiaomi Mi Router 4A/4CAdrian Schmutzler2020-12-083-207/+130
| | | | | | | | | The Xiaomi Mi Router 4A (100M) and 4C are relatively similar in their specs. Create a shared DTSI for them. Partitions are split in preparation for Mi Router 4AC. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove redundant status for USB controllersAdrian Schmutzler2020-12-0732-245/+0
| | | | | | | | | | | | | | | | | | mt7621, mt7628an and rt5350 have USB controllers (ehci/ohci or xhci) enabled by default. Thus, this patch drops redundant status=okay statements in derived device DTS files. While at it, also drop an explicit status=okay in mt7621.dtsi, as this is default. Note: For rt5350, about 50 % of the devices enabled ehci/ohci in the DTS files, and there is actually no device actively disabling it. It looks like only a few people are aware that the controllers are enabled by default here. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: simplify status for ehci/ohci on mt7628 TP-Link devicesAdrian Schmutzler2020-12-0716-56/+72
| | | | | | | | | | | | | | At the moment, ehci/ohci is enabled in mt7628an SoC DTSI, then disabled in the TP-Link-specific DTSI files, and finally enabled again in the DTS files of the devices needing it. This on-off-on scheme is hard to grasp on a quick look. Thus, this patch drops the status in the TP-Link-specific DTSI files, having the TP-Link devices treated like the rest of mt7628an DTSes, i.e. ehci/ohci is enabled by default and needs to be disabled explicitly where needed. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for Belkin F9J1108v2 (AC1750 DB Wi-Fi)Damien Mascord2020-12-073-8/+277
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This device is the non-US build of the F9K1115 v2, with a different firmware magic. Specifications: SoC: QCA9558 CPU: 720 MHz Flash: 16 MiB NOR RAM: 128 MiB WiFi 2.4 GHz: QCA9558-AT4A 3x3 MIMO 802.11b/g/n WiFi 5 GHz: QCA9880-2R4E 3x3 MIMO 802.11a/n/ac Ethernet: 4x LAN and 1x WAN (all 1gbps) USB: 1 x USB 2.0 (lower), 1 x USB 3.0 (upper) MAC addresses based on OEM firmware: Interface Address Location --------- ------- -------- lan *:5A sometimes in 0x6 wan *:5B 0x0 2.4Ghz *:5A 0x1002 5Ghz As per mini PCIe EEPROM Flashing instructions: The factory.bin can be flashed via the Belkin web UI or via the uboot http upgrade page. Once the factory.bin has been written, sysupgrade.bin will work as usual. Signed-off-by: Damien Mascord <tusker@tusker.org> Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> [wrap commit message/code, adjust label-mac-device, whitespace fixes, merge block in 02_network] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: fix ADB P.DG A4001N A-000-1A1-AX LEDsÁlvaro Fernández Rojas2020-12-061-8/+2
| | | | | | | There's no eth0.2 since all ethernet ports as configured as LAN. LAN LED is unneeded since all ethernet ports have their own LED. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add support for Technicolor TG582nDaniele Castro2020-12-0614-26/+255
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Technicolor TG582n has a similar PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. Hardware: * Board ID: DANT-1 * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - Winbond W9751G6KB-25 * Serial flash: 16 Mbyte - MXIC MX25L6445EMI * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43227 Wireless Network Adapter (rev 30) * LEDs: 2x Power, 1x Ethernet, 1x Broadband, 2x Wi-Fi, 2x WPS, 4x ethernet * Buttons: 1x Reset, 1x WPS, 1x WiFi * UART: 1x TTL 115200n8, VCC GND TX RX, on J3 connector (short R62 and R63) Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the CFE boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file PCB: |GPIO: |TG582n: LED2R |488(08) |red Power LED2G |484(04) |green Power LED10R |486(06) | LED13G |485(05) |green Ethernet LED11R |494(14) | LED14G |491(11) |green Broadband LED5R |487(07) |red Internet LED5G |481(01) |green Internet LED12R |498(18) | LED12G |499(19) | LED6R |482(02) |red Wi-Fi LED6G |483(03) |green Wi-Fi LED7R |490(10) |red WPS LED7G |489(09) |green WPS LED4 |508(28) |ethernet port 4 LED3 |507(27) |ethernet port 3 LED9 |506(26) |ethernet port 2 LED8 |505(25) |ethernet port 1 SW3 |503(23) |key Reset SW5 |504(24) |key WPS SW4 |495(15) |key Wi-Fi SW6 |493(13) | SW1 |492(12) | Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [Fix base-files, refresh patch] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add support for Technicolor TG582n Telecom Italia brandedDaniele Castro2020-12-0614-26/+245
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Technicolor TG582n Telecom Italia branded a.k.a. Telecom Italia ADSL2+ Wi-Fi N (AGTWI) has the same PCB as the unbranded Technicolor TG582n with LEDs connected to different GPIO PINs in active low configuration and different LED names. It has a PCB similar to the OpenWrt's ADB P.DG A4001N1 one. Hardware: * Board ID: DANT-V * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - EtronTech EM68B16CWQD-25H * Serial flash: 16 Mbyte - Spansion FL 128SAIF00 * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43227 Wireless Network Adapter (rev 30) * LEDs: 2x Power, 1x ADSL, 2x Internet, 2x Wi-Fi, 2x Service, 4x ethernet * Buttons: 1x Reset, 1x WPS (named WiFi/LED) * UART: 1x TTL 115200n8, VCC GND TX RX, on J3 connector (short R62 and R63) Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the CFE boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file PCB: |GPIO: |TG582n: |AGTWI: LED2R |488(08) |red Power |red Power LED2G |484(04) |green Power |green Power LED10R |486(06) | |missing R85 end LED LED13G |485(05) |green Ethernet |green ADSL LED11R |494(14) | |red Internet LED14G |491(11) |green Broadband |green Internet LED5R |487(07) |red Internet |red Wi-Fi LED5G |481(01) |green Internet |green Wi-Fi LED12R |498(18) | |red Service LED12G |499(19) | |green Service LED6R |482(02) |red Wi-Fi |missing R108 end LED LED6G |483(03) |green Wi-Fi |missing R107 end LED LED7R |490(10) |red WPS |missing R91 end LED LED7G |489(09) |green WPS |missing R92 end LED LED4 |508(28) |ethernet port 4 |ethernet port 4 LED3 |507(27) |ethernet port 3 |ethernet port 3 LED9 |506(26) |ethernet port 2 |ethernet port 2 LED8 |505(25) |ethernet port 1 |ethernet port 1 SW3 |503(23) |key Reset |key Reset SW5 |504(24) |key WPS |key Wi-Fi/LED SW4 |495(15) |key Wi-Fi |missing R127 end key SW6 |493(13) | |missing R171 end key SW1 |492(12) | |missing R1 end key Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [DT fixes, base-files fixes and device variant] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add support for ADB P.DG A4101N A-000-1A1-AEDaniele Castro2020-12-0614-26/+227
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ADB P.DG A4101N A-000-1A1-AE has a similar PCB as the OpenWrt's ADB P.DG A4001N1 with LEDs connected to different GPIO PINs in active low configuration. Hardware: * Board ID: 96328avngv * SoC: Broadcom BCM6328 (rev b0) @ 320MHz, CPU BMIPS4350 * RAM DDR2: 64 Mbyte - Winbond W9751G6KB-25 * Serial flash: 16 Mbyte - Winbond 25Q128BVFG * Ethernet: 4x Ethernet 10/100 baseT * Wifi 2.4GHz: Broadcom Corporation BCM43225 Wireless Network Adapter (rev 23) * LEDs: 1x Power, 1x DSL, 1x Internet, 4x ETH, 1x USB, 1x WLAN, 1x WPS, 1x TEL * Buttons: 1x Reset, 1x WPS, 1x unnamed * UART: 1x TTL 115200n8, VCC RX TX GND, on J502 connector Installation via CFE: * Stock CFE has to be overwritten with a generic 6328 one that can upload .bin images with no signature check (cfe6328_configured.bin) * Connect a serial port to the board * Stop the cfe boot process after power on by pressing enter * Set static IP 192.168.2.10 and subnet mask 255.255.255.0 * Navigate to http://192.168.2.50/ * Upload the OpenWrt image file A4101N GPIO LAYOUT: Power always on DSL GPIO483(03) Internet GPIO491(11) ETH1 GPIO505(25) ETH2 GPIO506(26) ETH3 GPIO507(27) ETH4 GPIO508(28) USB GPIO490(10) WLAN controlled by BCM43225 WPS GPIO489(09) TEL GPIO511(31) Key RESET GPIO503(23) Key WPS GPIO504(24) Key unnamed GPIO492(12) Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [Amend commit description, DTS improvements, refresh patches] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: remove an unused callback from the ip17xx switch driverFelix Fietkau2020-12-052-34/+0
| | | | | | Also remove the leftover kernel hack that adds support for it Signed-off-by: Felix Fietkau <nbd@nbd.name>
* bcm63xx: Add support for D-Link DSL-2750u rev C1Ahmed Naseef2020-12-0513-9/+171
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for the D-Link DSL-2750u rev C1. (https://deviwiki.com/wiki/D-Link_DSL-2750U_rev_C1) It uses the same hardware as ADB P.DG A4001N. CPU: Broadcom BCM63281 (320 MHz) RAM: 32M (Winbond W9725G6JB) Flash: 8M (MXIC MX25L6445E) Ethernet: 4x 100 Mbps Wireless: 802.11b/g/n: BCM43225 USB: 1x 2.0 Flash instructions: 1. Assign static IP 192.168.1.100 to PC 2. Unplug the power source 3. Press the RESET button at the router, don't release it yet! 4. Plug the power source.Wait some seconds 5. Release the RESET button 6. Browse to http://192.168.1.1 7. Send the openwrt-bcm63xx-generic-DSL2750U-C1-squashfs-cfe.bin and wait some minutes until the firmware upgrade finish. Signed-off-by: Ahmed Naseef <naseefkm@gmail.com> [DTS improvements, proper board patch, refresh patches] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: A4001N A-000-1A1-AX: remove PSI (nvram) partitionDaniele Castro2020-12-051-6/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ADB P.DG A4001N A-000-1A1-AX a.k.a. Telecom Italia ADSL2+ Wi-Fi N (AGPWI) is a Telecom Italia braded router and it seems that there are no public available unbranded versions of this router. The stock Telecom Italia braded firmware has many partitions and the partition layout changes with every firmware relase. The PSI nvram partition is present in the stock firmware under the "UNKNOWN" name but it's empty, full of FFs. Since removing partitions does not cause problems with the stock firmware reflashing procedure, I removed from the dts the PSI nvram partition from OpenWrt, expanded the rootfs one and added the NVRAM partition contained in the cfe bootloader. Furthermore this router's flash needs to be entirely reprogrammed and a new generic bcm6328 cfe must be flashed to boot OpenWrt. The same process takes place when reflashing the stock firmware. Here follows the original flash layout for AGPWI_1.1.0_013, the last stock Telecom Italia braded firmware for which we have root credentials (admin/riattizzati). Flash layout: Section 00 Type BOOT Range 0x00000000-0x00020000 MaxSize 0x00020000 No more information. Section 01 Type IMAGE Range 0x00020000-0x007C0000 MaxSize 0x0079FF6C Uninitialized. Section 02 Type IMAGE Range 0x00800000-0x00FA0000 MaxSize 0x0079FF6C Uninitialized. Section 03 Type CONF Range 0x00FA0000-0x00FC0000 MaxSize 0x0001FF6C Size 0x0000841E Name 'rg_conf' Checksum 0x0041E03B Counter 0x0000051F Start Offset 0x00000000 Section 04 Type CONF Range 0x00FC0000-0x00FE0000 MaxSize 0x0001FF6C Size 0x0000838E Name 'rg_conf' Checksum 0x00419A5A Counter 0x00000522 Start Offset 0x00000000 Section 05 Type FACTORY Range 0x00FE0000-0x00FF0000 MaxSize 0x0000FF6C Size 0x00000554 Name 'rg_factory' Checksum 0x0001255E Counter 0x000004D3 Start Offset 0x00000000 Section 06 Type UNKNOWN Range 0x00FF0000-0x01000000 MaxSize 0x00010000 No more information. Total 7 sections found. The last AGPWI firmware relase should be AGPWI_4.0.6 and it has much more partitions than AGPWI_1.1.0_013. The cfe partition in the stock firmware is 0x00020000 bytes long unlike the OpenWrt dts in wich it's 0x00010000 bytes long because from 0x00010000 to 0x00020000 in the stock cfe there are only 00s and also because the cfe must anyway be reflashed with a generic bcm6328 cfe 0x00010000 bytes long to run OpenWrt. Signed-off-by: Daniele Castro <danielecastro@hotmail.it> [Amend commit, remove unneeded cfe_nvram partition] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: support xmit_more in BQLSieng Piaw Liew2020-12-051-0/+54
| | | | | | | | Support bulking hardware TX queue by using xmit_more. Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> [Amend commit description, fix kernel xmit_more exceptions] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add BQL supportSieng Piaw Liew2020-12-051-0/+67
| | | | | | | | Add Byte Queue Limits support to reduce/remove bufferbloat in bcm63xx target. Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> [Amend commit description] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ath79: add support for TP-Link TL-WDR7500 v3Adrian Schmutzler2020-12-044-2/+61
| | | | | | | | | | | | | | | | | | | | | | | | | | This ports support for the TP-Link TL-WDR7500 v3 from ar71xx to ath79. The basic features appear to be identical to the Archer C7 v1, however it has the (supported) QCA9880-BR4A chip of the C7 v2. Specifications: SoC: QCA9558 CPU: 720 MHz Flash: 8 MiB RAM: 128 MiB WLAN: 2.4 GHz b/g/n, 5 GHz a/n/ac Qualcomm Atheros QCA9880-BR4A Ethernet: 5x Gbit ports USB: 2x 2.0 ports Flashing instructions: Upload the factory image via the OEM firmware GUI. TFTP recovery appears to be available as well. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 5.4 to 5.4.81John Audia2020-12-049-20/+20
| | | | | | | | | | | | | | All modifications made by update_kernel.sh/no human intervention needed Build system: x86_64 Build-tested: ipq806x/R7800, ath79/generic, bcm27xx/bcm2711 Run-tested: ipq806x/R7800 No dmesg regressions, everything functional Signed-off-by: John Audia <graysky@archlinux.us> [another refresh] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: drop redundant status for gpio/gpio0Adrian Schmutzler2020-12-0445-180/+0
| | | | | | | | | | The first gpio controller (gpio or gpio0) is always enabled by default in the SoC DTSI files. No need to set status=okay in the device DTS files a second time. Remove the redundant statements. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: drop num-cs for SPI controllerAdrian Schmutzler2020-12-04171-297/+3
| | | | | | | | None of the spi drivers on ath79 uses the num-cs property. Cc: Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Chuanhong Guo <gch981213@gmail.com>
* ath79: remove num-chipselects from SPI controllerAdrian Schmutzler2020-12-049-14/+0
| | | | | | | | | | | | | | The num-chipselects property is only valid for bit-banged spi-gpio [1]. For the generic SPI controller bindings, num-cs would be the correct property [2]. Since num-cs is not required on ath79 either, just drop the lines. [1] https://www.kernel.org/doc/Documentation/devicetree/bindings/spi/spi-gpio.yaml [2] https://www.kernel.org/doc/Documentation/devicetree/bindings/spi/spi-controller.yaml Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* x86: enable CONFIG_MMC_SDHCI_ACPI for x86_64Mengyang Li2020-12-031-0/+2
| | | | | | | | | | | | | | | | | | | | | Some x86_64 single board computer (including Atomic Pi) has onboard emmc, but requires CONFIG_MMC_SDHCI_ACPI driver to use or boot from it. Here is boot message for the mmc device [ 2.838008] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA [ 2.857536] mmc1: SDHCI controller on ACPI [80860F14:01] using ADMA [ 2.950019] mmc0: new HS200 MMC card at address 0001 [ 3.158271] mmcblk0: mmc0:0001 M52516 14.6 GiB [ 3.170290] mmcblk0boot0: mmc0:0001 M52516 partition 1 4.00 MiB [ 3.177191] mmcblk0boot1: mmc0:0001 M52516 partition 2 4.00 MiB [ 3.183963] mmcblk0rpmb: mmc0:0001 M52516 partition 3 4.00 MiB, \ chardev (248:0) Other lines changed in this config file are introduced by menuconfig. Signed-off-by: Mengyang Li <mayli.he@gmail.com>
* brcm63xx: add USB status LED in 01_leds for ADP P.DG A4001NDaniele Castro2020-12-041-1/+2
| | | | | | Add a status LED in 01_leds for USB 2-1 connected devices. Signed-off-by: Daniele Castro <danielecastro@hotmail.it>
* ath79: remove ar934x MDIO reset from MAC nodeDavid Bauer2020-12-021-2/+2
| | | | | | | | | | | Remove the MDIO reset from the MAC mode for the AR934x SoC family. The reset is currently also defined for the MDIO node, where the reset is acquired exclusively. In case the ethernet node is enabled, this triggers a warning, as the reset is already acquired by the MAC. Signed-off-by: David Bauer <mail@david-bauer.net>
* bcm63xx: enetsw: switch to netdev_alloc_skb_ip_alignSieng Piaw Liew2020-12-021-0/+37
| | | | | | | | | | | | | | | | | | | Increases packet processing performance by 30%. Tested on BCM6328 320 MHz and iperf3 -M 512 for packet/sec performance. Before: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-30.00 sec 120 MBytes 33.7 Mbits/sec 277 sender [ 4] 0.00-30.00 sec 120 MBytes 33.5 Mbits/sec receiver After: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-30.00 sec 155 MBytes 43.3 Mbits/sec 354 sender [ 4] 0.00-30.00 sec 154 MBytes 43.1 Mbits/sec receiver Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> [Merge patches, amend commit and add patch description] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: batch process RX pathSieng Piaw Liew2020-12-021-0/+53
| | | | | | | | | | | | | | | | | | | Use netif_receive_skb_list to batch process skb in RX. Tested on BCM6328 320 MHz using iperf3 -M 512, increasing performance by 12.5%. Before: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-30.00 sec 120 MBytes 33.7 Mbits/sec 277 sender [ 4] 0.00-30.00 sec 120 MBytes 33.5 Mbits/sec receiver After: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-30.00 sec 136 MBytes 37.9 Mbits/sec 203 sender [ 4] 0.00-30.00 sec 135 MBytes 37.7 Mbits/sec receiver Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> [Amend commit description] Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 05:36:14 +0000