aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/mvebu/files/arch/arm
Commit message (Collapse)AuthorAgeFilesLines
* mvebu: add reset delays of PHYs for Fortinet FortiGate 50EINAGAKI Hiroshi2023-09-161-0/+4
| | | | | | | | | | | Add reset-(de)assert-us to ethernet PHYs on Fortinet FortiGate 50E to solve instability after HW resetting of PHYs. (ex.: restarting "network" service, etc...) Fixes: #13391 Fixes: 102dc5a62506 ("mvebu: add support for Fortinet FortiGate 50E") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> (cherry picked from commit 5c65224d8f5787f6bdfaec9547637f1f2f46354f)
* mvebu: use PHY LED trigger for speed LEDs on FortiGate 50EINAGAKI Hiroshi2023-05-181-0/+12
| | | | | | | | | | | | | Use <mdio>:<addr>:<speed> trigger instead of netdev(link) trigger for Fortinet FortiGate 50E, to indicate link speed on the each phys. 1000 Mbps: Green 100 Mbps : Amber 10 Mbps : (turn off) Fixes: 102dc5a62506 ("mvebu: add support for Fortinet FortiGate 50E") Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: add support for Fortinet FortiGate 50EINAGAKI Hiroshi2023-03-081-0/+491
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fortinet FortiGate 50E (FG-50E) is a UTM, based on Armada 385 (88F6820). Specification: - SoC : Marvell Armada 385 88F6820 - RAM : DDR3 2 GiB (4x Micron MT41K512M8DA-107, "D9SGQ") - Flash : SPI-NOR 128 MiB (Macronix MX66L1G45GMI-10G) - Ethernet : 7x 10/100/1000 Mbps - LAN 1-5 : Marvell 88E6176 - WAN 1, 2 : Marvell 88E1512 (2x) - LEDs/Keys : 18x/1x - UART : "CONSOLE" port (RJ-45, RS-232C level) - port : ttyS0 - settings : 9600bps 8n1 - assignment : 1:NC , 2:NC , 3:TXD, 4:GND, 5:GND, 6:RXD, 7:NC , 8:NC - note : compatible with Cisco console cable - HW Monitoring: nuvoTon NCT7802Y - Power : 12 VDC, 2 A - plug : Molex 5557-02R Flash instruction using initramfs image: 1. Power on FG-50E and interrupt to show bootmenu 2. Call "[R]: Review TFTP parameters.", check TFTP parameters and connect computer to "Image download port" in the parameters 3. Prepare TFTP server with the parameters obtained above 4. Rename OpenWrt initramfs image to "image.out" and put to TFTP directory 5. Call "[T]: Initiate TFTP firmware transfer." to download initramfs image from TFTP server 6. Type "r" key when the following message is showed, to boot initramfs image without flashing to spi-nor flash "Save as Default firmware/Backup firmware/Run image without saving:[D/B/R]?" 7. On initramfs image, backup mtd if needed minimum: - "firmware-info" - "kernel" - "rootfs" 7. On initramfs image, upload sysupgrade image to the device and perform sysupgrade 8. Wait ~200 seconds to complete flashing and rebooting. If the device is booted with stock firmware, login to bootmenu and call "[B]: Boot with backup firmware and set as default." to set the first OS image as default and boot it. Notes: - All "SPEED" LEDs(Green/Amber) of LAN and 1000M "SPEED" LEDs(Green) of WAN1/2 are connected to GPIO expander. There is no way to indicate link speed of networking device on Linux Kernel/OpenWrt, so those LEDs cannot be handled like stock firmware. On OpenWrt, use netdev(link) trigger instead. - Both colors of Bi-color LEDs on the front panel cannot be turned on at the same time. - "PWR" and "Logo" LEDs are connected to power source directly. - The following partitions are added for OpenWrt. These partitions are contained in "uboot" partition (0x0-0x1fffff) on stock firmware. - "firmware-info" - "dtb" - "u-boot-env" - "board-info" Image header for bootmenu tftp: 0x0 - 0xf : ? 0x10 - 0x2f : Image Name 0x30 - 0x17f: ? 0x180 - 0x183: Kernel Offset* 0x184 - 0x187: Kernel Length* 0x188 - 0x18b: RootFS Offset (ext2)* 0x18c - 0x18f: RootFS Length (ext2)* 0x190 - 0x193: DTB Offset 0x194 - 0x197: DTB Length 0x198 - 0x19b: Data Offset (jffs2) 0x19c - 0x19f: Data Length (jffs2) 0x1a0 - 0x1ff: ? *: required for initramfs image MAC addresses: (eth0): 70:4C:A5:xx:xx:7C (board-info, 0xd880 (hex)) WAN 1 : 70:4C:A5:xx:xx:7D WAN 2 : 70:4C:A5:xx:xx:7E LAN 1 : 70:4C:A5:xx:xx:7F LAN 2 : 70:4C:A5:xx:xx:80 LAN 3 : 70:4C:A5:xx:xx:81 LAN 4 : 70:4C:A5:xx:xx:82 LAN 5 : 70:4C:A5:xx:xx:83 Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* mvebu: add support for Buffalo LinkStation LS220DEDaniel González Cabanelas2023-02-261-0/+380
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Buffalo LinkStation LS220DE is a dual bay NAS, based on Marvell Armada 370 Hardware: SoC: Marvell Armada 88F6707 CPU: Cortex-A9 800 MHz, 1 core Flash 1: SPI-NOR 1 MiB (U-Boot) Flash 2: NAND 512 MiB (OS) RAM: DDR3 256 MiB Ethernet: 1x 1GbE USB: 1x 2.0 SATA: 2x 3Gb/s LEDs/Input: 5x / 2x (1x button, 1x slide-switch) Fan: 1x casing Flash instructions, from hard drive: 1. Get access to the "boot" partition at the hard drive where the stock firmware is installed. It can be done with acp-commander or by plugging the hard drive to a computer. 2. Backup the stock uImage: mv /boot/uImage.buffalo /boot/uImage.buffalo.bak 3. Move and rename the Openwrt initramfs image to the boot partition: mv openwrt-initramfs-kernel.bin /boot/uImage.buffalo 4. Power on the Linkstation with the hardrive inside. Now Openwrt will boot, but still not installed. 5. Connect via ssh to OpenWrt: ssh root@192.168.1.1 6. Rename boot files inside boot partition mount -t ext3 /dev/sda1 /mnt mv /mnt/uImage.buffalo /mnt/uImage.buffalo.openwrt.bak mv /mnt/initrd.buffalo /mnt/initrd.buffalo.bak 7. Format ubi partitions at the NAND flash ("kernel_ubi" and "ubi"): ubiformat /dev/mtd0 -y ubidetach -p /dev/mtd1 ubiformat /dev/mtd1 -y 8. Flash the sysupgrade image: sysupgrade -n openwrt-squashfs-sysupgrade.bin 9. Wait until it finish, the device will reboot with OpenWrt installed on the NAND flash. Restore the stock firmware: 1. Take the hard drive used for the installation and restore boot backup files to their original names: mount -t ext3 /dev/sda1 /mnt mv /mnt/uImage.buffalo.bak /mnt/uImage.buffalo mv /mnt/initrd.buffalo.bak /mnt/initrd.buffalo 2. Boot from the hard drive and perform a stock firmware update using the Buffalo utility. The NAND will be restored to the original state. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: add support for ipTIME NAS1dualSungbo Eo2022-01-291-0/+318
| | | | | | | | | | | | | | | | | | | | | | | | ipTIME NAS1dual is a 1-bay NAS, based on Marvell Armada 385 SoC. Specifications: * SoC: 88F6820 * RAM: 2 GiB * Flash: SPI NOR 64 MiB * SATA: 1x 3Gb/s * Ethernet: 2x 1GbE * USB: 1x 3.0 * Fan: 2 speed level * UART: J11 (115200 8N1) * Pinout: [3V3] (TXD) (RXD) (GND) Installation via web interface: 1. Flash **initramfs** image through the stock web interface. 2. Boot into OpenWrt and perform sysupgrade with sysupgrade image. Revert to stock firmware: 1. Perform sysupgrade with stock image. Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* mvebu: cortexa9: Add support for Ctera C200-V2Pawel Dembicki2022-01-151-0/+426
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 2-Bay NAS - maximum two 3.5" Harddisks Hardware: - SoC: Marvell 88F6707-A1 ARMv7 Processor 1,2GHz (ARMADA 370 SoC) - Ram: 1GB (2x Nanya NT5CC512M8DN-D1) - NAND Flash: 256MB (ESMT F59L2G81A-25T) - Lan: 1x GBE (Marvell 88E1318-NNB2) - Storage: 2x SATA HDD 3.5" Slot - USB: 2x USB 3.0 port (Renesas uPD720202) - Console: Internal J3 connector (1: Vcc, 2: Rx, 3: Tx, 4: GND) - LEDs: 13x GPIO controlled - Buttons: 2x GPIO controlled Known issues: - Buzzer is unused due lack of proper driver - USB1/2 usbport ledtrigger won't work (through DT) - Renesas uPD720202 requires firmware file. It's possible to find non-free binary. Please look for 'UPDATE.mem' file and put in into '/lib/firmware/renesas_usb_fw.mem' file. Installation: - Apply factory initramfs image via stock web-gui. - Do sysupgrade to make installation complete. Back to stock: - OpenWrt rootfs partition use unused space after stock firmware. - Full revert is possible. - Login via ssh and run: ## ctera_c200-v2_back_to_factory start ## . /lib/functions.sh part=$(find_mtd_part "active_bank") active_bank=$(strings "$part" | grep bank) if [ "$active_bank" = "bank1" ]; then echo "bank2" > /tmp/change_bank else echo "bank1" > /tmp/change_bank fi mtd write /tmp/change_bank active_bank reboot ## ctera_c200-v2_back_to_factory end ## Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> (put back-to-stock script into commit message, removed dup. SUBPAGESIZE var, added 01_leds for non-working dt-usb-port trigger) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* mvebu: LS421DE: improve pin configurationDaniel González Cabanelas2021-05-011-3/+12
| | | | | | | | | | | | | The CLK125 output pin at the ethernet PHY is connected via capacitor to GND and nowhere else. Disable it. Also tune the LED masks. The MPP56 and MPP60 pins at the SoC are conected to the μPD720202 USB3.0 chip: - MPP56: wired to PCIe CLKREQ# (out) - MPP60: wired to PCIe RESET# (in) Configure the pcie pinmux for these pins. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: venom resize kernel to 6MBTad Davanzo2021-03-191-4/+4
| | | | | | | | | | | | | | | | | | | | | | | venom has a 3MB kernel partition as specified by the DTS. 3MB is not sufficient for building with many kernel modules or newer kernel versions. venom uboot however as set from factory will load up to 6MB. This can be observed by looking a uboot log: NAND read: device 0 offset 0x900000, size 0x600000 6291456 bytes read: OK and from uboot environment variables: $ fw_printenv | grep "priKernSize"; priKernSize=0x0600000 Resize the root partitions from 120MB to 117MB to let kernel expand into it another 3MB. And set kernel target size to 6MB. Lastly set the kernel-size-migration compatibility version on venom to prevent sysupgrading without first reinstalling from a factory image. Signed-off-by: Tad Davanzo <tad@spotco.us>
* mvebu: LS421DE: make cosmetics changes in dts fileDaniel González Cabanelas2021-03-131-5/+11
| | | | | | | | | Make some cosmetic changes in the Buffalo LinkStation LS421DE NAS: - Delete pointless #xxx-cells - bootargs: replace earlyprintk with earlycon and remove unneeded args. - Separate pinmux nodes with empty lines. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: LS421DE: fix the thermal zonesDaniel González Cabanelas2021-01-301-13/+42
| | | | | | | | | | | | | | | | | | | | | | The thermal zones kernel documentation is misleading, we cannot use more than one sensor in a thermal zone node. Furthermore the drivetemp driver for some reason it only catches one sensor from the hard drives array (the first available). In the Buffalo Linkstation LS421DE board there is also a sensor at the ethernet phy chip that can also be monitored. Very useful to stop the fan when there are no hard drives in the bays. (It might be also possible to add the CPU sensor, but it requires kernel patching for registering the sensor via device tree, using the function: devm_thermal_zone_of_sensor_register) Fix the thermal zones to use only one sensor per node and add the ethernet phy sensor. Also adjust the hdd temperatures to be more conservative for a mechanical hard drive. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: LS421DE: use the RTC as a wakeup sourceDaniel González Cabanelas2020-12-221-0/+1
| | | | | | | | | | | | | | | | | | | The Buffalo Linkstation LS421DE comes with a Ricoh RS5C372A real time clock. This RTC has the INTRA pin connected to the power management circuit, allowing to wake up the device from the power off state when an alarm is scheduled. Add the "wakeup-source" property in the RTC dts node to allow the use of the alarm. Example of use, the device is powered off and it comes to life after 5 minutes: echo $(expr $(date '+%s') + 60 * 5) > /sys/class/rtc/rtc0/wakealarm poweroff This feature isn't available in the stock firmware. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: LS421DE: fix low performance issueDaniel González Cabanelas2020-12-221-0/+4
| | | | | | | | | | The Buffalo Linkstation LS421DE isn't able to enable the Level 2 cache (AKA Aurora cache). As of result of this, the throughput is about half of the expected, e.g when doing network data transfers. Fix it by adding the broken-idle property in the coherency fabric node. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* treewide: remove default-state off for LEDsAdrian Schmutzler2020-11-161-2/+0
| | | | | | | | | default-state = "off" is default for LEDs, no need to specify it explicitly. https://www.kernel.org/doc/Documentation/devicetree/bindings/leds/common.yaml Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: LS421DE: improve the HDD ledsDaniel González Cabanelas2020-11-161-2/+2
| | | | | | | Improve the HDD LEDs used for disk activity: - Use the trigger activity per ata channel Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* target: update SPDX license namesAdrian Schmutzler2020-09-221-1/+1
| | | | | | | SPDX moved from GPL-2.0 to GPL-2.0-only and from GPL-2.0+ to GPL-2.0-or-later. Reflect that in the SPDX license headers. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: LS421DE: add linkstation poweroff driverDaniel González Cabanelas2020-08-281-13/+0
| | | | | | | | | | | Compile the Linkstation poweroff module for the Buffalo LS421DE. Without this driver the device remains forever halted if a power off command is executed. The driver will also allow to use the WoL feature, which wasn't availabe in the stock firmware. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: LS421DE: use automatic fan control with thermal zonesDaniel González Cabanelas2020-07-041-1/+64
| | | | | | | | | | | | | | | | The Buffalo Linkstation LS421DE has a chassis fan for cooling two internal hard drives. Currently there is no control over this fan, running always at fixed medium speed. With the recent jump to the kernel 5.4, now we can monitor the hard drive temperature and control the fan with thermal zones. Install the kmod-hwmon-drivetemp module and wire up a thermal zone on the dts file to allow automatic fan control by the kernel. Tested succesfully using a single Crucial BX500 SSD drive. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: LS421DE: dts file improvementsDaniel González Cabanelas2020-06-271-31/+22
| | | | | | | | | | | | - Delete useless HDD presence inputs: they aren't buttons, and probably they are outputs in the stock firmware. - Change the Function Button keycode: the current one isn't mapped by the kernel module. - Use the recommended property names for the ethernet stuff. - Add missing i2c pinmux. - Minor cosmetic changes. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com>
* mvebu: consolidate DTS filesAdrian Schmutzler2020-06-232-0/+573
| | | | | | | | | | | | The DTS files in files-4.19 and files-5.4 are exactly identical except for one file (armada-3720-uDPU.dts), which is only present for 4.19, as it has been upstreamed before 5.4. Since there is no point in maintaining all these identical files twice, this patch moves them to the "files" directory, only keeping the named exception to files-4.19. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: move files to files-4.9 and files-4.4 folderHauke Mehrtens2018-02-132-568/+0
| | | | | | | | This is needed to prevent copying it into kernel 4.14. These device tree files are already integrated into kernel 4.14 and we would like to use the upstream versions only. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: wrt3200acm enable SDIO interfaceHenryk Heisig2017-03-111-0/+10
| | | | | | add mwifiex-sdio package to wrt3200acm Signed-off-by: Henryk Heisig <hyniu@o2.pl>
* mvebu: add default sata triggerAnsuel Smith2017-03-082-0/+2
| | | | | | | | | | | Change dts file to add default sata trigger to sata led. Backport upstream accepted patch to add sata trigger to device tree source files already upstreamed. Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com> [backport upstream accepted patch] Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: several fixes for Linksys WRT3200ACMÁlvaro Fernández Rojas2017-01-131-44/+40
| | | | | | | | - Fix WLAN LEDs definition. - Fix USB pinctrl definition. - Remove SDHCI definition. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mvebu: Fix up some leds on this seriesKabuli Chana2017-01-101-1/+1
| | | | | | correct ports, fix power led on rango, tested mamba,shelby,rango Signed-off-by: Kabuli Chana <newtownBuild@gmail.com>
* mvebu: revert remove of mvsw61xx device tree nodesMathias Kresin2016-11-131-0/+13
| | | | | | | | | | The marvell,88e6352 and marvell,88e6172 compatible strings are used in target/linux/generic/files/drivers/net/phy/mvsw61xx.c. No idea why grep missed them when I searched for them. Thanks to Syrone Wong for noticing and reporting my mistake. Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: dts: fix dtc compiler warningsMathias Kresin2016-11-121-13/+0
| | | | | | | | | | | Fixes invalid device tree parameters. Drop the mvsw61xx node used in mvebu device tree source files. It looks like some kind of ethernet switch cargo cult. Neither the marvell,88e6352 nor the marvell,88e6172 compatible strings can be found in any LEDE file or in the kernel sources. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mvebu: add support for the Linksys WRT3200ACM (Rango)Imre Kaloz2016-10-241-0/+446
| | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* mvebu: replace ClearFog dts files with patches from upstreamJonas Gorski2016-09-262-571/+0
| | | | | | | | Make the dts file match with what is upstream, to ensure it has the latest changes and switching to newer kernels is easier. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com> Acked-by: Felix Fietkau <nbd@nbd.name>
* mvebu: add SolidRun ClearFog A1 supportLuka Perkov2016-02-172-0/+571
| | | | | | Signed-off-by: Andrej Vlasic <andrej.vlasic@sartura.hr> SVN-Revision: 48736
* mvebu: add support for 4.1 and switch overImre Kaloz2015-12-104-1147/+0
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 47818
* mvebu: add support for the Linksys WRT1900ACS (Shelby)Imre Kaloz2015-10-081-0/+320
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 47164
* mvebu: fix cobra chainmaskImre Kaloz2015-08-211-2/+2
| | | | | | | | Thanks Sebastian for spotting it. Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 46697
* mvebu: fix gpio config on the WRT1200ACImre Kaloz2015-07-311-3/+3
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 46527
* mvebu: add support for the Linksys Caiman and CobraImre Kaloz2015-04-163-0/+941
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 45456
* mvebu: migrate mamba support to the upstreamed codeImre Kaloz2015-04-121-429/+0
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 45400
* mvebu: update mamba dtsImre Kaloz2015-03-231-0/+88
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44949
* mvebu: update mamba dtsImre Kaloz2015-01-251-70/+71
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 44128
* mvebu: add the new tlc59116 driver and migrate the Mamba to itImre Kaloz2015-01-151-2/+53
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 43975
* now that the driver knows it, use the 88e6172's switch type in the mamba dtsImre Kaloz2015-01-121-1/+1
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 43945
* mvsw6171: rename to 'mvsw61xx'Luka Perkov2015-01-111-1/+1
| | | | | | | | | In preparation for properly supporting switches beyond the 88E6171. Signed-off-by: Claudio Leite <leitec@staticky.com> SVN-Revision: 43935
* enable swconfig and the mvsw6171 driverImre Kaloz2015-01-051-4/+11
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 43854
* add tmp421 to the device tree instead of relying on autodetectImre Kaloz2015-01-041-0/+5
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 43825
* update wrt1900ac dtsImre Kaloz2014-07-131-3/+2
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41629
* fix the WPS button's GPIO number on the mambaImre Kaloz2014-06-291-1/+1
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41392
* update mamba dtsImre Kaloz2014-06-291-9/+8
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41379
* update mamba dtsImre Kaloz2014-06-201-14/+33
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41292
* define the power led for the WRT1900ACImre Kaloz2014-06-201-0/+18
| | | | | | Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41288
* preliminary support for the WRT1900AC (work in progress)Imre Kaloz2014-06-171-0/+242
SVN-Revision: 41232
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-23 23:02:31 +0000