KumiSystems/openwrtv4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
openwrtv4/target/linux/mpc85xx/base-files/etc/board.d/02_network

29 lines
531 B
Text
Raw Normal View History

mpc85xx: add user-space support for the TL-WDR4900 v1 Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35733
2013-02-21 19:20:34 +00:00
#!/bin/sh
mpc85xx: migrate network setup to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47540
2015-11-20 23:52:31 +00:00
# Copyright (C) 2014-2015 OpenWrt.org
mpc85xx: add user-space support for the TL-WDR4900 v1 Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35733
2013-02-21 19:20:34 +00:00
all: drop old uci-defaults.sh 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
2015-12-11 15:26:06 +00:00
. /lib/functions/uci-defaults.sh
mpc85xx: fix WAN/LAN-MAC for TP-LINK TL-WDR4900 v1 This works around a bootloader issue where every device has the same lan/wan-mac 00:04:9f:ef:01:01 - with this patch we read the macs from config-partition during initial network setup. We have 9 valid macs stored in the partition, the 1st two are used for the radios, 3 and 4 are now used for WAN/LAN. on an already setup / running device we can get the real macs with . /lib/functions.sh . /lib/functions/system.sh echo "LAN = $(mtd_get_mac_binary config 338)" echo "WAN = $(mtd_get_mac_binary config 344)" see: https://dev.openwrt.org/ticket/14714 from the ticket / user klondike: U-Boot passed this commit https://gitorious.org/0xlab-kernel/u-boot/commit/ecd1a09b81f2ed6e6ba7bd1d0bfb0cc3d0ea2ad0 http://u-boot.10912.n7.nabble.com/U-Boot-PATCH-mpc83xx-remove-hardcoded-network-addresses-from-config-files-td44372.html I suppose to prevent this particular issue, but the WDR4900 may be using an old bootloader still affected. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I have been checking the contents of the dtb on the flash, this particular bit is quite revealing: ethernet@b0000 { #address-cells = <0x1>; #size-cells = <0x1>; device_type = "network"; model = "eTSEC"; compatible = "fsl,etsec2"; fsl,num_rx_queues = <0x8>; fsl,num_tx_queues = <0x8>; local-mac-address = [00 00 00 00 00 00]; ^^^^^^^^^^^^^^^^^ interrupt-parent = <0x2>; phy-handle = <0x3>; phy-connection-type = "rgmii-id"; ptimer-handle = <0x4>; queue-group@0 { #address-cells = <0x1>; #size-cells = <0x1>; reg = <0xb0000 0x1000>; rx-bit-map = <0xff>; tx-bit-map = <0xff>; interrupts = <0x1d 0x2 0x1e 0x2 0x22 0x2>; }; }; I also have been checking the live device map to find this: root@GHS-AP3:~# hexdump -C /proc/device-tree/soc@ffe00000/ethernet@b0000/local-mac-address 00000000 00 04 9f ef 01 01 |......| 00000006 root@GHS-AP3:~# hexdump -C /proc/device-tree/soc@ffe00000/ethernet@b1000/local-mac-address * root@GHS-AP3:~# hexdump -C /proc/device-tree/soc@ffe00000/ethernet@b2000/local-mac-address * My conclussion is that U-Boot most likely finds the device and (as no valid MAC-address is provided) falls back to the default MAC provided by the old code, the kernel then receives thee modified device map from U-Boot and assumes this is the correct MAC for the device despite it obviously isn't. This can be seen at target/linux/mpc85xx/patches-3.10/140-powerpc-85xx-tl-wdr4900-v1-support.patch The enetaddr is filled up by using the device tree data by the process_boot_dtb function and used by the platform_fixups function to set the eth0 address (by calling dt_fixup_mac_address_by_alias("ethernet0", enetaddr); ). But instead we should be used the device address which to my understanding is provided in the mtd. Signed-off-by: Bastian Bittorf <bittorf@bluebottle.com> SVN-Revision: 43074
2014-10-26 17:58:53 +00:00
. /lib/functions.sh
. /lib/functions/system.sh
mpc85xx: add user-space support for the TL-WDR4900 v1 Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35733
2013-02-21 19:20:34 +00:00
mpc85xx: migrate network setup to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47540
2015-11-20 23:52:31 +00:00
board_config_update
treewide: use the generic board_name function Use the generic function instead ot the target specific ones. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-05-12 20:36:07 +00:00
board=$(board_name)
mpc85xx: add user-space support for the TL-WDR4900 v1 Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35733
2013-02-21 19:20:34 +00:00
case "$board" in
mpc85xx: use the generic board detect Use the values populated by the generic board detect function. The first compatible from the device tree source file will be the board name in userspace. The model property from the device tree source file will be the model name. Change the board name where used in the userspace and drop the target specific board detect, to use the generic one. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-05-15 21:59:25 +00:00
aerohive,hiveap-330)
mpc85xx: Add Aerohive HiveAP-330 Access Point The following adds the Aerohive HiveAP-330 Access Point to LEDE under the mpc85xx/p1020 subtarget. Hardware: - SoC: Freescale P1020NSE2DFB - NAND: Intel JS28F512M29EWH 64MB - Memory: 2x ProMOS V59C1G01168QBJ3 128MB (Total of 256MB) - 2.4GHz WiFi: Atheros AR9390-AL1A - 5.0GHz WiFi: Atheros AR9390-AL1A - Eth1: Atheros AR8035-A PoE - Eth2: Atheros AR8035-A - TPM: Atmel AT97SC3204 - LED Driver: TI LP5521 Flashing: 1. Hook into UART (9600 baud) and enter U-Boot. You may need to enter a password of administrator or AhNf?d@ta06 if prompted. 2. Once in U-Boot, tftp boot the initramfs image: dhcp; tftpboot 0x1000000 192.168.1.101:lede- mpc85xx-p1020-hiveap-330-initramfs.zImage; tftpboot 0x6000000 192.168.1.101:lede-mpc85xx-p1020-hiveap-330.fdt; bootm 0x1000000 - 0x6000000; 3. Once booted, scp over the sysupgrade file and sysupgrade the device to flash LEDE to the NAND. sysupgrade /tmp/lede-mpc85xx-p1020-hiveap-330-sysupgrade.img Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
2017-09-30 16:14:58 +00:00
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
mpc85xx: use the generic board detect Use the values populated by the generic board detect function. The first compatible from the device tree source file will be the board name in userspace. The model property from the device tree source file will be the model name. Change the board name where used in the userspace and drop the target specific board detect, to use the generic one. Signed-off-by: Mathias Kresin <dev@kresin.me>
2017-05-15 21:59:25 +00:00
tplink,tl-wdr4900-v1)
board.d: merge ucidef_add_switch() and ucidef_add_switch_ports() This changes uci-defaults-new.sh, config_generate and all relevant board.d files in order combine ucidef_add_switch() and ucidef_add_switch_ports() into a single function. Also removes now superfluous enable and reset arguments. Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47721
2015-12-03 17:30:24 +00:00
ucidef_add_switch "switch0" \
mpc85xx: fix typo added in r47676 Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47681
2015-12-01 09:22:53 +00:00
"0@eth0" "2:lan:1" "3:lan:2" "4:lan:3" "5:lan:4" "1:wan"
cleanup ucidef_set_interface* usage - 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>
2016-09-10 07:46:14 +00:00
ucidef_set_interface_macaddr "wan" "$(mtd_get_mac_binary config 332)"
mpc85xx: add user-space support for the TL-WDR4900 v1 Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35733
2013-02-21 19:20:34 +00:00
;;
*)
ucidef_set_interfaces_lan_wan "eth0" "eth1"
;;
esac
mpc85xx: migrate network setup to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47540
2015-11-20 23:52:31 +00:00
board_config_flush
mpc85xx: add user-space support for the TL-WDR4900 v1 Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 35733
2013-02-21 19:20:34 +00:00
exit 0
Reference in a new issue Copy permalink