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

196 lines
4.9 KiB
Text
Raw Normal View History

brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
#!/bin/sh /etc/rc.common
# Copyright (C) 2006-2015 OpenWrt.org
. /lib/functions/system.sh
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
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
configure_by_vlanports() {
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
local vlan0ports="$(nvram get vlan0ports)"
local vlan1ports="$(nvram get vlan1ports)"
local vlan2ports="$(nvram get vlan2ports)"
local cpuport="$(swconfig dev switch0 help 2>/dev/null | sed -ne "s|.*cpu @ \([0-9]*\).*|\1|p")"
if [ "${vlan0ports:0:9}" = "0 1 2 3 8" -a "${vlan1ports:0:3}" = "4 8" -a ${cpuport:-0} -eq 8 ] || \
[ "${vlan1ports:0:9}" = "0 1 2 3 8" -a "${vlan2ports:0:3}" = "4 8" -a ${cpuport:-0} -eq 8 ] || \
[ "${vlan2ports:0:9}" = "0 1 2 3 8" -a "${vlan1ports:0:3}" = "4 8" -a ${cpuport:-0} -eq 8 ];
then
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "8@eth0"
brcm47xx: fix switch config for devices with WAN port 0 Commit r47866 dropped default values which were handling WAN interface at port 0. Fix it by handling 2 more cases on NVRAM values. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 47932
2015-12-18 15:27:16 +00:00
elif [ "${vlan0ports:0:9}" = "1 2 3 4 8" -a "${vlan1ports:0:3}" = "0 8" -a ${cpuport:-0} -eq 8 ] || \
[ "${vlan1ports:0:9}" = "1 2 3 4 8" -a "${vlan2ports:0:3}" = "0 8" -a ${cpuport:-0} -eq 8 ] || \
[ "${vlan2ports:0:9}" = "1 2 3 4 8" -a "${vlan1ports:0:3}" = "0 8" -a ${cpuport:-0} -eq 8 ];
then
ucidef_add_switch "switch0" \
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "8@eth0"
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
elif [ "${vlan0ports:0:9}" = "0 1 2 3 5" -a "${vlan1ports:0:3}" = "4 5" -a ${cpuport:-0} -eq 5 ] || \
[ "${vlan1ports:0:9}" = "0 1 2 3 5" -a "${vlan2ports:0:3}" = "4 5" -a ${cpuport:-0} -eq 5 ] || \
[ "${vlan2ports:0:9}" = "0 1 2 3 5" -a "${vlan1ports:0:3}" = "4 5" -a ${cpuport:-0} -eq 5 ];
then
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "5@eth0"
brcm47xx: fix switch config for devices with WAN port 0 Commit r47866 dropped default values which were handling WAN interface at port 0. Fix it by handling 2 more cases on NVRAM values. Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 47932
2015-12-18 15:27:16 +00:00
elif [ "${vlan0ports:0:9}" = "1 2 3 4 5" -a "${vlan1ports:0:3}" = "0 5" -a ${cpuport:-0} -eq 5 ] || \
[ "${vlan1ports:0:9}" = "1 2 3 4 5" -a "${vlan2ports:0:3}" = "0 5" -a ${cpuport:-0} -eq 5 ] || \
[ "${vlan2ports:0:9}" = "1 2 3 4 5" -a "${vlan1ports:0:3}" = "0 5" -a ${cpuport:-0} -eq 5 ];
then
ucidef_add_switch "switch0" \
"1:lan" "2:lan" "3:lan" "4:lan" "0:wan" "5@eth0"
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
else
brcm47xx: cosmetic fix in model detection In "brcm47xx: rework model detection" the file 01_detect was moved to 01_network, therefore also update the warning message in case everything fails. Signed-off-by: Paul Wassi <p.wassi@gmx.at>
2018-08-12 08:02:22 +00:00
logger -t "01_network" "Unable to determine network configuration"
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
ucidef_set_interface_lan "eth0"
fi
}
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
configure_by_boardnum() {
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
local boardnum="$1"
case "$boardnum" in
# WAP54G, Sitecom WL-105b
"2" | \
"1024")
ucidef_set_interface_lan "eth0"
;;
# Generic detection fallback
*)
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
configure_by_vlanports
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
;;
esac
}
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
configure_by_boardtype() {
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
local boardtype="$1"
local boardnum="$2"
case "$boardtype" in
"bcm94710r4")
ucidef_set_interfaces_lan_wan "eth0" "eth1"
;;
"0x0467")
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "5@eth0"
;;
"0x042f" | \
"0x0472")
# WL-500gP
if [ "$boardnum" = "45" ]; then
ucidef_add_switch "switch0" \
"0:wan" "1:lan" "2:lan" "3:lan" "4:lan" "5@eth0"
# Generic BCM94704
else
ucidef_set_interface_wan "eth1"
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:lan" "5@eth0"
# MAC addresses on 4704 tend to be screwed up. Add a workaround here
local mac="$(nvram get et0macaddr)"
local pat="[0-9a-fA-F][0-9a-fA-F]:[0-9a-fA-F][0-9a-fA-F]"
pat="$pat:[0-9a-fA-F][0-9a-fA-F]:[0-9a-fA-F][0-9a-fA-F]"
pat="$pat:[0-9a-fA-F][0-9a-fA-F]:[0-9a-fA-F][0-9a-fA-F]"
case "$mac" in
$pat)
ucidef_set_interface_macaddr "lan" "$mac"
ucidef_set_interface_macaddr "wan" "$(macaddr_add "$mac" 1)"
;;
esac
fi
;;
# Buffalo WBR-B11 and Buffalo WBR-G54
"bcm94710ap")
ucidef_set_interface_wan "eth1"
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:lan" "5@eth0"
;;
*)
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
configure_by_boardnum "$boardnum"
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
;;
esac
}
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
configure_by_model() {
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
local model="$1"
local boardtype="$2"
local boardnum="$3"
# Netgear WGT634U exception
if grep -sqE 'mtd0: 000(6|a)0000' /proc/mtd; then
ucidef_add_switch "switch0" \
brcm47xx: fix wgt634u port assignment, broken since openwrt r47866 Signed-off-by: Russell Senior <russell@personaltelco.net>
2016-05-07 09:32:13 +00:00
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "5@eth0"
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
return
fi
case "$model" in
"Asus WLHDD" | \
"Asus WL300G")
ucidef_set_interface_lan "eth1"
;;
"Asus WL330GE")
ucidef_add_switch "switch0" "4:lan" "5t@eth0"
;;
"Asus WL500G" | \
"Microsoft MN-700")
ucidef_set_interfaces_lan_wan "eth0" "eth1"
;;
brcm47xx: fix switch port mapping on Asus RT-N12 and RT-N16 models On Asus RT-N12 and RT-N16 models, the WAN and LAN4 ports are swapped in the initial switch configuration since the presets present in nvram appear to be wrong. Add special casing for these models to detect_by_model() in order to ensure a proper switch configuration. Fixes FS#502. Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2017-07-19 08:39:10 +00:00
"Asus RT-N12"* | \
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
"Asus WL500GP V2" | \
"Buffalo WHR-G125" | \
brcm47xx: fix switch port mapping on D-Link DIR-330 D-Link DIR-330 is clone of ASUS WL500GP2, by default conf the WAN port is eth1, it's not working cus eth1 not soldered and wan port function performs 5th port of the switch. Signed-off-by: Antony Black <gtrtfm@gmail.com>
2017-11-02 10:53:26 +00:00
"D-Link DIR-330" | \
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
"Motorola WR850G" | \
"Siemens SE505 V2")
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "5@eth0"
;;
"Asus WL700")
ucidef_add_switch "switch0" \
"0:wan" "1:lan" "2:lan" "3:lan" "4:lan" "5@eth0"
;;
brcm47xx: add switch port mapping to Asus WL-500W Switch ports 0..3 are connected to external ports LAN{1..4} in sequence, switch port 4 is not used, and switch port 5 is connected to the CPU. The WAN port is attached to the CPU's second network interface; it has no connection to the internal switch. Reuse the "Dell TrueMobile 2300" entry, which describes the same mapping. Signed-off-by: Mirko Parthey <mirko.parthey@web.de>
2018-05-22 19:23:36 +00:00
"Asus WL500W" | \
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
"Dell TrueMobile 2300")
ucidef_set_interface_wan "eth1"
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "5@eth0"
;;
brcm47xx: fix switch port mapping on Asus RT-N16 On the Asus RT-N16, the ports are not mapped the in the same way as the RT-N12. It is, however, the same as the Linksys E3000v1. Signed-off-by: Tim Thorpe <timfthorpe@gmail.com>
2017-10-10 14:48:54 +00:00
"Asus RT-N16"* | \
brcm47xx: add proper switch port mapping for WRT610Nv2 / Linksys E3000v1 Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 48511
2016-01-27 20:47:44 +00:00
"Linksys E3000 V1")
ucidef_add_switch "switch0" \
"0:wan" "1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "8@eth0"
;;
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
*)
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
configure_by_boardtype "$boardtype" "$boardnum"
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
;;
esac
}
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
model="$(cat /tmp/sysinfo/model)"
boardtype="$(board_name)"
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
case "$boardtype" in
*:*)
boardnum="${boardtype##*:}"
boardtype="${boardtype%:*}"
;;
esac
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
board_config_update
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
brcm47xx: rework model detection On brcm47xx boards, the model ID is the combination of the "boardtype" nvram variable and an optional supplemental "boardnum" variable while the human readable model name is usually exposed in the "machine" field of the /proc/cpuinfo file. Move the extraction of the board nvram variables and model name string into the 01_sysinfo file and rework the 01_detect board configuration script to solely use the prepared sysinfo values without performing own detection logic. As a consequence, we can drop the ucidef_set_board_id() and ucidef_set_model_name() invocations in favor to the generic behaviour which copies the /tmp/sysinfo/{board_name,model} values into the board.json "id" and "name" fields respectively. Since "01_detect" only contains network configuration logic after this change, move it to "01_network" and rename the contained "detect_by_xxx" functions to "configure_by_xxx" instead, to avoid potential confusion. Fixes FS#1576 Acked-by: Rafał Miłecki <rafal@milecki.pl> Signed-off-by: Jo-Philipp Wich <jo@mein.io>
2018-07-30 06:36:26 +00:00
configure_by_model "$model" "$boardtype" "$boardnum"
brcm47xx: migrate network config to board detection framework Signed-off-by: Jo-Philipp Wich <jow@openwrt.org> SVN-Revision: 47866
2015-12-11 15:19:43 +00:00
board_config_flush
Reference in a new issue Copy permalink