aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/dts
Commit message (Collapse)AuthorAgeFilesLines
* kernel: remove a hack that was obsoleted upstreamDaniel Gimpelevich2016-06-221-1/+1
| | | | Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* lantiq: VGV7510KW22BRN - set the phy clock sourceJohn Crispin2016-06-191-0/+6
| | | | | | | | | | | | | VGV7510KW2 with VRX288 v1.2 has brnboot 1.8 installed. Starting with this brnboot version, the "GPHY Clock Source" isn't set anymore by brnboot, with the result that xrx200-net fails to probe/initialize the phys. Use the phy clock source device tree binding to specify the clock source. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49284 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: VGV7510KW22BRN - support dual-imageJohn Crispin2016-06-191-1/+4
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49282 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: move partitions into partion table nodeJohn Crispin2016-06-1942-1006/+1253
| | | | | | | | | | Starting with kernel 4.4, the use of partitions as direct subnodes of the mtd device is discouraged and only supported for backward compatiblity reasons. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49280 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: VG3503J - use the same PHY led functionality as the OEM firmwareJohn Crispin2016-06-191-8/+8
| | | | | | | | | | | | | Based on the vg3503j_gphy_led.sh script published in the VG3503J wiki article, the OEM Firmware uses the following PHY led functionality: gphy led 0: LINK/ACTIVITY gphy led 1: LINK gphy led 2: ACTIVITY Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49278 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: use the same functionality for all ethernet phys ledJohn Crispin2016-06-191-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | The VGV7510KW22 has the leds for LAN1-3 connected to pin1 of the phys and the led for LAN4 connect to pin0 of the phy. This results with the current configuration in a fast flashing LAN4 led as soon as a network cable is connected. Something similar was reported on the forum[1] for the VGV7519 as well. Since it isn't predicable to which pin a (single) phy led is connected, use the (default) pin1 functionality Constant On: 10/100/1000MBit Blink Fast: None Blink Slow: None Pulse: TX/RX for all ethernet phy leds. After checking pictures of all vr9 boards, it looks like only the VG3503J has more than one led connected per phy. Using the phy led device tree bindings to assign the functionality to the "additional" leds, the VG3503J phy leds should behave as before. Signed-off-by: Mathias Kresin <openwrt@kresin.me> [1] https://forum.openwrt.org/viewtopic.php?pid=321523 git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49270 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: remove read-only flag on two partitions on BTHOMEHUBV3AJohn Crispin2016-04-261-2/+0
| | | | | | | | | | | Remove read-only flag on two partitions on BTHOMEHUBV3A: uboot-config - otherwise fw_setenv command cannot be used. ath9k-cal - so that ath9k calibration data can be copied to the partition on a newly installed board. Signed-off-by: Ben Mulvihill <ben.mulvihill@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@49250 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: VGV7510KW22/VGV7519 update spi pinmux groupJohn Crispin2016-02-082-2/+2
| | | | | | | | | | | | | With the backport of the kernel 4.5 pinctrl-xway patches (3551609d & 826bca29) the pinmux group "spi" was splitted into "spi_di", "spi_do" & "spi_clk". But the no longer existing group "spi" is still used by some device tree source files. This fixes the detection of the wireless chipset of the VGV7510KW22. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48658 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: BTHOMEHUBV5A - explicit select the flash deviceJohn Crispin2016-02-081-1/+1
| | | | | | | | | | | | | The stock u-boot doesn't disable unused flash banks. Therefore, the nand driver tries to initialize a not connected NOR flash and the device hangs on boot. Workaround the issue by selecting the second flash bank (NAND). Signed-off-by: Mathias Kresin <openwrt@kresin.me> Acked-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48657 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Make the ar9.dtsi sram node match "simple-bus"Felix Fietkau2016-01-291-1/+1
| | | | | | | | | | | All other SoC types are using "lantiq,sram" and "simple-bus" to ensure that all child nodes are set up correctly during linux kernel initialization (plat_of_setup(void) in arch/mips/lantiq/prom.c). Without this some of sram child nodes might not be parsed. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48548 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Move the definition of the xrx200-net node to vr9.dtsiFelix Fietkau2016-01-2911-764/+669
| | | | | | | | | | This removes a lot of duplicate register and interrupt definitions by moving the xrx200-net definition to vr9.dtsi and making all devices re- use it. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48547 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: add support for TP-Link VR200vHauke Mehrtens2016-01-181-0/+280
| | | | | | | | | | This adds basic support for TP-Link VR200v. Currently the following parts are not working: FXO, Voice, DECT, WIFI (both) Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48328 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Remove incorrect PCIe compatible stringsFelix Fietkau2016-01-172-5/+0
| | | | | | | | | Re-defining the compatible property is not required since the correct value is inherited from vr9.dtsi. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48295 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Switch to the new SPI driverFelix Fietkau2016-01-178-31/+92
| | | | | | | | | | | | | | | | Compared to the "old" driver: - Each device must assign a pinctrl setting to the SPI node to allow the new SPI driver to configure the SPI pins. While here we are also using separate input and output settings so we are independent of whether the bootloader configures the pins correctly. - We use the new "compatible" strings to make the driver choose the correct number of chip-selects for each SoC. - The new driver starts counting the chip-selects at 1 (instead of 0, like the old one did). Thus we have to adjust the devices accordingly. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48293 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Enable the hardware SPI driver on the DGN3500/DGN3500BFelix Fietkau2016-01-171-53/+38
| | | | | | Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48290 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Enable SPI for the EASY80920 board againFelix Fietkau2016-01-171-46/+41
| | | | | | | | Also switch to the SPI definition provided by vr9.dtsi Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48289 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Switch FRITZ3370 from spi-gpio to the hardware SPI driverFelix Fietkau2016-01-171-40/+31
| | | | | | Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48288 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Re-use the SPI node from vr9.dtsi in TDW89X0.dtsiFelix Fietkau2016-01-171-40/+36
| | | | | | | | This removes the duplicate SPI register definition. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48287 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Add the SPI node to ar9.dtsi and vr9.dtsiFelix Fietkau2016-01-172-0/+20
| | | | | | | | | | This allows devices to use SPI without having to re-define (and thus duplicating) the whole SPI node. By default SPI is disabled (as before) because only few devices need it. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48286 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Configure the PCIe reset GPIO using OFFelix Fietkau2016-01-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | After the latest pinctrl backports there are only 50 (instead of 56 as before) GPIOs/pins exported (thus the first GPIO on VRX200 SoCs is now 462, before it was 456). This means that any hardcoded GPIOs have to be adjusted. This broke the PCIe driver (which seems to be the only driver which uses hardcoded GPIO numbers), it only reports: ifx_pcie_wait_phy_link_up timeout ifx_pcie_wait_phy_link_up timeout ifx_pcie_wait_phy_link_up timeout ifx_pcie_wait_phy_link_up timeout ifx_pcie_wait_phy_link_up timeout pcie_rc_initialize link up failed!!!!! To prevent more of these issues in the future we remove the hardcoded PCIe reset GPIO definition and simply pass it via device-tree (like the PCI driver does). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48285 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Use the new pinctrl compatible stringsFelix Fietkau2016-01-174-4/+4
| | | | | | | | | | | | | | | | These were introduced in upstream commit be14811c03cf "pinctrl/lantiq: introduce new dedicated devicetree bindings" and finally allow us to use the individual pins within our dts (for example spi_clk, etc.). Please note that this changes the number of GPIOs which are available for some SoCs. VRX200 SoCs for example only have 50 pins, but previously 56 pins were exposed. This means that all places which are using hardcoded GPIO numbers (which are not passed via device-tree) need to be adjusted (because the first GPIO number is now 462, instead of 456). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48284 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Add the xbar to vr9.dtsJohn Crispin2016-01-011-1/+5
| | | | | | | | linux 4.4 (since commit 08b3c894e56580b8ed3e601212a25bda974c3cc2 "MIPS: lantiq: Disable xbar fpi burst mode") requires that the xbar is defined in the .dts of vrx200 (VR9) SoCs. git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48056 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: TDW8980 - use devicename:colour:function led naming schemeJohn Crispin2016-01-011-1/+1
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48044 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: P2812HNUFX - move usb leds to P2812HNU-F1John Crispin2016-01-012-10/+18
| | | | | | | | | | The P2812HNU-F3 doesn't have usb leds. Only the P2812HNU-F1 has those leds. Reported-by: Sylwester Petela <sscapi@gmail.com> Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48043 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: use devicename:colour:function led naming schemeJohn Crispin2016-01-0129-368/+392
| | | | | | | | | | | | | | | | The leds of the following boards are not renamed due to lack of manuals/informations: - ARV7519PW - ARV7510PW22 - ARV4510PW The leds of the ARV4518PWR01* boards are unchanged, since the leds doesn't match the leds from the manual or pictures (e.g. there shouldn't be a wps led). Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48042 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: add support for indicating the boot state using three ledsJohn Crispin2016-01-0131-78/+173
| | | | | | | | | | | | | | The BTHOMEHUBV5A has a RGB power led, where every colour is perfect to indicate the current boot state. This patch adds support for such cases. The existing led sequences should be the same as before. Boards which are using a led different from power (like TDW89x0) are changed to switch of the led after boot Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48041 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: use dsl led defined in DTSJohn Crispin2016-01-012-2/+2
| | | | | | | | | | | | | | | | | dsl_control (dsl_notify.sh) is the only process which is aware of the state of the atm/ptm interface. Use the dsl led exclusive for the dsl line state. On boards which don't have a distinct internet and a dsl led, let the netdev status of the atm interface trigger the shared led. Triggering the shared led according to the status of the ppp interface isn't suitable, since the led would be switched of if the ppp connection goes down, but the line is still in sync. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48040 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: define default leds in dts filesJohn Crispin2016-01-0131-135/+371
| | | | | | | | | | - ARV7525PW: use the power led as dsl led as done by the stock firmware - FRITZ3370: use the info led as internet led - FRITZ7320: use the power led as dsl led as done by the stock firmware Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48037 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: ARV752DPW - fix dts fileJohn Crispin2016-01-011-9/+13
| | | | | | | | | | | | | | Use the same led logic and labels as the OEM firmware (red = okay, blue = failure). Add the red internet led. Remove missing usb led workaround. The workaround shouldn't be in the default configuration. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48036 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: ARV752DPW22 - fix dts fileJohn Crispin2016-01-011-22/+12
| | | | | | | | | | | No need to switch (and keep) on all leds at boot. Use the same led logic and labels as the OEM firmware (red = okay, blue = failure). Add the red internet led. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48035 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: DGN1000B - fix typo in dts fileJohn Crispin2016-01-011-1/+1
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48034 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: ARV4518PWR01* move redundant parts to dtsiJohn Crispin2016-01-013-356/+186
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48033 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: P2812HNUFX - move leds to dtsiJohn Crispin2016-01-013-114/+61
| | | | | | | | Beside the used labels, they are the same on both boards. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@48031 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: TDW89x0 - increase spi frequencyJohn Crispin2015-12-231-2/+4
| | | | | | | | | | | | | | | | | Use the same max spi frequency as set in u-boot. According to the datasheets, the Q64-104HIP as well as the Winbond 25Q64FVSIG support spi frequencies up to 50 MHz. During my tests, the Q64-104HIP couldn't be recognized/initialized if the frequency was > 40MHz. Both chips do support fast read as well. While touching the dts file, I fixed the dtc compiler warnings. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47994 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Configure LED polarity for TDW8970 and TDW8980.John Crispin2015-12-232-4/+1
| | | | | | | | | This patch configures the correct ath9k WLAN LED polarity for the TDW8970, and for the TDW8980 as well. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47969 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: fix ARV7519RW22 buttonsJohn Crispin2015-12-171-7/+7
| | | | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47918 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: add the TDW8980 5GHz ledJohn Crispin2015-12-171-0/+7
| | | | | | | | | Still unused, but u-boot doesn't take care of the led, which results in a permanent switched on 5GHz LED. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47915 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Configure LED polarity for TDW8970.John Crispin2015-12-171-0/+4
| | | | | | | | This patch configures the correct ath9k WLAN LED polarity for the TDW8970. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47913 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Configure disabled WLAN bands for TDW89X0.John Crispin2015-12-171-0/+1
| | | | | | | | | | | | | | | | | The TDW8970 has a AR9381, which is the bgn 3x3:3 variant of the AR938x family. The TDW8980 has a AR9287, which is the bgn 2x2:2 variant of the AR928x family. This means that the chip for both routers is 2.4 GHz only. Anyway, the manufacturer didn't disable the 5 GHz band in the EEPROM partition (at least on my TDW8970). So this patch disables the 5 GHz band. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47912 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: get rid of the dsl_fw mtd partitionFelix Fietkau2015-12-053-18/+3
| | | | | | | | | Now that we have redistributable vdsl/adsl firmware blobs in /lib/firmware, we can drop the dsl_fw partition and extend the firmware partition. Signed-off-by: Andre Heider <a.heider@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47783 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: re-enable spi-xway for TD-W89X0 now that it is fixedFelix Fietkau2015-12-041-58/+46
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47768 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: fix up m25p80 device ids (#20975)Felix Fietkau2015-12-025-10/+5
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47690 3c298f89-4303-0410-b956-a3cf2f4a3e73
* Revert "lantiq: activate spi-xway on TDW89X0"John Crispin2015-10-191-47/+59
| | | | | | | | | | This reverts commit 68c2e4789b4f071ee75d39248f4d08fe8283eb28. commit r47159 was bad Signed-off-by: John Crispin <blogic@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47207 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: activate spi-xway on TDW89X0John Crispin2015-10-071-59/+47
| | | | | | | | use the hardware spi core in favour of spi-gpio. Signed-off-by: John Crispin <blogic@openwrt.org> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47159 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: several ARV7519RW22 fixesJohn Crispin2015-10-051-9/+13
| | | | | | | | | | | | | | Fixes ARV7519RW22 flash register (only 1 flash). Power LED is green, not red. Rename message LEDs to internet. Add LEDs configuration (lan, wan, power). Enable switch VLANs. Fix secondary USB. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> Signed-off-by: José Vázquez Fernández <ppvazquezfer@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47132 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Add target TP-Link TD-W8980John Crispin2015-10-053-250/+284
| | | | | | | | | The device is similar to the TD-W8970, beside a different Atheros 2.4 GHz wireless chip and the additional, PCI connected, WAVE300 5 GHz wireless. Signed-off-by: Mathias Kresin <openwrt@kresin.me> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@47130 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Introduce DWC2 compatible DTS definitions for AR9 USBJohn Crispin2015-09-141-1/+10
| | | | | | | | | | | | Since the AR9 USB is very similar to the VR9 USB it too can be used with the upstream DWC2 driver. Here are the DTS definitions which make it compatible with the DWC2 driver. Signed-off-by: Antti Seppälä <a.seppala@gmail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46914 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Add support for Arcadyan ARV8539PW22 (Speedport W 504V)John Crispin2015-07-071-0/+162
| | | | | | | | lantiq: Add support for Arcadyan ARV8539PW22 (Speedport W 504V) Signed-off-by: Jannis Pinter <jannis@pinterjann.is> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46224 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Add support for the BT Home Hub 5AJohn Crispin2015-07-071-0/+287
| | | | | | | | | | | | | | | u-boot support depends on the next "upstream" version ([0]) from Daniel Schwierzeck. Since the installation process is quite complicated a "how to" was added to the wiki: [1] [0] https://github.com/danielschwierzeck/u-boot-lantiq/tree/openwrt/v2014.01-next [1] http://wiki.openwrt.org/toh/bt/homehub_v5a V2: Use the correct PCI interrupt (fixes 2.4GHz wifi) Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46223 3c298f89-4303-0410-b956-a3cf2f4a3e73
* lantiq: Make the MEI address available for kernel driversJohn Crispin2015-07-071-0/+1
| | | | | | | | Newer DSL driver versions depend on the address information. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46221 3c298f89-4303-0410-b956-a3cf2f4a3e73
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-19 16:46:16 +0000