aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* apm821xx, ath79, ipq40xx, ipq806x, lantiq, ramips: base-files: Use generic ↵Petr Štetiar2018-12-066-273/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | diag.sh I wanted to add status LEDs support to my imx6 based board and have found out, that I could use diag.sh script found in ramips platform, which seems to be also shared in a few other platforms: 4801276bc2078c5bcf03003c831e3b0a target/linux/ramips/base-files/etc/diag.sh 4801276bc2078c5bcf03003c831e3b0a target/linux/ipq40xx/base-files/etc/diag.sh 4801276bc2078c5bcf03003c831e3b0a target/linux/ath79/base-files/etc/diag.sh And @chunkeey suggested to me, that I can also add lantiq, ipq806x and apm821xx to the list of platforms which could share this generic diag.sh. I've extended the base diag.sh in a way, that if it detects any of the DTS LED aliases, then it would use the generic DTS set_led_state code. The code in platform's diag.sh has moved to base-files package in this commit: base-files: diag.sh: Make it more generic towards DTS so it could be reused Signed-off-by: Petr Štetiar <ynezz@true.cz> Tested-by: Christian Lamparter <chunkeey@gmail.com> (apm821xx and ipq40xx)
* base-files: diag.sh: Make it more generic towards DTS so it could be reusedPetr Štetiar2018-12-061-2/+48
| | | | | | | | | | | | | | | | I wanted to add status LEDs support to my imx6 based board and have found out, that I could use diag.sh script found in ramips platform, which seems to be also shared in a few other platforms: 4801276bc2078c5bcf03003c831e3b0a target/linux/ramips/base-files/etc/diag.sh 4801276bc2078c5bcf03003c831e3b0a target/linux/ipq40xx/base-files/etc/diag.sh 4801276bc2078c5bcf03003c831e3b0a target/linux/ath79/base-files/etc/diag.sh So I've extended the base diag.sh in a way, that if it detects any of the DTS LED aliases, then it would use the generic DTS set_led_state code. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* kernel: add DT binding support to AVM EVA parserDavid Bauer2018-12-061-0/+6
| | | | | | | It allows selecting split-firmware parser directly by specifying image-format in the device-tree. Signed-off-by: David Bauer <mail@david-bauer.net>
* comgt: Fix 3g.sh permissionsRosen Penev2018-12-061-2/+2
| | | | | | 3g.sh needs to be executable. 600 is not correct for that. Signed-off-by: Rosen Penev <rosenp@gmail.com>
* octeon: Evaluate board names in alphabetical orderJonathan Thibault2018-12-061-5/+5
| | | | Signed-off-by: Jonathan Thibault <jonathan@navigue.com>
* ipq806x: dts: Add support for RGMII RX and TX clock delaysRam Chandra Jangir2018-12-061-0/+3
| | | | | | | This change enables support to select phy4 in RGMII mode and enables RGMII TX/RX clock internal delays. Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
* kernel: ar83xx: Add support for three GMAC's connectionRam Chandra Jangir2018-12-064-1/+69
| | | | | | | | | | | | | We have IPQ8064 AP161 board which has three GMAC's * RGMII x2 * SGMII x1. The existing ar8327 driver does not have support for three GMAC's connection, hence this change adds support for the same. This has been verified on AP148 and AP161 board. Signed-off-by: xiaofeis <xiaofeis@codeaurora.org> Signed-off-by: Ram Chandra Jangir <rjangir@codeaurora.org>
* ar71xx: Add usb drivers in Archer C7 v4/v5 imagesDaniel Halmschlager2018-12-051-1/+1
| | | | | | | | | | | | This commit adds the default usb packages - kmod-usb-core - kmod-usb2 - kmod-usb-ledtrig-usbport for Archer C7 v4 and v5. (The C7 v5 configuration is based on the v4, therefore the change for v4 also applies for v5.) Signed-off-by: Daniel Halmschlager <dh@dev.halms.at>
* base-files: fix several bashismsMichael Heimpold2018-12-055-5/+5
| | | | | | | For equality test a simple = is sufficient, the == is usually disregarded as bashism. Signed-off-by: Michael Heimpold <mhei@heimpold.de>
* ipq40xx: fix openmesh sysupgrade with tar content out of orderMarek Lindner2018-12-051-3/+3
| | | | | | | | | | | | The tar extraction depends on the order in which the files are added to the tar file. Since the order is not guaranteed and depends on the host system, the combined mtd write fails with sysupgrade images built on some systems. Fix by changing to tar file order independent mtd write. Fixes: 86e18f6706e1 ("ipq806x: add support for OpenMesh A42") Signed-off-by: Marek Lindner <mareklindner@neomailbox.ch> Signed-off-by: Sven Eckelmann <sven@narfation.org>
* ipq40xx: add support for EnGenius EAP1300Steven Lin2018-12-058-8/+263
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | SOC: IPQ4018 / QCA Dakota CPU: Quad-Core ARMv7 Processor rev 5 (v7l) Cortex-A7 DRAM: 256 MiB NOR: 32 MiB ETH: Qualcomm Atheros QCA8072 WLAN1: Qualcomm Atheros QCA4018 2.4GHz 802.11bgn 2:2x2 WLAN2: Qualcomm Atheros QCA4018 5GHz 802.11a/n/ac 2:2x2 INPUT: RESET Button LEDS: Power, LAN, MESH, WLAN 2.4GHz, WLAN 5GHz 1. Load Ramdisk via U-Boot To set up the flash memory environment, do the following: a. As a preliminary step, ensure that the board console port is connected to the PC using these RS232 parameters: * 115200bps * 8N1 b. Confirm that the PC is connected to the board using one of the Ethernet ports. Set a static ip 192.168.99.8 for Ethernet that connects to board. The PC must have a TFTP server launched and listening on the interface to which the board is connected. At this stage power up the board and, after a few seconds, press 4 and then any key during the countdown. U-BOOT> set serverip 192.168.99.8 && set ipaddr 192.168.99.9 && tftpboot 0x84000000 openwrt.itb && bootm 2. Load image via GUI a. Upgrade EAP1300 to FW v3.5.3.2 In the GUI, System Manager > Firmware > Firmware Upgrade, to do upgrade. b. Transfer to OpenWrt from EnGenius. In Firmware Upgrade page, to upgrade yours openwrt-ipq40xx-engenius_eap1300-squashfs-sysupgrade.bin. 3. Revert to EnGenius EAP1300 To flash openwrt-ipq40xx-engenius_eap1300-squashfs-factory.bin by using sysupgrade command and "DO NOT" keep configuration. $ sysupgrade –n openwrt-ipq40xx-engenius_eap1300-squashfs-factory.bin Signed-off-by: Steven Lin <steven.lin@senao.com>
* brcm2708-gpu-fw: add fw required for camera moduleStijn Tintel2018-12-052-0/+22
| | | | | | | | To be able to use the camera module, start_x=1 has to be set in config.txt. This will cause the bootloader to load the GPU firmware that contain the extra video codecs. Install these firmware files. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* brcm2708-gpu-fw: update to git HEADStijn Tintel2018-12-051-7/+7
| | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: add missing symbolStijn Tintel2018-12-042-0/+2
| | | | Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* mac80211: fix brcmfmac on brcm2708Stijn Tintel2018-12-041-0/+76
| | | | | | | | | An upstream change broke brcmfmac when loaded with modparam roamoff=1. As we are carrying a patch that enables roamoff by default on the brcm2708 target to improve stability, wireless is currently broken there. Add a patch to fix brcmfmac with roamoff=1. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* ramips: fix Netgear EX3700/EX3800 wireless driver selectionMathias Kresin2018-12-041-1/+1
| | | | | | Fix the typo to select kmod-mt76x2. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mt76: update to the latest versionFelix Fietkau2018-12-041-3/+3
| | | | | | | | | | | 5a5b396 mt76: throttle transmission of buffered multicast packets 8084323 mt7603: implement code for adjusting energy detect CCA thresholds 8929a6e mt7603: increase MCU timeout f2ba65f mt7603: update firmware to 20161027164355 0ad998b mt7603: increase aggregation limits (based on vendor driver changes) da00af0 mt7603: clear bit 18 in MT_SEC_SCR to fix ICV error Signed-off-by: Felix Fietkau <nbd@nbd.name>
* Revert "kernel: use add_mtd_partitions() helper when using OpenWrt parsers"Rafał Miłecki2018-12-033-12/+20
| | | | | | | | | | | | | | | | | | | This reverts commit 7e88753ace0022bd56f77a7a647894f2936cf17b. Using subpartitions (hierarchical layout) resulted in calling MTD ops of parent partition instead of master device ops. That was expected and should work but testing revealed some bugs. Apparently the way MTD_ERASE_PARTIAL is implemented in the OpenWrt breaks something and using parent partition ops triggers using that code. On SmartRG SR400ac it was resulting in: [ 225.487519] jffs2: Erase at 0x01ac0000 failed immediately: errno -22 on the second boot (for some reason erasing was starting over) and it was breaking flash access in a long term. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: add support for D-Link DWR-118-A1Pawel Dembicki2018-12-036-0/+215
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The DWR-118-A1 Wireless Router is based on the MT7620A SoC. Specification: - MediaTek MT7620A (580 Mhz) - 64 MB of RAM - 16 MB of FLASH - 1x 802.11bgn radio - 1x 802.11ac radio (MT7610EN) - 3x 10/100 Mbps Ethernet (3 LAN) - 2x 10/100/1000 Mbps ICPlus IP1001 Ethernet PHY (1 WAN AND 1 LAN) - 1x internal, non-detachable antenna - 2x external, non-detachable antennas - 1x USB 2.0 - UART (J1) header on PCB (57600 8n1) - 7x LED (5x GPIO-controlled), 2x button - JBOOT bootloader Known issues: - WIFI 5G LED not working - flash is very slow The status led has been assigned to the dwr-118-a1:green:internet led. At the end of the boot it is switched off and is available for other operation. Work correctly also during sysupgrade operation. Installation: Apply factory image via http web-gui or JBOOT recovery page How to revert to OEM firmware: - push the reset button and turn on the power. Wait until LED start blinking (~10sec.) - upload original factory image via JBOOT http (IP: 192.168.123.254) Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* ramips: mt7620: select only the matching mt76 driverChen Minqiang2018-12-032-25/+28
| | | | | | | | | | | | | Because every device has selected the corresponding mt76 driver, we can now disable the mt76 metapackage by default to make sure that other devices (those don't need mt76) avoid selecting unwanted packages. We can find the hardware specifies and determine the dependencies on these sites: https://wikidevi.com/wiki/ https://openwrt.org/toh/hwdata/ Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
* ramips: mt7620: drop mt76 driver for boards without mt76 wirelessChen Minqiang2018-12-031-4/+4
| | | | | | | These boards don't have a mt76 wireless at all and don't need any of the mt76 family drivers. Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
* ramips: mt7620: disable PCIe if nothing is attachedMathias Kresin2018-12-034-16/+0
| | | | | | | | All boards neither expose the PCIe as Mini-PCIe nor have anything attached to the PCIe Bus. Disable PCIe for those by dropping the node from the dts files. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: mt7620: add missing pci wifi nodes to dts filesChen Minqiang2018-12-033-0/+24
| | | | | | | | | These devices has pci wifi but not defined in dts: HC5761 HC5861 TINY-AC Signed-off-by: Chen Minqiang <ptpt52@gmail.com>
* kernel: use add_mtd_partitions() helper when using OpenWrt parsersRafał Miłecki2018-12-033-20/+12
| | | | | | | | | | | | | | | | | | | | | | | | This helper uses hierarchical partitions layout following the way upstream parsers work. It's closer to what we should use when mainlining our solutions. It also doesn't require hacky casting of struct mtd_partition to the const. THIS WILL AFFECT KERNEL PRINTING PARTITIONS IN THE LOG Something like: [ 3.930158] 0x0000004e0000-0x000001fb0000 : "rootfs_data" will get replaced by: [ 3.907338] Creating 1 MTD partitions on "rootfs": [ 3.912142] 0x00000031d400-0x000001ded400 : "rootfs_data" It's important to understand that "rootfs_data" in above example is a *subpartition* of the "rootfs" now. To get absolute addresses (e.g. for some debugging purposes) one has to add them to the "rootfs", e.g. [ 3.912548] 0x0000001c2c00-0x000001fb0000 : "rootfs" (0x1c2c00 + 0x31d400 = 0x4e0000) Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: backport 2 mtd partitioning fixesRafał Miłecki2018-12-0310-20/+133
| | | | | | This improves handling of subpartitions. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* openvpn: add list element parsingFlorian Eckert2018-12-033-3/+20
| | | | | | | | | | | | | For the parameters tls-cipher and ncp-ciphers more than one option can be used in the OpenVPN configuration, separated by a colon, which should be implemented as a list in order to configure it more clearly. By adding the new OPENVPN_LIST option to the openvpn.options file with the tls-cipher and ncp-cipher parameters, uci can now add this option as a "list" and the init script will generate the appropriate OpenVPN configuration from it. Signed-off-by: Hans Dedecker <dedeckeh@gmail.com> Signed-off-by: Florian Eckert <fe@dev.tdt.de>
* kernel: fix downloading rcX releasesRafał Miłecki2018-12-032-4/+17
| | | | | | | | They are no longer stored in the "testing" subdirectory and are not available as .tar.xz archives. If -rc is detected download it from the git.kernel.org and use .tar.gz. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ath79: add support for Ubiquiti AirRouterRussell Senior2018-12-034-1/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Indoor low-power router with 2.4 GHz radio CPU: Atheros AR7241 rev 1 RAM: 32 MB Flash: 8 MB NOR SPI Switch: Atheros AR7240 Ports: 1x WAN, 4x LAN 10/100 Ethernet WLAN: Atheros AR9285 (2.4 GHz) USB: 1x USB2 host port Note: Ethernet WAN/LAN port naming is reversed from ar71xx. WAN is eth0; LAN is eth1.1. UART settings: 115200, 8N1 LEDs +-------------------------- | | | | | | | | VCC | x x RX | * x | x x | x x TX | * x GND | * x | | | | +-------------------------- ETHERNET PORTS Installation from Ubiquiti firmware, is as for other ubnt-xm AirOs devices. Signed-off-by: Russell Senior <russell@personaltelco.net>
* ath79: split ubnt outdoor device leds into separate dtsiRussell Senior2018-12-035-31/+39
| | | | | | Move common LED configuration into a separate includible dtsi. Signed-off-by: Russell Senior <russell@personaltelco.net>
* cryptodev-linux: move from packages feedEneas U de Queiroz2018-12-031-0/+60
| | | | | | | | | | | | | | | The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software. This is actually a build dependency for /dev/crypto support in openssl. Since it is a kernel module, it belongs here anyway. - Removed Nikos Mavrogiannopoulos as maintainer. - Streamlined make flags Signed-off-by: Eneas U de Queiroz <cote2004-github@yahoo.com>
* x86: make sysupgrade.tgz reachable againTomasz Maciej Nowak2018-12-031-1/+1
| | | | | | | | | Moving binding mount before check for saved sysupgrade configuration made it unreachable. Fix it by moving binding mount after the check. Fixes: f78b2616 (x86: mount writable bootfs) Reported-by: Lucian Cristian <luci@powerneth.ro> Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* Revert "base-files: fwtool: Fix wrong checksum on combined-image with metadata"Jo-Philipp Wich2018-12-021-1/+1
| | | | | | | | | | | | | | | | | This reverts commit 41770add03ad77a0ce41ed424ad050238f7d9272. The fwtool_check_image() procedure is used by `sysupgrade --test` which must not alter the image under test in any way. Currently, when the LuCI ui or any other sysupgrade wrapper first invokes sysupgrade --test to verify the compatibility of the image and then calculates the sha256sum over it, the resulting checksum will differ from the original image since the test invocation will implicitely strip the metadata trailer. To properly fix the underlying issue, the combined image checksumming code must be modified to skip the metadata trailer. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* ramips: merge relocate compile into build recipeMathias Kresin2018-11-302-10/+5
| | | | | | | Compile the loader if the relocate-kernel image recipe is used and get rid of the legacy build code to do so. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: specify "firmware" partition format in JBOOT devicesPawel Dembicki2018-11-305-3/+8
| | | | | | | | | | | | | Specify firmware partition format by compatible string. List of devices: -DWR-116-A1 -DWR-118-A2 -DWR-512-B -DWR-921-C1 -LR-25G001 Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* kernel: add DT binding support to the jimage parserPawel Dembicki2018-11-301-0/+11
| | | | | | | | It allows specifying jimage parser directly in the DT. Tested on LAVA LR-25G001 Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* ramips: add support for MTC Wireless Router WR1201Valentín Kivachuk2018-11-305-0/+187
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | MTC Wireless Router WR1201 is the OEM name of the board. It is also sold rebranded as STRONG Dual Band Gigabit Router 1200. Specification: - SoC: MediaTek MT7621A (880 MHz) - Flash: 16 MiB - RAM: 128 MiB - Wireless: 2.4Ghz(MT7602EN) and 5Ghz (MT7612EN) - Ethernet speed: 10/100/1000 - Ethernet ports: 4+1 - 1x USB 3.0 - 1x microSD reader - Serial baud rate of Bootloader and factory firmware: 57600 The OEM webinterface writes only as much bytes as listed in the uImage header field to the flash. Also, the OEM webinterface evaluates the name field of uImage header before flashing (the string "WR1201_8_128") To flash via webinterface, is mandatory to use first initramfs.bin and after (from the OpenWrt) the sysupgrade.bin Some notes: - Some microSD will not work: mtk-sd 1e130000.sdhci: no support for card's volts mmc0: error -22 whilst initialising SDIO card mtk-sd 1e130000.sdhci: no support for card's volts mmc0: error -22 whilst initialising MMC card mtk-sd 1e130000.sdhci: no support for card's volts mmc0: error -22 whilst initialising SDIO card mtk-sd 1e130000.sdhci: card claims to support voltages below defined range mtk-sd 1e130000.sdhci: no support for card's volts mmc0: error -22 whilst initialising MMC card mtk-sd 1e130000.sdhci: no support for card's volts mmc0: error -22 whilst initialising SDIO card mtk-sd 1e130000.sdhci: no support for card's volts mmc0: error -22 whilst initialising MMC card Signed-off-by: Valentín Kivachuk <vk18496@gmail.com>
* odhcpd: update to latest git HEADHans Dedecker2018-11-291-4/+4
| | | | | | | d404c7e netlink: fix triggering of NETEV_ADDR6LIST_CHANGE event ae6cf80 config: correctly break string for prefix filter Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
* ramips: specify "firmware" partition formatINAGAKI Hiroshi2018-11-29246-0/+246
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specify firmware partition format by compatible string. formats in ramips: - denx,uimage - tplink,firmware - seama It's unlikely but the firmware splitting might not work any longer for the following boards, due to a custom header: - EX2700: two uImage headers - BR-6478AC-V2: edimax-header - 3G-6200N: edimax-header - 3G-6200NL: edimax-header - BR-6475ND: edimax-header - TEW-638APB-V2: umedia-header - RT-N56U: mkrtn56uimg But it rather looks like the uImage splitter is fine with the extra header. The following dts are not touched, due to lack of a compatible string in the matching firmware splitter submodule: - CONFIG_MTD_SPLIT_JIMAGE_FW DWR-116-A1.dts DWR-118-A2.dts DWR-512-B.dts DWR-921-C1.dts LR-25G001.dts - CONFIG_MTD_SPLIT_TRX_FW WCR-1166DS.dts WSR-1166.dts - CONFIG_MTD_SPLIT_MINOR_FW RBM11G.dts RBM33G.dts - CONFIG_MTD_SPLIT_LZMA_FW AR670W.dts - CONFIG_MTD_SPLIT_WRGG_FW DAP-1522-A1.dts Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ramips: unifiy sysupgrade file extensionsMathias Kresin2018-11-292-8/+7
| | | | | | | Use .bin as file extension where possible. The user doesn't need to that sysupgrade images for NAND boards are tarballs. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: remove duplicate image build variablesMathias Kresin2018-11-291-4/+1
| | | | | | | Remove image build variables which are set to the same value as the default image build recipe. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: bdcom-wap2100: Change DTS license to GPL-2.0-or-later OR MITPetr Štetiar2018-11-291-0/+1
| | | | | | | | Having MIT as alternative is sometimes preferred by upstream maintainers and allows sharing that simple code with other projects. We don't really want multiple DTS versions for the same device. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: ubnt-xw: Change DTS license to GPL-2.0-or-later OR MITPetr Štetiar2018-11-291-1/+1
| | | | | | | | Having MIT as alternative is sometimes preferred by upstream maintainers and allows sharing that simple code with other projects. We don't really want multiple DTS versions for the same device. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ath79: ubnt-bullet-m-xw: Change DTS license to GPL-2.0-or-later OR MITPetr Štetiar2018-11-291-1/+1
| | | | | | | | Having MIT as alternative is sometimes preferred by upstream maintainers and allows sharing that simple code with other projects. We don't really want multiple DTS versions for the same device. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* rules.mk: fix syntax errorJo-Philipp Wich2018-11-291-1/+1
| | | | | | | Fix broken assignment operator added in a previous commit. Fixes db73ec9f51 ("rules.mk: add INSTALL_SUID macro") Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* rules.mk: add INSTALL_SUID macroJo-Philipp Wich2018-11-291-0/+1
| | | | | | This is useful for packages that want to stage SUID executables. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* base-files: fix prerm return value, align with postinst codeTony Ambardar2018-11-291-5/+10
| | | | | | | | | | | | | | | The return value of a package prerm script is discarded and not returned correctly by default_prerm(). This allows other operations like service shutdown to "leak" their return value, prompting workarounds like commit 48cfc826 which do not address the root cause. Preserve a package prerm script return value for use by default_prerm(), sharing the corresponding code from default_postinst() for consistency. Also use consistent code for handling of /etc/init.d/ scripts. Run Tested on: LEDE 17.01.4 running ar71xx. Signed-off-by: Tony Ambardar <itugrok@yahoo.com>
* ramips: fix MTD EEPROM offset for TL-WR840N v5Felix Fietkau2018-11-291-1/+1
| | | | | | | The previous offset was invalid and pointed to the end of the partition, which was causing issues with mt76 Signed-off-by: Felix Fietkau <nbd@nbd.name>
* sdk: find kernel modules when KDIR is a symlinkKarl Vogel2018-11-291-1/+1
| | | | | | | | | | | The find statement would not return any results if the KDIR_BASE pointed to a symlink. Ran into this issue due to a custom Kernel/Prepare that was installing a symlink to the kernel directory. The extra slash at the end fixes this scenario and does no harm for targets that have a proper KDIR. Signed-off-by: Karl Vogel <karl.vogel@gmail.com>
* ramips: bdcom-wap2100: Enable mt7610e 5GHz radioPetr Štetiar2018-11-282-1/+13
| | | | | | | | | | | | The 5GHz radio of this device uses an mt7610e PCI-E chip, which has been recently started to be supported. mt76x0e 0000:01:00.0: card - bus=0x1, slot = 0x0 irq=4 mt76x0e 0000:01:00.0: ASIC revision: 76100002 mt76x0e 0000:01:00.0: Firmware Version: 0.1.00 mt76x0e 0000:01:00.0: EEPROM ver:01 fae:00 Signed-off-by: Petr Štetiar <ynezz@true.cz>
* ramips: bdcom-wap2100: Set firmware partition format to denx,uimagePetr Štetiar2018-11-281-0/+1
| | | | | | | | | | | Specify firmware partition format to denx,uimage in compatible DTS property. 2 uimage-fw partitions found on MTD device firmware Creating 2 MTD partitions on "firmware": 0x000000000000-0x00000017f72b : "kernel" 0x00000017f72b-0x000000f70000 : "rootfs" Signed-off-by: Petr Štetiar <ynezz@true.cz>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-08 02:53:06 +0000