Difuse/difos
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
difos/target/linux/mvebu/base-files/etc/board.d/02_network

75 lines
1.7 KiB
Text
Raw Normal View History

automatically generate network config Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41381
2014-06-29 12:50:12 +00:00
#!/bin/sh
#
mvebu: add support for the Linksys WRT3200ACM (Rango) Signed-off-by: Imre Kaloz <kaloz@openwrt.org> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
2016-10-13 10:52:20 +00:00
# Copyright (C) 2014-2016 OpenWrt.org
# Copyright (C) 2016 LEDE-Project.org
automatically generate network config Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41381
2014-06-29 12:50:12 +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
mvebu: migrate led and network setup to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47541
2015-11-20 23:59:31 +00:00
mvebu: switch network and led config defaults to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47674
2015-11-30 10:43: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)
automatically generate network config Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41381
2014-06-29 12:50:12 +00:00
case "$board" in
mvebu: use device-tree board detection Convert whole target to Device Tree based board detection instead of identifying devices by dts file name. With this we can drop mvebu.sh translation script and rely on common method for model detection. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
2019-05-11 17:37:34 +00:00
cznic,turris-omnia)
ucidef_set_interface_lan "lan0 lan1 lan2 lan3 lan4"
ucidef_set_interface_wan "eth2"
;;
mvebu: fix regression for non-generic ESPRESSObin versions When targets for multiple ESPRESSObin devices were added, not all files were updated which means any ESPRESSObin version beside generic won't have proper networking, sysupgrade and uboot-env. This patch fixes the issue. * fixup network detection * fixup uboot-env * fixup platform.sh for sysupgrade Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
2019-06-07 13:50:50 +00:00
globalscale,espressobin|\
globalscale,espressobin-emmc|\
globalscale,espressobin-v7|\
globalscale,espressobin-v7-emmc)
mvebu: use device-tree board detection Convert whole target to Device Tree based board detection instead of identifying devices by dts file name. With this we can drop mvebu.sh translation script and rely on common method for model detection. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
2019-05-11 17:37:34 +00:00
ucidef_set_interfaces_lan_wan "lan0 lan1" "wan"
mvebu: Sort 02_network alphabetically Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
2017-07-12 02:21:09 +00:00
;;
mvebu: use device-tree board detection Convert whole target to Device Tree based board detection instead of identifying devices by dts file name. With this we can drop mvebu.sh translation script and rely on common method for model detection. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
2019-05-11 17:37:34 +00:00
linksys,caiman|\
linksys,cobra|\
linksys,mamba|\
linksys,rango|\
linksys,shelby|\
linksys,venom)
ar71xx/ipq806x/mediatek/mvebu: fix network defaults After "73d923e base-files: emit tagged switch configuration by default" some default network configurations are broken because the lan and wan ifnames are forcibly set to untagged netdevs. Adjust the offending set_interfaces_lan_wan() calls to use the proper tagged device names. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2017-02-07 07:55:46 +00:00
ucidef_set_interfaces_lan_wan "eth0.1" "eth1.2"
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" \
mvebu: switch network and led config defaults to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47674
2015-11-30 10:43:31 +00:00
"0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "5@eth0" "4:wan" "6@eth1"
automatically generate network config Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41381
2014-06-29 12:50:12 +00:00
;;
mvebu: use device-tree board detection Convert whole target to Device Tree based board detection instead of identifying devices by dts file name. With this we can drop mvebu.sh translation script and rely on common method for model detection. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
2019-05-11 17:37:34 +00:00
marvell,a385-db-ap)
ucidef_set_interfaces_lan_wan "eth0 eth1" "eth2"
;;
marvell,armada8040-mcbin)
ucidef_set_interfaces_lan_wan "eth0 eth1 eth3" "eth2"
;;
marvell,armada8040-db)
ucidef_set_interfaces_lan_wan "eth0 eth2 eth3" "eth1"
;;
marvell,armada7040-db)
ucidef_set_interfaces_lan_wan "eth0 eth2" "eth1"
;;
marvell,armada-3720-db)
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
marvell,axp-gp)
ucidef_set_interface_lan "eth0 eth1 eth2 eth3"
mvebu: add support for Turris Omnia Adds support for the Turris Omnia and builds an eMMC sysupgrade image in the same format as the SolidRun ClearFog. An initramfs image in the simple yet Omnia-specific 'medkit' image format is also built in order to ease the initial flashing process. Notable hardware support omissions are support for switching between SFP cage and copper PHY, and RGB LED control. Due to a current limitation of DSA, only 1/2 CPU switch uplinks are used. Specifications: - Marvell Armada 385 1.6GHz dual-core ARMv7 CPU - 1GB DDR3 RAM - 8GB eMMC Flash - 5x Gigabit LAN via Marvell 88E6176 Switch (2x RGMII CPU ports) - 1x switchable RJ45 (88E1514 PHY) / SFP SGMII WAN - 2x USB 3.0 - 12x dimmable RGB LEDs controlled by independent MCU - 3x Mini PCIe slots - Optional Compex WLE200N2 Mini PCIe AR9287 2x2 802.11b/g/n (2.4GHz) - Optional Compex WLE900VX Mini PCIe QCA9880 3x3 802.11ac (2.4 / 5GHz) - Optional Quectel EC20 Mini PCIe LTE modem Flash instructions: If the U-Boot environment has been modified previously (likely manually via serial console), first use serial to reset the default environment. => env default -a => saveenv Method 1 - USB 'medkit' image w/o serial - Copy openwrt-mvebu-turris-omnia-sysupgrade.img.gz and omnia-medkit-openwrt-mvebu-turris-omnia-initramfs.tar.gz to the root of a USB flash drive formatted with FAT32 / ext2/3/4 / btrfs / XFS. Note that the medkit MUST be named omnia-medkit*.tar.gz - Disconnect other USB devices from the Omnia and connect the flash drive to either USB port. - Power on the Omnia and hold down the rear reset button until 4 LEDs are illuminated, then release. - Wait approximately 2 minutes for the Turris Omnia to flash itself with the temporary image, during which LEDs will change multiple times. - Connect a computer to a LAN port of the Turris Omnia with a DHCP client - (if necessary) ssh-keygen -R 192.168.1.1 - ssh root@192.168.1.1 $ mount /dev/sda1 /mnt $ sysupgrade /mnt/openwrt-mvebu-turris-omnia-sysupgrade.img.gz - Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself and you can remove the flash drive. Method 2 - TFTP w/ serial - Extract omnia-medkit-openwrt-mvebu-turris-omnia-initramfs.tar.gz and copy dtb + zImage to your TFTP server (rename if desired) - Connect Turris Omnia WAN port to DHCP-enabled network with TFTP server - Connect serial console and interrupt U-Boot => dhcp => setenv serverip <tftp_server_ip_here> => tftpboot 0x01000000 zImage => tftpboot 0x02000000 dtb => bootz 0x01000000 - 0x02000000 - OpenWrt will now boot from ramdisk - Download openwrt-mvebu-turris-omnia-sysupgrade.img.gz to /tmp/ $ sysupgrade /tmp/openwrt-mvebu-turris-omnia-sysupgrade.img.gz - Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
2017-06-02 16:31:06 +00:00
;;
mvebu: uDPU: add sysupgrade support This patch adds sysupgrade, uboot-env and networking support for Methode uDPU device. Device features 4 partitions: ----------------------------------------- | boot | recovery | rootfs | misc | | (ext4) | (ext4) | (fsf2) | (f2fs) | _________________________________________ Idea was to use f2fs only but the u-boot currently lacks support so first 2 partition are ext4 to be u-boot readable, and this was a reason why custom build and sysupgrade sections were required. On the sysupgrade, boot and rootfs partitions are updated, firmare image and user configuration is saved on the misc partition and if the upgrade was successfull, recovery partition will be updated on after the reboot from preinit script. If the sysupgrade fails for any reason, device will fallback to recovery initramfs image. Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
2019-07-22 11:08:18 +00:00
methode,udpu)
mvebu: add initial support for uDPU board This adds initial support for micro-DPU (uDPU) board which is based on Armada-3720 SoC. micro-DPU is the single-port FTTdp distribution point unit made by Methode Electronics which offers complete modularity with replaceable SFP modules both for uplink and downlink (G.hn over twisted-pair, G.hn over coax, 1G and 2.5G Ethernet over Cat-5e cable). On-board features: - 512 MiB DDR3 - 2 x 2.5G SFP via HSGMII SERDES interface to the A3720 SoC - USB 2.0 Type-C connector - 4GB eMMC - ETSI TS 101548 reverse powering via twisted pair (RJ45) or coax (F Type) uDPU is intented to run on kernel 4.19 on newer due to the SFP and hardware support. Signed-off-by: Vladimir Vid <vladimir.vid@sartura.hr>
2019-06-19 19:00:03 +00:00
ucidef_set_interfaces_lan_wan "eth1" "eth0"
;;
mvebu: use device-tree board detection Convert whole target to Device Tree based board detection instead of identifying devices by dts file name. With this we can drop mvebu.sh translation script and rely on common method for model detection. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
2019-05-11 17:37:34 +00:00
solidrun,clearfog*a1)
mvebu: clearfog: document interface configuration Take explicit note of what physical ports eth{0,1,2} refer to. Also repair port assignment: At some point between 4.9.20 and 4.9.29 the numbering changed. Keep previous port assignment that was: LAN = SFP+Switch WAN = standalone ethernet Also use the same assignment for Clearfog-Base to avoid confusion. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
2017-04-24 14:52:31 +00:00
# eth0 is standalone ethernet
# eth1 is switch (-pro) or standalone ethernet (-base)
# eth2 is SFP
mvebu: clearfog: assign SFP port to WAN zone The single SFP port is meant for direct media access to WAN, such as VDSL2, GPON). While it could also be used for in-home fiber, it is much more likely that the LAN is standard ethernet, especially considering that SFP is the onmly port that can go beyond 1Gbps. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
2017-05-22 17:07:13 +00:00
ucidef_set_interfaces_lan_wan "eth1" "eth0 eth2"
mvebu: clearfog: document interface configuration Take explicit note of what physical ports eth{0,1,2} refer to. Also repair port assignment: At some point between 4.9.20 and 4.9.29 the numbering changed. Keep previous port assignment that was: LAN = SFP+Switch WAN = standalone ethernet Also use the same assignment for Clearfog-Base to avoid confusion. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
2017-04-24 14:52:31 +00:00
# if switch exists (clearfog-pro)
# switch port 5 is connected to eth1
mvebu: add switch config for clearfog pro Check for switch0 existance and add default switch config if found. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
2016-09-26 11:25:44 +00:00
swconfig list 2>&1 | grep -q switch0 && \
ucidef_add_switch "switch0" \
mvebu: clearfog: document interface configuration Take explicit note of what physical ports eth{0,1,2} refer to. Also repair port assignment: At some point between 4.9.20 and 4.9.29 the numbering changed. Keep previous port assignment that was: LAN = SFP+Switch WAN = standalone ethernet Also use the same assignment for Clearfog-Base to avoid confusion. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com>
2017-04-24 14:52:31 +00:00
"0:lan:5" "1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "5u@eth1" "6:lan:6"
mvebu: add ClearFog Base support Add support for SolidRun ClearFog Base board. The base model is a smaller version of ClearFog Pro without the DSA switch, replacing it with a second copper gigabit port, and only one PCIe socket. Signed-off-by: Marko Ratkaj <marko.ratkaj@sartura.hr>
2017-04-06 18:13:31 +00:00
;;
automatically generate network config Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41381
2014-06-29 12:50:12 +00:00
*)
ucidef_set_interface_lan "eth0"
;;
esac
mvebu: switch network and led config defaults to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47674
2015-11-30 10:43:31 +00:00
board_config_flush
automatically generate network config Signed-off-by: Imre Kaloz <kaloz@openwrt.org> SVN-Revision: 41381
2014-06-29 12:50:12 +00:00
exit 0
Reference in a new issue Copy permalink