aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
...
* ar71xx: disable ENS202EXT in mikrotik and nand subtargetsJo-Philipp Wich2017-05-312-0/+2
| | | | Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ar71xx: move Wallys DR344 to generic build targetPiotr Dymacz2017-05-303-7/+10
| | | | Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: fix Wallys DR344 GPIO-connected LEDs and buttonPiotr Dymacz2017-05-303-10/+33
| | | | | | | | | | | | | | | | | | | | This fixes wrong GPIO numbers for LEDs and button in Wallys DR344 board and sets color of all LEDs to green as the mass production boards have only green one. Actually, DR344 has 6 GPIO-connected LEDs and one button: - GPIO11: status - GPIO12: sig1 - GPIO13: sig2 - GPIO14: sig3 - GPIO15: sig4 - GPIO16: reset button - GPIO17: lan WAN LED is connected directly with AR8035 PHY. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: set GE interface as wan by default in Wallys DR344Piotr Dymacz2017-05-301-1/+1
| | | | | | | This aligns default network interfaces configuration with vendor firmware: GE (eth0) -> wan, FE (eth1) -> lan. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: fix GE interface support in Wallys DR344Piotr Dymacz2017-05-301-30/+8
| | | | | | | | GMAC0 interface of AR9344 SOC in Wallys DR344 board is connected with AR8035, not with AR8327. Without this fix, GE interface doesn't work at all or shows high packet loss ratio. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* ar71xx: add support for EnGenius ENS202EXTMarty Plummer2017-05-3011-1/+179
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | EnGenius ENS202EXT is an outdoor wireless access point with 2-port 10/100 switch, detachable antennas and proprietery PoE. The device is based on Qualcomm/Atheros AR9341 v1. Specifications: - 535/400/200 MHz (CPU/DDR/AHB) - 64 MB of RAM - 16 MB of FLASH - UART (J1) header on PCB (unpopulated) - 2x 10/100 Mbps Ethernet - 2.4 GHz, up to 26dBm - 2x external, detachable antennas - 7x LED, 1x button Flash instructions: You have three options: - Use the vendor firmware upgrade page on the web interface and give it the factory.img. This is the easiest way to go about it. - If you have serial access during u-boot, interrupt the normal boot (any key before timeout) and run 'run failsafe_boot'; this will bring you to a minimal openwrt luci image on ip 192.168.1.1 useful if you've bricked the normal firmware. - Use the vendor's management cli, which can be accessed via telnet with the same credentials as the web login (default admin:admin), then issue the following commands: *** Hi admin, welcome to use cli(V-1.6.7) *** ---========= Commands Help =========--- stat -- Status sys -- System wless2 -- 2.4G-Wireless mgmt -- Management tree -- Tree help -- Help reboot -- Reboot ens202ext>mgmt Management ---========= Commands Help =========--- admin -- Administration mvlan -- Management VLAN settings snmp -- SNMP settings backup -- Backup/Restore settings autorb -- Auto reboot settings fwgrade -- Firmware upgrade time -- Time settings wifisch -- Wifi schedule log -- Log diag -- Diagnostics disc -- Device Discovery logout -- Logout help -- Help exit -- Exit ens202ext/mgmt>fwgrade Management --> Firmware upgrade ---========= Commands Help =========--- fwup -- Firmware upgrade help -- Help exit -- Exit ens202ext/mgmt/fwgrade>fwup http://web.server/lede-ar71xx-generic-ens202ext-squashfs-factory.bin Signed-off-by: Marty Plummer <ntzrmtthihu777@gmail.com>
* ar71xx: fix LED defines for TP-Link TL-WR740N v6Andrey Polischuk2017-05-309-18/+112
| | | | | | Signed-off-by: Andrey Polischuk <androld.b@gmail.com> [changed commit subject, dropped redundant kernel config symbol] Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
* mvebu: clearfog: assign SFP port to WAN zoneJosua Mayer2017-05-301-1/+1
| | | | | | | | | The single SFP port is meant for direct media access to WAN, such as VDSL2, GPON). While it could also be used for in-home fiber, it is much more likely that the LAN is standard ethernet, especially considering that SFP is the onmly port that can go beyond 1Gbps. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: clearfog: document interface configurationJosua Mayer2017-05-301-6/+9
| | | | | | | | | | | | | Take explicit note of what physical ports eth{0,1,2} refer to. Also repair port assignment: At some point between 4.9.20 and 4.9.29 the numbering changed. Keep previous port assignment that was: LAN = SFP+Switch WAN = standalone ethernet Also use the same assignment for Clearfog-Base to avoid confusion. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: clearfog: include DTB for all variants in imageJosua Mayer2017-05-301-3/+5
| | | | | | | Installing all armada-388-clearfog-* DTBs in the same sdcard image, it now becomes much easier to swap sdcards between different device variants. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* mvebu: update boot-script to use generic variablesJosua Mayer2017-05-302-10/+44
| | | | | | | | | | | U-Boot provides standard variables for load addresses, and filesystem-agnostic load-commands. Furthermore thanks to distro-boot, the device and partition from which the system boots is known. The new boot-script makes use of all this information. Tested on the only board that uses this boot-script: Clearfog Pro Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
* sunxi: sysupgrade: sync with x86Matthias Schiffer2017-05-292-50/+72
| | | | | | | | | | | | sunxi sysupgrade was based on the x86 implementation; sync fixes and other changes from the current x86 version: x86: fix sysupgrades on disks with 4k block size x86: sysupgrade: move partition table change check to platform_check_image x86: sysupgrade: refactor platform_do_upgrade x86: sysupgrade: explicitly rescan disk after writing partition table Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* sunxi: sysupgrade: don't write partitions twiceMatthias Schiffer2017-05-291-1/+1
| | | | | | | | | | | | | | When existing partitions are retained, the dd call writing the uboot image in the space before the first partition was accidentally writing the whole image, making the code for individual partitions redundant. Limit the copy to 1016KiB (the first 8KiB are skipped, and the first partition starts at 1024KiB). In addition, conv=notrunc is replaced with conv=fsync. It seems this was an oversight, as notrunc doesn't make sense for block devices and all other dd commands use conv=fsync. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* x86: sysupgrade: explicitly rescan disk after writing partition tableMatthias Schiffer2017-05-291-0/+6
| | | | | | | This should ensure that the kernel partition can be mounted in platform_copy_config when its size has changed. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* x86: sysupgrade: refactor platform_do_upgradeMatthias Schiffer2017-05-291-33/+36
| | | | | | | By returning early when no upgrade device can be found and handling the SAVE_PARTITIONS=0 case differently, we can get rid of two levels of if. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* x86: sysupgrade: move partition table change check to platform_check_imageMatthias Schiffer2017-05-291-4/+25
| | | | | | | The staged sysupgrade will prevent us from using ask_bool in platform_do_upgrade; therefore, the check is moved to platform_check_image. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ramips: sysupgrade: move nand_do_upgrade call to platform_do_upgradeMatthias Schiffer2017-05-291-8/+1
| | | | | | | All targets with NAND support should gradually move their nand_do_upgrade calls from platform_pre_upgrade to platform_do_upgrade. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* lantiq: pinctrl: xway: fix copy/paste error in xrx200_grpsMartin Schiller2017-05-292-1/+12
| | | | Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* ipq806x: add qpic nand and bam dma node's in ipq4019 dts treeRam Chandra Jangir2017-05-291-0/+172
| | | | | | | This change adds QPIC BAM dma and NAND driver node's in IPQ4019 device tree, also enable this for AP-DK04.1 based boards. Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
* ipq806x: Add support for custom data mapping in bam_dma dmaengineRam Chandra Jangir2017-05-291-0/+217
| | | | | | | This change adds a new function to support for preparing DMA descriptor for custom data. Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
* ipq806x: Added bam transaction and support additional CSRsRam Chandra Jangir2017-05-291-0/+1273
| | | | | | | | | This change adds support for below: - Bam transaction which will be used for any NAND request. - Reset function for NAND BAM transaction - Add support for additional CSRs. Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
* ipq806x: Add bam_dma support in qcom_nand driverRam Chandra Jangir2017-05-291-0/+382
| | | | | | | | | The existing qcom_nand driver supports ADM DMA which is mainly required for ipq806x family based boards, IPQ40xx based boards uses BAM DMA in NAND driver, so this patch adds BAM DMA support with compatible string as qcom,ebi2-nandc-bam. Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
* ipq806x: Add support to configure ipq40xx GPIO_PULL bitsRam Chandra Jangir2017-05-291-0/+260
| | | | | | | | | | GPIO_PULL bits configurations in TLMM_GPIO_CFG register differs for IPQ40xx from rest of the other qcom SoC's. This change add support to configure the msm_gpio_pull bits for ipq40xx, It is required to fix the proper configurations of gpio-pull bits for nand pins mux. Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
* brcm47xx: remove target specific network preinit configJo-Philipp Wich2017-05-272-32/+0
| | | | | | | | | The generic preinit code is now able to setup network and switch vlan settings from the /etc/board.json file, therefor drop the target specific code. Fixes FS#790. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* x86: fix build of geode targetHauke Mehrtens2017-05-271-0/+1
| | | | | | The build bot complained that the OLPC option was not set. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: add missing config optionsHauke Mehrtens2017-05-272-0/+5
| | | | | | | This broke the build for the x86 generic target. This was found by the build bot. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* Move enablemodem from ramips to new package adb-enablemodem and make it used ↵Filip Moc2017-05-273-19/+2
| | | | | | also by TL-MR6400 Signed-off-by: Filip Moc <lede@moc6.cz>
* ar71xx: Add support for TP-Link MR6400Filip Moc2017-05-2713-0/+197
| | | | | | | | | | | | | | | | | You can flash via tftp recovery (serve factory image as /mr6400_tp_recovery.bin on 192.168.0.66/24, connect to any ethernet port and power on device while holding the reset button). Flashing via OEM web interface does not work. Hardware Specification (v1.0 EU): - SoC: QCA9531 - Flash: Winbond W25Q64FV (8MiB) - RAM: EtronTech EM6AB160TSE-5G (64MiB) - Wireless: SoC platform only (2.4GHz b/g/n, 2x internal antenna) - Ethernet: 2NIC (3x100M + 1x100M) - WWAN: TP-LINK LTE MODULE (2x external detachable antenna) - Power: DC 12V 1A Signed-off-by: Filip Moc <lede@moc6.cz>
* ramips: remove fictional LEDs from AsiaRF AWM00x device treeRussell Senior2017-05-271-14/+0
| | | | | | | | | Neither the AsiaRF AWM002 or AWM003 actually has an LED on the module board. The ld1 and ld2 do not represent actual LEDs. These pins might connect to LEDS on an eval board or other carrier board, but that is outside the scope of this device tree file. Signed-off-by: Russell Senior <russell@personaltelco.net>
* kernel: update kernel 4.9 to 4.9.30Hauke Mehrtens2017-05-2710-13/+13
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* uml: Fix sample command lineFlorian Fainelli2017-05-261-2/+2
| | | | | | Provide paths that match where LEDE is staging images. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* uml: Check for glibc static librariesFlorian Fainelli2017-05-261-0/+11
| | | | | | | | UML statically links against libutil, librt and libpthread. Some hosts do not necessarily have these libraries installed and we should find out sooner than later (during the final vmlinux linking stage) about that. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* treewide: fix device tree path in scriptsMathias Kresin2017-05-262-2/+2
| | | | | | | | The device tree is at /proc/device-tree/ without a base subdir. Fixes: da472e5b30f6 ("treewide: access device tree from userspace via /proc/") Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for GL-inet GL-MT300N-V2Kyson Lok2017-05-267-0/+155
| | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds supports for the GL-inet GL-MT300N-V2. Specification: - SoC: MediaTek MT7628AN - Flash: 16 MiB (W25Q128FVSG) - RAM: 128 MiB DDR - Ethernet: 1 x WAN (100 Mbps) and 1 x LAN (100 Mbps) - USB: 1 x USB 2.0 port - Button: 1 x switch button, 1 x reset button - LED: 3 x LEDS (system power led is not GPIO controller) - UART: 1 x UART on PCB (JP1: 3.3V, RX, TX, GND) Installation through Luci: - The original firmware is LEDE, so both LuCI or sysupgrade can be used. - Do not keep settings, for sysupgrade please use the -n option. Installation through bootloader webserver: - Plug power and hold reset button until red LED blink to bright. - Install sysupgrade image using web interface on 192.168.1.1. Signed-off-by: Kyson Lok <kysonlok@gmail.com> [match maximum image size with firmware partition] Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: access device tree from userspace via /proc/Mathias Kresin2017-05-262-2/+2
| | | | | | | Access the device tree via /proc/device-tree/ is the documented way to access the properties. Everything else might not work in future. Signed-off-by: Mathias Kresin <dev@kresin.me>
* x86/legacy: disable PAE againDaniel Golle2017-05-251-1/+1
| | | | | | | | | | | commit 961c0eacea ('x86: fix lifting kernel CPU requirements and always enable PAE') broke some older geode boards such as Soekris net4826. Hence disable PAE on x86/legacy again in order to still support those very old non-PAE capable CPUs. Fixes FS#773 - PAE broke Soekris net4826 Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* DWR-512: adding wwan support for the dwr-512 3G modemGiuseppe Lippolis2017-05-251-2/+2
| | | | | | | | | This PR allow the 3G modem embedded in the DWR-512 to be managed by the wwan-ncm scripts. The modem will use the usb-option and usb-cdc-ether drivers. The DWR-512 DT is updated accordingly. Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com>
* x86_64: add drivers for Xeon controller hub based GPIOPhilip Prindeville2017-05-251-2/+4
| | | | | | | These drivers are in many reference-design Xeon, iCore, or Atom64 based server boards. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* octeon: remove linux 4.4 supportFelix Fietkau2017-05-256-2051/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* Make GBit switch work on RB2011René Mayrhofer2017-05-251-1/+2
| | | | | | | | | | | | | | | | | | | | | This change is required to make the GBit switch work on my Mikrotik Routerboard RB2011UiAS-RM, and I assume that the other RB2011 variants are exactly the same in terms of the switch. I have tested the board without and with the patch and confirm that the GBit ports are not supported at all (i.e. no communication works) with the current version in trunk and that everything works with the patch applied. The test box has been running for a few days with the patch applied, and does not show any performance problems in a test setting. I have not used it with LEDE in production so far, but with a previous turnk version of OpenWRT for many years - with the same patch applied. I therefore have good indication that it is stable. For the record, the switch chip on my test box is identified as switch0: Atheros AR8327 rev. 4 switch registered on ag71xx-mdio.0 The value 0x6f000000 has been taken from the table at https://wiki.openwrt.org/toh/mikrotik/rb2011uias with the previous discussion thread still online at https://lists.openwrt.org/pipermail/openwrt-devel/2014-December/029949.html. One definite improvement from the older OpenWRT trunk version I have been running in production and current LEDE trunk is that the SFP interface can be kept in the default configuration without excessive kernel messages about it constantly going up and down. I have not yet tested an actual SFP module, though. Performance seems to be reasonable. Routing between two GBit ports on that switch separated by different VLANs with the default firewall ruleset (and one additional rule two allow traffic between the VLANs), but without NAT, iperf3 results are: [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 508 MBytes 426 Mbits/sec 102 sender [ 4] 0.00-10.00 sec 506 MBytes 425 Mbits/sec receiver With a connection going through NAT (also 2 ports on the same GBit switch, same ruleset, but NAT active), routing performance drops to around 250 MBit/s. (Note that RouterOS achieves beyond 900 MBit/s on the same hardware with the default rule set and the FastTrack rule active even for NAT, see https://wiki.mikrotik.com/index.php?title=Manual:IP/Fasttrack and http://www.mikrotik.com/download/share/FastTrack.pdf). Summarizing, I strongly recommend to apply this patch in trunk, so that the GBit switch chip rev. 4 can be supported upstream in the next LEDE release (hopefully soon). Signed-off-by: René Mayrhofer <rene@mayrhofer.eu.org>
* ar71xx: change image version for ubiquiti devicesMatthias Fritzsche2017-05-251-3/+3
| | | | | | | | | | changes the image version from hardcoded OpenWrt to $VERSION_DIST. AirOS shows a notification with the image version during a firmware upgrade. fixes #582 Signed-off-by: Matthias Fritzsche <txt.file@txtfile.eu>
* brcm2708: enable cpufreqStijn Tintel2017-05-233-8/+42
| | | | | | | | | | | | | With cpufreq disabled, the CPU stays locked at the frequency set by the bootloader. This severely degrades performance as the bootloader sets the CPU at the lowest frequency by default. Enable cpufreq for all subtargets and use the ondemand governor. Tested bcm2708 on RPi0W. Tested bcm2709 and bcm2710 on RPi3. Reported-by: Bryan Mayland <bmayland@capnbry.net> Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* lantiq: spi: double time out toleranceHauke Mehrtens2017-05-211-0/+37
| | | | | | | | | | | | | | | | | | | The generic SPI code calculates how long the issued transfer would take and adds 100ms in addition to the timeout as tolerance. On my 500 MHz Lantiq Mips SoC I am getting timeouts from the SPI like this when the system boots up: m25p80 spi32766.4: SPI transfer timed out blk_update_request: I/O error, dev mtdblock3, sector 2 SQUASHFS error: squashfs_read_data failed to read block 0x6e After increasing the tolerance for the timeout to 200ms I haven't seen these SPI transfer time outs any more. The Lantiq SPI driver in use here has an extra work queue in between, which gets triggered when the controller send the last word and the hardware FIFOs used for reading and writing are only 8 words long. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: update kernel 4.9 to 4.9.29Koen Vandeputte2017-05-2170-1087/+147
| | | | | | | | | | | | | - Refresh all patches - Removed upstreamed - Adapted 1 Compile tested on: bcm53xx, cns3xxx, imx6, lantiq Run tested on: cns3xxx & imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [update from 4.9.28 to 4.9.29] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: update kernel 4.4 to version 4.4.69Kevin Darbyshire-Bryant2017-05-2124-428/+143
| | | | | | | | | | | | | | | | | | | Refresh patches. A number of patches have landed upstream & hence are no longer required locally: 062-[1-6]-MIPS-* series 042-0004-mtd-bcm47xxpart-fix-parsing-first-block Reintroduced lantiq/patches-4.4/0050-MIPS-Lantiq-Fix-cascaded-IRQ-setup as it was incorrectly included upstream thus dropped from LEDE. As it has now been reverted upstream it needs to be included again for LEDE. Run tested ar71xx Archer C7 v2 and lantiq. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> [update from 4.4.68 to 4.4.69] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* bcm53xx: add support for TP-LINK Archer C5 V2Rafał Miłecki2017-05-215-3/+71
| | | | | | | | This model also contains few partitions non-discoverable partitions we need to "protect". Othen than that it uses non-deprecated serial entry in DTS that doesn't work with LEDE so we need to workaround it as well. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* Revert "ar71xx: Add support for Teltonika RUT900"John Crispin2017-05-1811-525/+1
| | | | | | | | This reverts commit 224e5f5efa22b8a0132522367afd3b22f05d53e1. pepe2k pointed out that this was not ready to merge Signed-off-by: John Crispin <john@phrozen.org>
* ramips: support jumbo frame on mt7621 up to 2kMichael Lee2017-05-184-17/+32
| | | | Signed-off-by: Michael Lee <igvtee@gmail.com>
* ar71xx: Add support for Teltonika RUT900Steffen Weinreich2017-05-1811-1/+525
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Teltonika RUT900 is a Router with LTE dual SIM, WiFi, 4x Ethernet ports, I/O, RS232, RS485, GPS. The device ist based on a Atheros AR9344 rev 3, Specifications: - 560/450/225 MHz (CPU/DDR/AHB) - 128 MB of RAM - 16 MB of FLASH - Serial Console header on a Card Board edge connector - 4x 10/100 Mbps Ethernet (3x LAN, 1x WAN) - 2.4 GHz Wifi - 2x external, detachable Wifi antennas - LTE Modem Huawei ME909u-521 (Also other Modem seen) - 2x LTE antennas - 1x GPS antenna - 7x LED, 1x button - 1x USB Connector - 1x Serial RS232 - 1x Serial RS485 - 1x MicroSD Card The GPL sources of the device are available at www.teltonika.lt/gpl/ and are based on OpenWRT Barrier Breaker (14.07) Running from tftp: The Router starts into the uboot Webupdater if the Button ist pressed more than 3 seconds, if no Network cable is attached it starts the uboot serial console, from there the router loads the firmware image via tftpboot from 192.168.1.2:firmware.bin (the router has the 192.168.1.1). With bootm the loaded image will be booted. Signed-off-by: Steffen Weinreich <steve@weinreich.org>
* kernel: add hwmon for W83627EHF and familyPhilip Prindeville2017-05-171-0/+32
| | | | | | | | Remove support for NCT6775/6 from W83627EHF driver so the NCT6775 driver will still be used for those chips. Signed-off-by: Daniel Golle <daniel@makrotopia.org> Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-31 00:34:26 +0000