aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
...
* ramips: fix HiWiFi HC5962 switch configurationDENG Qingfang2020-01-181-1/+4
| | | | | | | | HC5962 has only 3 LAN ports, switch port 0 is unused Signed-off-by: DENG Qingfang <dengqf6@mail2.sysu.edu.cn> (backported from commit 68f49df31507454f86b72a5c1e250505176baed7) Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: add kmod-mt7615e to Xiaomi Mi Router 3 Pro imagesOzgur Can Leonard2020-01-182-3/+5
| | | | | | | Now that the mt76/mt7615e driver is in Openwrt, might as well use it. Signed-off-by: Ozgur Can Leonard <ozgurcan@gmail.com> (cherry picked from commit d7c082ba4f7de97b3708d1f4a064954ffc774778)
* ar71xx/mikrotik: use ath10k-ct-smallbuffers for 64 MiB devicesThomas Nixon2020-01-181-1/+1
| | | | | | | | | | | This image is only needed on one device (wAP AC); since this target is going to be removed anyway it doesn't make sense to add an extra "low RAM" image. Fixes OOM issues on RouterBoard wAP AC. Signed-off-by: Thomas Nixon <tom@tomn.co.uk> (cherry picked from commit 788c8485eb5b71ef7e7b2a2d3077772e526e9746)
* ramips: fix wps leds/btn for TP-Link TL-WA801ND v5Jan Alexander2020-01-171-4/+16
| | | | | | | | | | | - fix color and active mode for existing wps led - add green wps led - add wps button Signed-off-by: Jan Alexander <jan@nalx.net> [wrap line] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 26105974e7f9758cd4bc443ce0322983f818acd5)
* ramips: mt7621: disable images for gehua_ghl-r-001Petr Štetiar2020-01-141-0/+1
| | | | | | | | | | | This device OOPs during the boot due to broken flash. It can be probably fixed with `broken-flash-reset` once ramips is on 4.19 kernel. So disable images for this device until its fixed. Ref: FS#2695, PR#2483 Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 28080d54d217fb4ab112e079f69462fee695dbf8)
* ramips: fix leds for TP-Link Archer C20 v4Maxim Anisimov2020-01-122-2/+3
| | | | | | | | | | | - add "gpio" group for wan_orange led - use tpt triggers for wifi led indication - add wifi 5 GHz led support Signed-off-by: Maxim Anisimov <maxim.anisimov.ua@gmail.com> [slight commit message adjustment, backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 3a538db60abfc50b47ce1774f66d489700a50c00)
* ath79: add SUPPORTED_DEVICES for TP-Link TL-WR841N/ND v9 to v12Adrian Schmutzler2020-01-081-0/+4
| | | | | | | In ar71xx, v10 and v12 did not have separate board_name. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 7ed643d2052381bdd0e9680ca964eb87700cbc5e)
* ath79: add support for TP-Link TL-WR841N/ND v12Adrian Schmutzler2020-01-086-23/+48
| | | | | | | | | | | | | | | | | | | | | | | | This router has the same hardware as TP-LINK TL-WR841N/ND v11 (same FCC ID, same TFTP image name...). Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed ip address 192.168.0.66 2. Download *-factory.bin image and rename it to wr841nv11_tp_recovery.bin (it's really v11, not v12) 3. Start a tftp server with the image file in its root directory 4. Turn off the router 5. Press and hold Reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 8b76c6695b9274e3c12fdf80bcad7dc0c7202585)
* ath79: add support for TP-Link TL-WR841N/ND v10Adrian Schmutzler2020-01-085-3/+26
| | | | | | | | | | | | | | | | | | | | | | | | The TL-WR841N/ND v10 is mostly identical to the v9. Apart from some minor changes, it contains a newer revision of the QCA9533 SoC and the CPU clock is significantly higher. Flash instruction (WebUI): Download *-factory.bin image and upload it via the firmwary upgrade function of the stock firmware WebUI. Flash instruction (TFTP): 1. Set PC to fixed ip address 192.168.0.66 2. Download *-factory.bin image and rename it to wr841nv10_tp_recovery.bin 3. Start a tftp server with the image file in its root directory 4. Turn off the router 5. Press and hold Reset button 6. Turn on router with the reset button pressed and wait ~15 seconds 7. Release the reset button and after a short time the firmware should be transferred from the tftp server 8. Wait ~30 second to complete recovery. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 4254193c1dc27e18baeb7488ac7fd4ce1afc5723)
* ath79: add support for the TP-LINK CPE220 V3Andrew Cameron2020-01-087-125/+192
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds support for a popular low-cost 2.4GHz N based AP Specifications: SoC: Qualcomm Atheros QCA9533 (650MHz) RAM: 64MB Storage: 8 MB SPI NOR Wireless: 2.4GHz N based built into SoC 2x2 Ethernet: 2x 100/10 Mbps, integrated into SoC Installation: 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 This also applies some minor changes to the common DTSI: - use &wmac for label-mac-device, as this one is actually set up in common DTSI - move &eth0 to parent DTSI - fix several leading spaces, added/removed newlines Signed-off-by: Andrew Cameron <apcameron@softhome.net> [DTS style fixes/improvements, updated commit message/title, backport to 19.07] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: Fix sysupgrade for Xiaomi mir3gHauke Mehrtens2020-01-061-3/+4
| | | | | | | | | | | | | | | | | | | This mostly reverts the original commit e9929ebeeaef ("ramips: Fix sysupgrade for Xiaomi mir3g") and replaces it with setting the BOARD_NAME to the old value. This way the folder in the tar will be named sysupgrade-mir3g and not sysupgrade-xiaomi_mir3g and the sysupgrade in OpenWrt 18.06 can find it. Without this change sysupgrade from 18.06 to 19.07 is only possible with the -F option. I tested the following sysupgrades successfully without -F 18.06 -> 19.07 19.07 -> master master -> 19.07 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* x86: fix missing led variable warning during bootPetr Štetiar2020-01-061-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> (cherry picked from commit 5816caad26ae294f0adb4ed07ed53dcba7277c33)
* ramips: Fix sysupgrade for Xiaomi mir3gHauke Mehrtens2020-01-051-3/+3
| | | | | | | | | | | | | | | | | Without this change sysupgrade from 18.06 to 19.07 is only possible with the -F option. In OpenWrt 18.06 the nand_do_platform_check() function is called with the board name mir3g only, if the tar does not use mir3g it will fail. OpenWrt 19.07 and later support the metadata with the supported_devices attribute to allow renaming. Do the renaming of the target between 19.07 and master like it is done for some other boards. I tested the following sysupgrades successfully without -F 18.06 -> 19.07 19.07 -> master master -> 19.07 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: remove duplicate dts nodes of MediaTek LinkIt Smart 7688Jack Chen2020-01-051-4/+0
| | | | | | | | There are two identical wmac nodes in the dts file of MediaTek LinkIt Smart 7688, so delete one of them. Signed-off-by: Jack Chen <redchenjs@live.com> (cherry picked from commit 4be271a4867dcf57a122eeb7b42407e7a506915e)
* sunxi: Turn on CONFIG_PINCTRL_SUN4I_A10 for A20Florian Fainelli2020-01-051-1/+1
| | | | | | | | | | | CONFIG_PINCTRL_SUN4I_A10 controls both the A10 and the A20 enablong of the pinctrl driver, this is necessary since upstream commit 5d8d349618a9464714c07414c5888bfd9416638f ("pinctrl: sunxi: add A20 support to A10 driver") which has been included in v4.13 and onwards. Fixes: ad2b3bf310f7 ("sunxi: Add support for kernel 4.14") Signed-off-by: Florian Fainelli <f.fainelli@gmail.com> (cherry picked from commit 32e4eaef1b4c2a7fa44787813fdf715b2ba500d9)
* kernel: bump 4.14 to 4.14.162Hauke Mehrtens2020-01-049-23/+23
| | | | | | | | | Refreshed all patches. Compile-tested on: ipq40xx, ramips Runtime-tested on: ipq40xx Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.161Hauke Mehrtens2020-01-0431-132/+132
| | | | | | | | | Refreshed all patches. Compile-tested on: ipq40xx, ramips Runtime-tested on: ipq40xx Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: fix Archer C20i wireless MAC addressDavid Bauer2020-01-031-0/+3
| | | | | | | | | | | The TP-Link Archer C20i previously had a generic Ralink MAC address set for both radios, as the caldata does only contain a generic MAC address. Set the MAC address from the vendor firmware for both radios to assign unique MAC addresses to every device. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 3b013dcdf8d8aa0e3601e3aac30342318025e32a)
* ramips: fix Archer C2 v1 5GHz MAC addressDavid Bauer2020-01-031-0/+2
| | | | | | | | | | | | The TP-Link Archer C2 v1 previously had a generic Ralink MAC address set for the 5GHz radio (MT7610), as the caldata does only contain a generic MAC address. Set the MAC address from the vendor firmware for the 5GHz radio to assign unique MAC addresses to every device. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit dcc923a4c45b48fcbef4f3964f74fbcaabad335e)
* ramips: add system LED indicators for TP-Link C20iDavid Bauer2020-01-031-1/+8
| | | | | | | | Use the WPS LED to indicate system status like it is done for the TP-Link Archer C2 v1 and many other boards. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit a272fafc9c507820cc62aa12464588bac45f250a)
* ramips: convert TP-Link MT7620 boards to tpt triggerDavid Bauer2020-01-036-5/+7
| | | | | | | | | | | | | This converts all MediaTek MT7620 boards from TP-Link to use the now supported WiFi throughput LED trigger. This way, the LED state now covers all VAPs regardless of their name. Also align all single-WiFi LEDs to represent the state of the 2.4GHz radio. This was not always the case previously, as later-added support for the MT7610 altered the phy probing order. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 1e7c6381f0058e49caab8de54eaad4862732f95d)
* ramips: fix inverted reset button for Ravpower WD03Moritz Warning2020-01-031-1/+1
| | | | | | | The button events "pressed" and "released" were switched. Tested with v18.06.4. Signed-off-by: Moritz Warning <moritzwarning@web.de> (cherry picked from commit 3e1325b219fced91f01d5594503f61d326a93b90)
* ramips: add LED trigger for TL-WR902AC v3 WAN LEDDavid Bauer2019-12-301-0/+1
| | | | | | | | | | | | This adds an LED trigger for the WAN LED on top of the TP-Link TL-WR902AC v3. Currently, only the LED on the port itself shows the link state, while the LED on top of the device stays dark. The WAN port of the device is a hybrid LAN/WAN one, hence why the LED at the port was labled LAN. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit c48b571ad708b9f66efb0c2942291c2d8f1d7780)
* ramips: remove bogus ralink,mtd-eeprom with offset 0x4Adrian Schmutzler2019-12-286-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Several devices in mt76x8 subtarget use the following line to set up wmac in their DTS(I) files: ralink,mtd-eeprom = <&factory 0x4> This is strange for several reasons: - They should use mediatek,mtd-eeprom on this SOC - The caldata is supposed to start at 0x0 - The parent DTSI mt7628an.dtsi specifies mediatek,mtd-eeprom anyway, starting from 0x0 - The offset coincides with the default location of the MAC address in caldata Based on the comment in b28e94d4bfa1 ("ramips: MiWiFi Nano fixes"), it looks like the author for this device wanted to actually use mtd-mac-address instead of ralink,mtd-eeprom. A check on the same device revealed that actually the MAC address start at offset 4 there, so the correct caldata offset is 0x0. Based on these findings, and the fact that the expected location on this SOC is 0x0, we remove the "ralink,mtd-eeprom = <&factory 0x4>" statement from all devices in ramips (being only mt7628an anyway). Thanks to Sungbo Eo for finding and researching this. Reported-by: Sungbo Eo <mans0n@gorani.run> Fixes: b28e94d4bfa1 ("ramips: MiWiFi Nano fixes") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 09d38a3bc328d122b0d84fcf6bb53d2bce7373b6)
* ipq40xx: use ath10k-ct-smallbuffers for 128 MiB devicesPaul Fertser2019-12-261-1/+3
| | | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com> (cherry picked from commit 0b7d779dcfc57507ab1d06ce6f1052d25e9de017)
* kernel: bump 4.14 to 4.14.160Hauke Mehrtens2019-12-2510-16/+16
| | | | | | | | | Refreshed all patches. Compile-tested on: ipq40xx, ath79 Runtime-tested on: ipq40xx Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.159Koen Vandeputte2019-12-2450-279/+151
| | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 302-0002-dmaengine-dw-implement-per-channel-protection-contro.patch Fixes: - CVE-2019-19332 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: use ath10k-ct-smallbuffers for 64 MiB devicesPaul Fertser2019-12-243-14/+14
| | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* lantiq: fix phys ledAleksander Jan Bajkowski2019-12-231-2/+2
| | | | | | | | | led2l and led2h value is incorrectly set by led3l and led3h. Bug was introduced in commit: 863e79f8d5544a8a884375d7e867f350fddca9b9 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Fixes: 863e79f8d554 ("lantiq: add support for kernel 4.9") (cherry picked from commit 692390225d76de8f2daf582454e74942b82d090a)
* ar71xx: fix MAC address setup for TL-WDR4300 boardSungbo Eo2019-12-212-1/+5
| | | | | | | | | | | | | | | | | | The current ethernet MAC address setup of TL-WDR4300 board is different from the setup of stock firmware: OpenWrt: lan = label_mac -2, wan = label_mac -2 stock: lan = label_mac, wan = label_mac +1 This patch applies to all devices using TL-WDR4300 board: TL-WDR3600 v1 TL-WDR4300 v1 TL-WDR4300 v1 (IL) TL-WDR4310 v1 Mercury MW4530R v1 Signed-off-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit 9b02d32e34df2bb8821ec6f08f525bee22d0d1ba)
* ath79: fix MAC address setup for TP-Link TL-WDR3600/TL-WDR4300Sungbo Eo2019-12-212-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | The current ethernet MAC address setup of TL-WDR4300 board is different from the setup of stock firmware: OpenWrt: lan = label_mac -2, wan = label_mac -2 stock: lan = label_mac, wan = label_mac +1 The full address assignment is as follows: LAN label WAN label + 1 5G label 2G label - 1 This patch changes all devices using TL-WDR4300 board: TL-WDR3600 v1 (checked on device) TL-WDR4300 v1 (checked on device) TL-WDR4300 v1 (IL) Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rephrase/extend commit title/message, backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit a4260eaab7744c8e3f1f7a62a61aab5e3b562342)
* ramips: fix USB LED for Belkin F9K1109v1Sungbo Eo2019-12-201-1/+1
| | | | | | | | | | | | | | | Device support for Belkin F9K1109v1 was added using set_usb_led() although this was removed in 772b27c20736 ("ramips: set F5D8235 v1 usb led trigger via devicetree"). Use ucidef_set_led_usbport() instead. Fixes: f2c83532f92c ("ramips: add support for Belkin F9K1109v1") Signed-off-by: Sungbo Eo <mans0n@gorani.run> [rephrase commit title and message, backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 1f455418ef1ea67fda710e1b86a9e021bb4a2413)
* ath79: migrate LED paths of TL-WDR4300 boardSungbo Eo2019-12-171-1/+4
| | | | | | | | | | | | | | TL-WDR4300 board uses only green LED names in DTSI. This patch adds migration for them. The actual LED colors on the devices have been reported to vary across subrevisions (v1.x). Despite, the USB LEDs on the back might have different color than the other LEDs on the front. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [extended commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 01d39cd18c4035e362f179548cd2c051aac03042)
* malta: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit e964338110526b3692847769343816cd2f853d18)
* sunxi: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 2105354968ed9698709d220ec446b6d9c27da3a5)
* layerscape: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-172-4/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 414d027ae8ac05ec9aa06bc50afd5458c2da02fc)
* kirkwood: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit 411e824ec371a322b975e90af5a1f32760a61720)
* at91: disable legacy PTYs and virtual terminalsDaniel Golle2019-12-171-6/+0
| | | | | | | | | | Enabling legacy PTYs causes problems with procd-hotplug. And as this is a headless target, no need to have virtual terminals. Remove corresponding kernel config options, they are disabled in generic kernel config. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit c1db4d9c5655e3c74ffdbb6a6a3367269f65c55f)
* mpc85xx: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-171-2/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit d0d7f5d9e49b8632f372c92e0339895fa10904f9)
* uml: remove CONFIG_LEGACY_PTY from kernel configDaniel Golle2019-12-172-4/+0
| | | | | | | Having legacy PTYs enabled causes problems with procd-hotplug. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit dcf48fda054c4bbc52f6106250a7e06ab8f5cbdd)
* oxnas: disable legacy PTYs and virtual terminalsDaniel Golle2019-12-171-6/+0
| | | | | | | | | | Enabling legacy PTYs causes problems with procd-hotplug. And as this is a headless target, no need to have virtual terminals. Remove corresponding kernel config options, they are disabled in generic kernel config. Signed-off-by: Daniel Golle <daniel@makrotopia.org> (cherry picked from commit c881769a558b38ddd5977a50b67cd32c6d3f7d5e)
* lantiq: remove redundant WiFi LED on FRITZ!Box 7320Manuel Kock2019-12-141-3/+0
| | | | | | | | | | The led wireless trigger is already set correctly to phy0tpt through the alias in the device tree. Signed-off-by: Manuel Kock <github.web@manu.li> [rephrased commit title] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 509894cffb7ec24ac21a381bed3c035efce42aeb)
* mpc85xx: add support for Enterasys WS-AP3710iDavid Bauer2019-12-147-0/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- SoC: NXP P1020 (2x e500 @ 800MHz) RAM: 256M DDR3 (Micron) FLASH: 32M NOR (Spansion S29GL128S) BTN: 1x Reset WiFi: 1x Atheros AR9590 2.4 bgn 3x3 2x Atheros AR9590 5.0 an 3x3 ETH: 1x Gigabit Ethernet (Atheros AR8033) LED: System (green/red) - Radio{0,1} (green) LAN (connected to PHY) - GE blue - FE green Serial is a Cisco-compatible RJ45 next to the ethernet port. 115200-N-8 are the settings for OS and U-Boot. Installation ------------ 1. Grab the OpenWrt initramfs, rename it to 01C8A8C0.img. Place it in the root directory of a TFTP server and serve it at 192.168.200.200/24. 2. Connect to the serial port and boot the AP. Stop autoboot in U-Boot by pressing Enter when prompted. Credentials are identical to the one in the APs interface. By default it is admin / new2day. 3. Set the bootcmd so the AP can boot OpenWrt by executing $ setenv boot_openwrt "setenv bootargs; cp.b 0xee000000 0x1000000 0x1000000; bootm 0x1000000" $ setenv bootcmd "run boot_openwrt" $ saveenv If you plan on going back to the vendor firmware - the bootcmd for it is stored in the boot_flash variable. 4. Load the initramfs image to RAM and boot by executing $ tftpboot 0x1000000 192.168.200.200:01C8A8C0.img; bootm 5. Make a backup of the "firmware" partition if you ever wish to go back to the vendor firmware. 6. Upload the OpenWrt sysupgrade image via SCP to the devices /tmp folder. 7. Flash OpenWrt using sysupgrade. $ sysupgrade -n /tmp/openwrt-sysupgrade.bin Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 16b01fb1b9c99513c318109bef96a1a3545c57a0)
* ath79: add support for TP-Link TL-WDR4300 v1 (IL)Adrian Schmutzler2019-12-134-0/+21
| | | | | | | | | The TL-WDR4300 v1 sold in Israel has a different TPLINK_HWID. Thanks to Josh4300 for testing on device. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit c642a97aa6b51352a718449cd715b92f94af4a5d)
* ramips: allow JCG_MAXSIZE in kiB in Build/jcg-headerAdrian Schmutzler2019-12-132-2/+4
| | | | | | | | | | | | | | | This allows JCG_MAXSIZE to be specified in kilobytes. This makes this value more consistent and easier comparable with other size variables. This also changes the only occurence of the variable, for Cudy WR1000. This is backported to 19.07 for convenience, as other developers backporting device support might not be aware that JCG_MAXSIZE in kilobytes would not work there. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 0bf4d681d4f2e4bd3c3a61e7fe5dca2a40b1902f)
* brcm47xx: add switch configuration for WNR3500LOlli Asikainen2019-12-111-1/+2
| | | | | | | | | | | | | | | | | | | | | Netgear WNR3500L is an already supported device, but out of the box, the device has no switch configuration and there is no wan. The correct configuration for this specific model is similar to some other models. This simple commit adds the correct switch and the out-of-the-box experience is improved. Experimentally determined: Port 0 => WAN Port 1..4 => LAN Port 5..7 => unused Port 8 => CPU Signed-off-by: Olli Asikainen <olli.asikainen@gmail.com> Tested-by: Fabian Zaremba <fabian@youremail.eu> [added port mapping to commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit deb835849aeb713968aaa48bf046101140ab4825)
* ramips: fix number of LAN Ports for Mikrotik RBM33GMartin Schiller2019-12-111-1/+4
| | | | | | | | | The Mikrotik RBM33G has only 2 LAN ports. Signed-off-by: Martin Schiller <ms@dev.tdt.de> [moved node in 02_network to maintain alphabetic sorting; backport] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 3a55c7935d4efdc86575601cb4aa7bc94e3c5e44)
* ramips: fix switch port order for TP-Link Archer C20iWalter Sonius2019-12-111-1/+1
| | | | | | | | | | | | | | | | | | | Physical port order watched from the backside of the C20i (from left to right) is: Internet / 1 / 2 / 3 / 4 Physical Port Switch port WAN 0 LAN 3 1 LAN 4 2 LAN 1 3 LAN 2 4 (not used) 5 CPU 6 Signed-off-by: Walter Sonius <walterav1984@gmail.com> [commit message/title improvements; backport to 19.07] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit a065cd29bf2dfd1ce1f07becd65aef96cec658e7)
* kernel: bump 4.14 to 4.14.158Koen Vandeputte2019-12-1020-40/+40
| | | | | | | | | | | | Refreshed all patches. Altered patches: - 400-mtd-add-rootfs-split-support.patch Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* generic ar8xxx: increase VLAN table for AR83x7David Bauer2019-11-303-9/+13
| | | | | | | | | | | | | The Atheros AR8327 and AR8337 have (according to their datasheet) a VLAN table with a maximum of 4096 entries. Currently, there's a hard limit of 128 VLANs, which is the same as for most other Atheros switches. Increase this limit only for the AR83x7 series and modify some shared functions to allow them to work with a variable max VLAN count. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 3f79aaa2979793c054eae2c8b4058c8c7fccdbe7)
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-30 04:36:43 +0000