aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq/base-files/etc
Commit message (Collapse)AuthorAgeFilesLines
* lantiq: simplify ath9k eeprom extraction scriptMathias Kresin2016-12-081-11/+16
| | | | | | | | | | | Add an extra function to patch the mac and fixup the checksum afterwards. Calculate the checksum position automatically. The offset to the mac address is the same for all checksum protected EEPROMs. No EEPROM requires a byte swapped mac address. The mac byte swap code was required due to an bug in the script that is now fixed. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix ath9k EEPROM data swapping for some devicesMartin Blumenstingl2016-12-081-14/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The EEPROM data in the flash of the ARV7518PW, ARV8539PW22, BTHOMEHUBV2B and BTHOMEHUBV3A is stored byte-swapped (swab16), meaning that for example the ath9k base_eep_header fields "version" (high and low byte), "opCapFlags" and "eepMisc" are swapped (the latter ones are just 1 byte wide, thus their position is swapped). The old "ath,eep-endian" property enabled the corresponding swapping logic in the ath9k driver (swab16 in ath9k_hw_nvram_swap_data, which is based on the magic bytes in the EEPROM data which have nothing to do with the calibration data - thus this logic should not be used anymore). Since we have switched to the upstream ath9k devicetree bindings there is no binding anymore which enables swab16 in ath9k (as this logic is not recommended anymore as explained above), leading to ath9k initialization errors: ath: phy0: Bad EEPROM VER 0x0001 or REV 0x00e0 (this shows that the version field is swapped, expected values are VER 0x000E and REV 0x0001) Swapping the ath9k calibration data when extracting it from the flash fixes the devices listed above (all other devices do not require additional swapping, since the position of the fields is already as expected by ath9k). This allows ath9k to read the version correctly again, as well as the more important "eepmisc" field (which is used for determining whether the data inside the EEPROM is Big or Little Endian which is required to parse the EEPROM contents correctly). Fixes: a20616863d3 ("lantiq: use ath9k device tree bindings binding/owl-loader") Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: fix image validation errorsMathias Kresin2016-12-042-4/+4
| | | | | | | 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-293-20/+22
| | | | | | | | | | | | | | | | | | | | 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: use ath9k device tree bindings binding/owl-loaderMartin Blumenstingl2016-11-291-0/+140
| | | | | | | | | | | | | | | | | 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: fix port indexing for WBMR-300Felix Fietkau2016-11-141-1/+1
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: use the device tree bindings from rt2x00 driverMathias Kresin2016-11-091-60/+0
| | | | | | | | | | | | | 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-091-2/+3
| | | | | | | | | | | | | | | | | 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>
* lantiq: rework VG3503J imageMathias Kresin2016-10-191-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use the new image build code and remove the lzma loader. The lzma loader was used to cheat the signature validation of the bootloader and I found another way to do this. To migrate boards already using LEDE/OpenWrt to the new image the following steps need to be done once: VR9 # run reset_uboot_config VR9 # reset VR9 # setenv ethaddr AA:BB:CC:DD:EE:FF VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000 VR9 # saveenv VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin VR9 # erase 0xb0020000 $(filesize) VR9 # cp.b 0x81000000 0xb0020000 $(filesize) The mac address is printed on the label at the bottom of the case. The following steps are need to be done during first install: VR9 # setenv preboot ping 1.1.1.1\;bootm 0xb001f000 VR9 # saveenv VR9 # tftp 0x81000000 lede-lantiq-xrx200-VG3503J-squashfs-sysupgrade.bin VR9 # erase 0xb0020000 $(filesize) VR9 # cp.b 0x81000000 0xb0020000 $(filesize) The image uses the uImage firmware splitter now instead of hardcoded kernel and rootfs partitions. The firmware partition size was extended to use flash space that was reserved for partitions required only by the ECI firmware. Due to the changes an upgrade to a later LEDE revision from a running LEDE is supported now. A default switch config was added and the device uses the same MAC addresses as the ECI firmware now instead of the same for all VG3503J. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: use wpad-mini for WBMR boardsMathias Kresin2016-10-151-16/+0
| | | | | | | | | | The WBMR boards are the only ones in the whole tree selecting the wpad and hostapd-utils package by default. Remove the wps uci-default script as well, there is no obvious reason why the wps config need to be set only for this board. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: cleanup led handling functionsMathias Kresin2016-10-052-10/+17
| | | | | | | | | Use a more generic name for the lantiq_get_dt_led_chosen function. Drop the lantiq_is_dt_led_chosen function. The lantiq_get_dt_led function can be used to achieve the same. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: board.d: apply alphabetical order to led fileMathias Kresin2016-10-051-12/+12
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: do not "local" variables outside of a functionMartin Blumenstingl2016-09-242-5/+5
| | | | | | | | | Older busybox versions allowed using the local keyword outside of functions, whereas 1.25.0 (which was introduced in 06fa1c46fc32) do not allow this anymore (leading to the following error when executing the script: "file: local: line nn: not in a function"). Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* cleanup ucidef_set_interface* usageMathias Kresin2016-09-101-2/+2
| | | | | | | | - quote the interface name - remove call of not existing function - remove the proto if it's the default proto Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: board.d: apply alphabetical orderMathias Kresin2016-09-101-43/+43
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: board.d: cleanup default switch configMathias Kresin2016-09-101-32/+19
| | | | | | | | | | | | | | | | Add or fix the physical port number of switch ports to allow LuCI to display the ports in physical order. Remove the physical port number in case bridge port and physical port order are the same. Reorder the ucidef_add_switch parameter to be aligned with the switch port number. Remove board settings which are covered by the default case and remove comments. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: generate switch configuration for BTHOMEHUBV2B.Sigurd Hogsbro2016-08-201-1/+8
| | | | | | | Split from HH3A as it appears to have a different switch. https://en.wikipedia.org/wiki/BT_Home_Hub#Models_and_technical_specifications Signed-off-by: Sigurd Hogsbro <sigurd@hogsbro.org>
* lantiq: board.d: set lan mac address only where necessaryMathias Kresin2016-08-101-16/+8
| | | | | | | Do not set the lan mac address for boards which having the lan mac address already set in device tree source file. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix switch configuration for EASY80920Hauke Mehrtens2016-07-281-0/+7
| | | | | | | | The device tree description misses some Ethernet ports and there was no model specified for this board. In addition there was no switch specific default configuration created. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq: fix WBMR-300HPD switch port assignmentFelix Fietkau2016-07-281-4/+5
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: add support for ARV7506PW11 (Alice/O2 IAD 4421)Oswald Buddenhagen2016-06-223-1/+12
| | | | | | | | | | | | | | | | | | Ethernet, ADSL2+ and LEDs are fully functional. Supporting the two TAE ports and SIP gateway was not attempted. The WiFi is unreliable, due to experimental support for rt35xx family devices by the rt2800pci driver. Signed-off-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de> [rebase to LEDE HEAD] [switch to normal image instead of brnboot image] [remove not required pinmux child nodes keys, leds, ebu, exin, pci_in and pci_out] [remove switch_rst pinmux child node (no support for hw reset in driver/setting a default GPIO value in DT] [enable usage of the wireless LED] [fixup mac address configuration] Sgned-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: remove gr7000 supportJohn Crispin2016-06-221-4/+0
| | | | | | this seems to have never worked as the wrong SoC is selected Signed-off-by: John Crispin <john@phrozen.org>
* lantiq: diag - switch off the power led on failsafeMathias Kresin2016-06-201-0/+4
| | | | | | | | | | | | | | This patch is a follow up to commit 4cf3fd4 "add support for indicating the boot state using three leds". At the time of writing the patch, I wasn't aware that it's possible to switch info failsafe after boot (factory reset). Enabling the failsafe led without disabling the running led causes an unexpected led colour on devices using a single multicolour led to indicate the boot state. Signed-off-by: Mathias Kresin <dev@kresin.me>
* Revert "lantiq: Use correct macaddr generating logic for the DGN3500"Felix Fietkau2016-06-151-5/+0
| | | | | | | This reverts commit 492964e741f1e0254b6ed7c0a095551a31d25dc9, which makes no sense. /etc/board.d cannot be used for system init stuff. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: add ARV4525PW wifi ledJohn Crispin2016-06-141-0/+3
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* lantiq: fix fritz7320 wifi supportJohn Crispin2016-06-141-0/+3
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* lantiq: Add Support for Fritz!Box 7360 SLJohn Crispin2016-06-131-0/+5
| | | | | Signed-off-by: Sebastian Ortwein <krone@animeland.de> Tested-by: Guido Lipke <lipkegu@gmail.com>
* lantiq: add default lan setup to board.d scriptJohn Crispin2016-06-131-0/+3
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* lantiq: add Buffalo WBMR-300HPD supportFelix Fietkau2016-06-112-0/+14
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: Use correct macaddr generating logic for the DGN3500Daniel Gimpelevich2016-05-271-0/+5
| | | | Signed-off-by: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
* lantiq: VGV7519 - add vlan supportMathias Kresin2016-05-271-1/+2
| | | | | | Add the lantiq,switch property to enable vlans and setup them up. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix ARV4518PWR01 networkMohammed Berdai2016-05-271-0/+4
| | | | | | | | This patch fixes the missing Lan interface config in the file /etc/config/network for ARV4518PWR01/A which results in eth0 and br-lan being down and therefore no way to access the router unless via UART-TTL. Signed-off-by: Mohammed Berdai <mohammed.berdai@gmail.com>
* image / basefiles: make console password configurableJohn Crispin2016-04-181-1/+1
| | | | | Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com> Signed-off-by: John Crispin <john@phrozen.org>
* lantiq: Fix typo in LED diag script.John Crispin2016-04-261-1/+1
| | | | | | | Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> Acked-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 49242
* lantiq: do not set default firmware fileFelix Fietkau2016-03-071-1/+1
| | | | | | | | | We are now shipping a DSL firmware, do not set it by default to some file name. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 48941
* lantiq: add support for TP-Link VR200vHauke Mehrtens2016-01-181-0/+7
| | | | | | | | | 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> SVN-Revision: 48328
* lantiq: fix VDSL device detection with Linux 4.4Felix Fietkau2016-01-181-1/+1
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48319
* lantiq: match default xdsl mode and default wan interfaceJohn Crispin2016-01-011-1/+5
| | | | | | Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48047
* lantiq: use devicename:colour:function led naming schemeJohn Crispin2016-01-011-4/+4
| | | | | | | | | | | | | | | | 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> SVN-Revision: 48042
* lantiq: add support for indicating the boot state using three ledsJohn Crispin2016-01-012-54/+16
| | | | | | | | | | | | | | 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> SVN-Revision: 48041
* lantiq: use dsl led defined in DTSJohn Crispin2016-01-011-8/+11
| | | | | | | | | | | | | | | | | 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> SVN-Revision: 48040
* lantiq: use power leds defined in DTSJohn Crispin2016-01-011-15/+19
| | | | | | | | Use the power leds defined in the dts file instead of hardcoded led names. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48039
* lantiq: use default leds defined in DTSJohn Crispin2016-01-011-20/+7
| | | | | | | | | | | | | Remove all now double defined leds from the led board file. Use pppoe as default for all broadband connections, since it's the default in OpenWrt now. Rename the the wifi leds to make sure, the not applicable default values get overwritten. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48038
* lantiq: BTHOMEHUBV2B - remove missing usb led workaroundJohn Crispin2016-01-011-1/+0
| | | | | | | | The workaround shouldn't be in the default configuration. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 48032
* lantiq: Fix LED handling.John Crispin2015-12-171-24/+32
| | | | | | | | | | - Use common OpenWrt blink patterns instead of custom ones - Add preinit_regular hook - Handle the TDW89X0 that does not have a configurable power LED Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net> SVN-Revision: 47914
* all: drop old uci-defaults.shJo-Philipp Wich2015-12-112-2/+2
| | | | | | | | | Replace former uci-defaults.sh implementation with the uci-defaults-new.sh one and update all users accordingly. Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47867
* lantiq: fix led setup after switch to uci-defaults-new.shJohn Crispin2015-12-111-6/+7
| | | | | | | | | | | | | | | | | | | | | | | The switch to uci-defaults-new.sh revealed a bug in the former used uci-defaults.sh, which failed to add leds with colons in the led name. This bug isn't any longer present in uci-defaults-new.sh and therefore all via DT defined leds will be added to /etc/config/system with their initial on/off state, regardless whether they are already added by the board specific led mappings. This results for a BTHOMEHUBV5A into the following led configuration: - soc:blue:power is added as led_power with the initial state "switched on" - soc:blue:power is added as led_soc_blue_power with the initial state "switched off" With the final result of a switched off power led after boot. The only led that needs to be added is the BTHOMEHUBV5A specific dimmed led. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47850
* lantiq: fix logic error in dsl board.d codeJo-Philipp Wich2015-12-061-1/+1
| | | | | | | | | | | Starting with r47755 the pppoe wan interface section isn't any longer added to the network config on firstboot, using the default configuration. Since the commit message does not mention such a change, I assume that this wasn't intentionally. Signed-off-by: Mathias Kresin <openwrt@kresin.me> SVN-Revision: 47793
* lantiq: get rid of the dsl_fw mtd partitionFelix Fietkau2015-12-051-35/+0
| | | | | | | | | 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> SVN-Revision: 47783
* lantiq: move esi calls to dsl_cpe_control scripts to fix ordering wrt. ↵Felix Fietkau2015-12-041-7/+0
| | | | | | | | loading vr9 drivers Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 47764
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-18 16:12:31 +0000