aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/dts
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: make dts files and kernel config kernel version specificMathias Kresin2018-02-2074-11286/+0
| | | | | | | | | | Move the devicetree source files to a kernel specific directory in preparation of adding kernel 4.14 support. Rename the subtarget kernel config files to match a specific kernel version. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: rename gphy firmwareMathias Kresin2018-02-2014-22/+22
| | | | | | | | | | Rename the gphy firmware to match the name requested by kernel 4.14 and update the devicetree source files to use the new name. Update the u-boot lantiq Makefile to be compatible with the new names as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix dts compatible stringThomas Nixon2017-12-292-2/+2
| | | | | | | | | | This was broken in 7bab49fd ("lantiq: add compatible strings to dts files"), causing for the dm200 garbled serial output during boot, and likely other issues. Signed-off-by: Thomas Nixon <tom@tomn.co.uk> [fix the compat string of the P2601HNFX as well] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add missing model namesMathias Kresin2017-12-161-0/+1
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: remove the former board name from device tree modelMathias Kresin2017-12-1659-59/+59
| | | | | | | Remove the former used board name from the device model property and use the model name as it is. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: drop SoC name from eval boards compatible stringMathias Kresin2017-12-1611-11/+11
| | | | | | Keep it in the same format as used for the other eval boards. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add compatible strings to dts filesMathias Kresin2017-12-1653-0/+59
| | | | | | The compatible string is mandetory for devicetree source file. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: ARV752DPW22: fix wireless mac addressMathias Kresin2017-10-181-0/+1
| | | | | | | | | | The ARV752DPW22 has the same generic mac address in the EEPROM as it was already noticed for other lantiq boards using a ralink wireless. Use the base mac address from the boardconfig partition as it is done by the stock firmware. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: drop phy id specfic compatible stringMathias Kresin2017-10-072-3/+3
| | | | | | | | | | | | With kernel commit 7630ea4bda18 ("Documentation: net: phy: improve explanation when to specify the PHY ID") the purpose of using phy id specific compatibles was clarified. Remove the phy id specific compatibles since they are meant to be used if the phy reports an incorrect or no phy id at all. Reported-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: remove gen_nand compatible stringMathias Kresin2017-10-077-7/+7
| | | | | | | | | | | | | The generic nand driver fails to load with: gen_nand 14000000.nand-parts: platform_nand_data is missing gen_nand: probe of 14000000.nand-parts failed with error -22 and the xway-nand driver is used afterwards. Drop the gen_nand compatible to get rid of the error message. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: ase: fix SPI supportMathias Kresin2017-10-042-0/+2
| | | | | | | | | | Do not disable SPI in the subtarget, otherwise the SPI driver can not be used. Disable SPI by default and enable it in the board specific device tree source file. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: ARV7519RW22: enable PCIeJorge Amorós2017-09-101-1/+2
| | | | | | | Enable PCIe to make the (still unsupported) WAVE300 wireless visible to the system. Signed-off-by: Jorge Amorós <joramar76@yahoo.es>
* lantiq: VR200v: enable PCIVittorio Alfieri2017-09-091-0/+5
| | | | | | | Enable PCI to make the (still unsupported) WAVE300 wireless visible to the system. Signed-off-by: Vittorio Alfieri <vittorio88@gmail.com>
* lantiq: fix typo in EASY80920.dtsiMathias Kresin2017-07-071-1/+1
| | | | | | | There is no device tree property named phynmode0. Use phy-mode as it is done for the other ethernet nodes. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add Netgear DM200 supportThomas Nixon2017-07-071-0/+214
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Netgear DM200 is an inexpensive VDSL modem: CPU: VRX220 MIPS 34Kc 5.6 @ 500Mhz RAM: 64MiB Flash: 8MiB Ethernet: 1x100M DSL: VDSL2+, ADSL2+ reset button, 3x bi-color LEDs Serial port is 115200 baud, on the 4 pin header; pins from the bottom to top are GND, RX, TX. To upgrade from the vendor firmware, upload factory.img The DM200 bootloader supports flashing over TFTP; hold the reset button while powering on the device, and wait for the power light to start flashing green before releasing. The device is now listening on 192.168.0.1/24, and can be sent a factory.img or a netgear image with a TFTP put. Once the image is loaded, it will be written to the flash, and the device will reboot; this will take a few minutes. Thanks to Edward O'Callaghan and Baptiste Jonglez, who implemented their own ports for this device and provided valuable feedback. Signed-off-by: Thomas Nixon <tom@tomn.co.uk>
* lantiq: show xdsl line init status on shared dsl/internet ledMathias Kresin2017-06-1711-11/+11
| | | | | | | | | | | | | On boards which don't have a distinct internet and dsl led, use the shared LED to indicate the xdsl line state and any traffic that is send/received via the netdev. This traffic doesn't necessarily need to be internet traffic. Rename the shared LED of existing configs to "dsl", to match the new defaults. The configuration of the to be renamed LED is identical with the new defaults. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add Allnet ALL0333CJ supportTino Reichardt2017-06-031-0/+119
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for the Allnet ADSL2+ Modem ALL0333CJ. Specifications: - SoC: Amazon-SE - RAM: 16MB - Storage: 4MB NOR FLash - LEDs: Power, Ethernet, DSL (Sync) - Buttons: 1x Reset Button (not currently supported, will be done) - 1x Ethernet-Port: 1x RJ45 10/100BaseTX - 1x WAN-Port: AnnexB & J, G.992.1(ADSL), G.992.3(ADSL2), G.992.5(ADSL2+) Installation: - can be done via telnet+tftp or serial console - default passwords: - via telnet (root:admin) - via webinterface http://172.16.1.254:8235/ (admin:coolwhite) Installation via telnet / tftp: host: # your own host must have an tftpd daemon, then do this: host: ifconfig eth0:172 172.16.1.1 up host: # telnet to allnet modem, root:admin host: telnet 172.16.1.254 modem: # kill this daemon, it spams your console modem: killall dsl_cpe_control modem: # change to some place in ram: modem: cd /ramdisk/tftp_upload modem: # load lede-lantiq-ase-ALL0333CJ-squashfs-sysupgrade.bin alias uImage modem: tftp -g -r uImage 172.16.1.1 modem: # load these extra tools from your tftpd via: modem: # source: https://github.com/mcmilk/uboot-utils/releases/download/0.1/mips32.tar.gz modem: tftp -g -r flashwrite 172.16.1.1 modem: tftp -g -r fw_setenv 172.16.1.1 modem: tftp -g -r fw.conf 172.16.1.1 modem: ln -s fw_setenv fw_printenv modem: chmod +x * modem: ./fw_setenv disable_recovery y modem: ./fw_setenv kernel_addr 0xb0010000 modem: ./flashwrite /dev/mtd/1 uImage 0 Installation via serial line at uboot: uboot: # erase everything exept bootloader uboot: protect on b0000000 +10000; protect on b03f0000 +10000 uboot: erase all uboot: # get new firmware via tftp: uboot: tftpboot 0x80100000 uImage; setenv kernel_addr 0xb0010000 uboot: # copy to flash: uboot: cp.b 0x80100000 $(kernel_addr) $(filesize) uboot: # disable proprietary image checking: uboot: setenv disable_recovery=y; saveenv uboot: # reboot with LEDE ;) uboot: reset Ethernet works as expected, DSL syncronization does not work properly currently, I am working on this issue. Signed-off-by: Tino Reichardt <milky-lede@mcmilk.de>
* lantiq: fix amazonse.dstiTino Reichardt2017-06-031-3/+15
| | | | | | | Add missing memory@0 and localbus@0 sections. Fix MEI and GPTU interrupt definitions. Signed-off-by: Tino Reichardt <milky-lede@mcmilk.de>
* lantiq: fix avm fritz box mac addressesMathias Kresin2017-05-053-3/+7
| | | | | | | | | It has been shown that the Fritz boxes have the correct mac address set in the wireless calibration data/eeeprom. Use this mac address as base for the ethernet and xdsl interface increment/decrement the address to match the values stored in the tffs. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: DGN3500: make switch LEDs blink on activityKevin Darbyshire-Bryant2017-04-251-0/+15
| | | | | | | | | | | | | | | | | Make switch port LEDs blink on activity as they do with stock firmware. The u-boot loader sets suitable values in the LED control register that unfortunately get blown away by the linux switch driver init. Restore that value by using driver 'initvals'. 0x0431 is the led control register, the value 0x0960. Each nybble represents each LED's mode (LED3,2,1,0) in this case OFF, 1000LINK+Activity, 100/10LINK+Activity, OFF. Only LED1&2 are physically present. Enabling the blinkenlights exposed the fact that an RRCP packet was being emitted by the switch on all ports every second. Further initvals copied from stock firmware's u-boot driver disabled this 'feature'. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
* lantiq: improve DGN3500 LED definitionsKevin Darbyshire-Bryant2017-04-211-9/+11
| | | | | | | | | | | | | | | | Add red:internet led on gpio 30 previously claimed as missing. Wifi led was claimed as blue however there are no blue leds on the board at all. Actually there are two wifi leds, green & amber so add definitions for those. Make the newly discovered green wifi led gpio 14 the default. There is no amber power led on this board. The mention of the amber power led in the manual means power red and power green at the same time. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> [removed unnecessary aliases, add migration script] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: update spi driver to upstream versionHauke Mehrtens2017-03-261-1/+1
| | | | | | These patches are backported from upstream Linux kernel. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: xrx200: use vlan for ethernet wan portMathias Kresin2017-03-113-36/+6
| | | | | | | | | | | | | | | | | | | | | | | Using the lantiq,wan device tree property for one interface node and the lantiq,switch device tree property for another interface node at the same time was never intended/isn't supported at the moment. The property is meant to be used in two phy operation mode where one phy is assigned to an interface without lantiq,* device tree property and the other phy is assigned to an interface with the lantiq,wan device property to have two netdevs. If both properties are used at the same time, the lantiq,wan interface is shown as independent netdev but not able to operate independent. The port needs to be managed via swconfig. These dependency is not obvious and fooled already a lot of users. Add a default WAN vlan for xrx200 devices having an ethernet WAN port and remove the lantiq,wan device tree property. Leave it up to the user to set the ethernet WAN port as default WAN interface or to use this port as additional LAN port. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add support for the Alpha ASL56026Alex Maclean2017-03-081-0/+170
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ASL56026 is a VDSL2 router with dual 100mbit ethernet, also known as the ECI B-FOCuS V-2FUb/I. CPU: Lantiq XRX268 v1.1 at 333MHz Modem: Lantiq VRX208 RAM: 32MiB DDR2 at 167MHz Flash: 8MiB NOR, Spansion S29GL064N90TF04 UART is at JP1: Pin 1 TX Pin 2 GND Pin 3 +3.3V Pin 4 NC Pin 5 RX Boot selection pins are exposed via several resistor jumpers: boot_sel0 is at J15, on the rear of the board. Default is high. boot_sel1 is at J3, next to the flash - it is also the flash CE# pin. Default is low. boot_sel2 is at J12, directly below the SoC. Default is low. boot_sel3 is at J16, on the rear of the board. Default is low. The boot_sel pins should never be shorted, the jumper must be moved or a lower value resistor used to change the pull (existing resistors are 4k7, 1k should work) To install with the stock bootloader you must break the built in image selection process which uses at least the following vars: f_upgrade_addr, f_upgrade2_addr, loadaddr, kernel_addr, activeregion, committedregion This is done by setting loadaddr and both f_upgrade_addr vars to the same address: VR9 # setenv loadaddr 0xB0040000 VR9 # setenv f_upgrade_addr 0xB0040000 VR9 # setenv f_upgrade2_addr 0xB0040000 VR9 # saveenv Then flash the firmware image: VR9 # tftpboot 0x81000000 lede-lantiq-xrx200-ASL56026-squashfs-sysupgrade.bin VR9 # erase B0040000 +${filesize} VR9 # cp.b 0x81000000 0xB0040000 ${filesize} Signed-off-by: Alex Maclean <monkeh@monkeh.net>
* lantiq: add support for kernel 4.9Hauke Mehrtens2017-02-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The following patches were dropped because they are already applied upstream: 0012-pinctrl-lantiq-fix-up-pinmux.patch 0013-MTD-lantiq-xway-fix-invalid-operator.patch 0014-MTD-lantiq-xway-the-latched-command-should-be-persis.patch 0015-MTD-lantiq-xway-remove-endless-loop.patch 0016-MTD-lantiq-xway-add-missing-write_buf-and-read_buf-t.patch 0017-MTD-xway-fix-nand-locking.patch 0044-pinctrl-lantiq-introduce-new-dedicated-devicetree-bi.patch 0045-pinctrl-lantiq-Fix-GPIO-Setup-of-GPIO-Port3.patch 0046-pinctrl-lantiq-2-pins-have-the-wrong-mux-list.patch 0047-irq-fixes.patch 0047-mtd-plat-nand-pass-of-node.patch 0060-usb-dwc2-Add-support-for-Lantiq-ARX-and-XRX-SoCs.patch 0120-MIPS-lantiq-add-support-for-device-tree-file-from-bo.patch 0121-MIPS-lantiq-make-it-possible-to-build-in-no-device-t.patch 122-MIPS-store-the-appended-dtb-address-in-a-variable.patch The PHY driver was reduced to the code adding the LED configuration, the rest is already upstream: 0023-NET-PHY-adds-driver-for-lantiq-PHY11G.patch The SPI driver was replaced with the version pending for upstream inclusion: New driver: 0090-spi-add-transfer_status-callback.patch 0091-spi-lantiq-ssc-add-support-for-Lantiq-SSC-SPI-controller.patch Old driver: 0100-spi-add-support-for-Lantiq-SPI-controller.patch Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* generic: rtl8366rb: fix compatible stringMathias Kresin2017-02-031-1/+1
| | | | | | | Use a vendor prefix as it has to be for all not core driver. Update the compatible string in the device tree files accordingly. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: enable SMP for XRX200Felix Fietkau2017-02-012-2/+2
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: update USB controller initializationHauke Mehrtens2017-01-094-6/+11
| | | | | | | | | | | | | This adds USB initialization fixes for Danube, Amazon SE and xrx300 and should fix the clock on at least Danube which hopefully closes FS#351. The xrx200 usb driver now uses more memory for the dwc2 fifos, this was increased in the chip compared to ar9. This is based in part on the vendor documentation and the vendor code base as a reference. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: fix console print for additional boardsHauke Mehrtens2017-01-063-0/+12
| | | | | | | | | | | | | | I missed 3 boards in this commit: commit d8dde8c5178eba8c847dd48e7d06e6663ba1979f Author: Hauke Mehrtens <hauke@hauke-m.de> Date: Wed Jan 4 21:53:22 2017 +0100 lantiq: fix console print Add bootargs parameters for ARV4525PW, ARV7506PW11 and ARV8539PW22 again. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: fix console printHauke Mehrtens2017-01-0535-4/+128
| | | | | | | | | | | | | | | | | | The boot loader of many boards provides a kernel boot argument with a broken console parameter to the kernel. This will be taken before the stdout-path defined in device tree and the serial will not work on this board. Multiple boards are affected by this problem, so revert this patch for all boards. Later we can remove the boot arguments from the device tree again, after the individual board was checked to work. This partly reverts this commit: commit 4995c64857a09c4cc92238ba0bd52cdb06c4c581 Author: Martin Blumenstingl <martin.blumenstingl@googlemail.com> Date: Sun Dec 11 21:55:00 2016 +0100 lantiq: specify console using stdout-path instead of cmdline argument Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: drop the FRITZ7360SL led-dsl aliasMathias Kresin2016-12-241-1/+0
| | | | | | | | | | | | | The power LED can not be used for indicating the xDSL line state and the in system (boot) state at the same time in LEDE. As soon as the xDSL Line goes down, the power LED is switched off. During xDSL handshake the power led would blink with the same or a similar pattern as during boot. Both might confuse users. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add FRITZ7360SL phy reset gpiosMathias Kresin2016-12-241-5/+5
| | | | | | | | | | | | | | | Due to a hardware bug of Atheros 8030 phys, the driver need to reset the phys on link state change. Use the correct compatible string for the at903x phys connected to switch port 0 and 1. Fix the pinmux of the gpio lines connected to the reset pin of the phys and define the reset-pins to let the driver do the fixups. Fixes FS#343 Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix DGN1000B boot status ledsMathias Kresin2016-12-241-9/+7
| | | | | | The alias node should not be a child of the chosen node. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: remove "init" kernel command line parameter from bootargsMartin Blumenstingl2016-12-1234-125/+2
| | | | | | | | | | /etc/preinit has been the default init-script for a very long time (at least since Linux 2.6.30 in OpenWrt). Remove the kernel command line "init" parameter to get rid of duplicate and inconsistent definitions of this parameter (some boards, like FRITZ3370 for example did not use it at all, while it's just copy and paste on others). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: specify console using stdout-path instead of cmdline argumentMartin Blumenstingl2016-12-1240-37/+70
| | | | | | | | Use devicetree's /chosen/stdout-path instead of the kernel command line (embedded in the .dts-files) to specify the serial console. Using the chosen node is recommended on devicetree based platforms. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: falcon: remove bootargs-appendHauke Mehrtens2016-12-1010-40/+0
| | | | | | | This attribute is not evaluated any more and the boot loader on these reference boards does not provide a broken root= or console= parameter. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: fix image validation errorsMathias Kresin2016-12-0413-11/+16
| | | | | | | The boards did not have the name set that is expected during metadata validation on sysupgrade. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use BT HomeHub 5 Type A OEM partition layoutMathias Kresin2016-11-291-15/+14
| | | | | | | | | | | | | | | | | | | | This way the on nand bad block table is preserved and used. Add support for nand OOB ECC checksums as well. It should fix all reported ubi errors, which were all related to bad nand blocks and a purged on nand bad block table. The existing ubi partition will be reused, which eliminates the need to touch the caldata during initial install. The BT u-boot has support for loading a kernel from an ubi volume. It isn't necessary any longer to replace the BT u-boot with a custom compiled one to use LEDE. It is required to restore the BT Firmware and install LEDE from scratch to switch to the new partition layout. An image for restoring the BT firmware and installing LEDE is provided at https://github.com/mkresin/lede/releases. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: backport kernel patch to pass of node to nand_dt_initMathias Kresin2016-11-291-2/+0
| | | | | | | | | | | | | | | | | | | Backport upstream commit a61ae81a1907af1987ad4c77300508327bc48b23. The actually purpose of the patch was to do some cleanup. As a side effect of this cleanup, the device node is now passed to nand_dt_init. This allows to use the common nand device tree properties - nand-bus-width - nand-on-flash-bbt - nand-ecc-mode - nand-ecc-step-size - nand-ecc-strength for the plat_nand driver. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use ath9k device tree bindings binding/owl-loaderMartin Blumenstingl2016-11-2911-125/+148
| | | | | | | | | | | | | | | | | This moves the extraction of the eeprom/calibration data to a hotplug firmware script. Additionally it modifies all .dts to configure ath9k directly from within the .dts. The owl-loader approach enables support on devices with exotic eeprom data locations (such as unaligned positions on the flash or data inside an UBI volume). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> [add ath9k caldata mac address patcher] [fixes DGN3500 wifi mac] [fixes BTHOMEHUBV3A wifi mac] [set invalid mac for BTHOMEHUB2B, FRITZ3370, FRITZ7320 & FRITZ7360SL to restore previous random mac behavior] Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add Falcon supportHauke Mehrtens2016-11-2715-0/+1380
| | | | | | | | | | | | This adds support for the Intel Falcon SoC for GPON. Support for the Falcon SoC was removed in commit c8218363951 svn rev: 40392 from OpenWrt, this commit adds it again. This patch adds a new subtarget for the Falcon SoC, but it still misses all the drivers needed to control the GPON part. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* treewide: fix button keys codes used in dtsMathias Kresin2016-11-2715-19/+20
| | | | | | Use keycodes that matches the intended use case based on the label. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: specify the PCIe controller's interrupt, size and address cellsMartin Blumenstingl2016-11-261-2/+10
| | | | | | This allows adding devices to the PCIe controller in the .dts files. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: write protect vgv7519 u-boot and u-boot-env partitionsEddi De Pieri2016-11-231-0/+2
| | | | Signed-off-by: Eddi De Pieri <eddi@depieri.net>
* lantiq: device tree bindings for dwc2 on danubeBen Mulvihill2016-11-211-1/+2
| | | | | | | | | Device tree binding for dwc2 usb driver on danube. Leave old ifxhcd-danube driver as an alternative. Also adds dr_mode = "host" to eliminate warning on boot. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com>
* lantiq: enable VMMC for VGV7519dpeddi2016-11-161-1/+10
| | | | Signed-off-by: Eddi De Pieri <eddi@depieri.net>
* lantiq: enable VMMC for VGV7510KW22Eddi De Pieri2016-11-161-1/+10
| | | | Signed-off-by: Eddi De Pieri <eddi@depieri.net>
* treewide: dts: use keycode defines from input dt-bindingMathias Kresin2016-11-1339-4/+70
| | | | | | | | | | | | | | | | | | | | | All compiled device tree files not mentioned are binary identical to the former ones. Fix the obvious decimal/hex confusion for the power key of ramips/M2M.dts. Due to the include of the input binding header, the BTN_* node names in: - ramips/GL-MT300A.dts - ramips/GL-MT300N.dts - ramips/GL-MT750.dts - ramips/Timecloud.dts will be changed by the compiler to the numerical equivalent. Move the binding include of lantiq boards to the file where they are used the first time to hint the user where the values do come from. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use the device tree bindings from rt2x00 driverMathias Kresin2016-11-0910-110/+136
| | | | | | | | | | | | | Set a device specific wireless mac address for ARV7506PW11, VGV7519 and VGV7510KW22. The one from the EEPROM is a generic one and the same on all boards. Use the wifi@0,0 label and the pci0,0 compatible string for the ARV7519PW and ARV7525PW since the pci vendor and device id is unknown. It should work anyway since the compatible string isn't evaluated (yet). Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix VGV7519 and VGV7510KW22 mac addressesMathias Kresin2016-11-092-2/+2
| | | | | | | | | | | | | | | | | The VGV7510KW22 stock firmware uses the following mac-addresses: lan (ifno 1): AA:BB:CC:DD:EE:60 wlan (ifno 2): AA:BB:CC:DD:EE:61 atm0 (ifno 3): AA:BB:CC:DD:EE:62 atm1/wan (ifno 4): AA:BB:CC:DD:EE:63 The VGV7519 stock firmware uses the following mac-addresses: lan: AA:BB:CC:DD:EE:EF wlan: AA:BB:CC:DD:EE:EF wan: AA:BB:CC:DD:EE:EE Signed-off-by: Mathias Kresin <dev@kresin.me>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 18:10:07 +0000