bcm47xx: use eth0 for switch name

This fixes some strange problems with tg3. I assume that the Ethernet
driver was not brought up if the switch was named switch0.

This was reported and tested by ernesto (Faulp3lz).

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>

SVN-Revision: 41042
This commit is contained in:
Hauke Mehrtens 2014-06-07 15:41:41 +00:00
parent dec0d7f025
commit 9dc5fb9103
1 changed files with 3 additions and 3 deletions

View File

@ -224,14 +224,14 @@ start() {
eval "$network_defs"
[ -n "$vlan1ports" -o -n "$vlan2ports" ] && {
local cfg=`ucidef_add_switch "switch0" 1 1`
local cfg=`ucidef_add_switch "eth0" 1 1`
[ -n "$cfg" ] && uci rename network.$cfg=eth0
[ -n "$vlan1ports" ] && {
cfg=`ucidef_add_switch_vlan "switch0" 1 "$vlan1ports"`
cfg=`ucidef_add_switch_vlan "eth0" 1 "$vlan1ports"`
[ -n "$cfg" ] && uci rename network.$cfg=eth0_1
}
[ -n "$vlan2ports" ] && {
cfg=`ucidef_add_switch_vlan "switch0" 2 "$vlan2ports"`
cfg=`ucidef_add_switch_vlan "eth0" 2 "$vlan2ports"`
[ -n "$cfg" ] && uci rename network.$cfg=eth0_2
}
}