ltq-xdsl-app: drop esi call

The esi call was added to workaround a race condition between applying
a configured mac address to the wan interface and starting the protocol
(handler) as it was observed in a DHCP over ATM bridge configuration.

Martin Schiller, TDT GmbH was so kind to test with their local
infrastructure if the race condition still exists. The provided package
dumps captured behind the DSLAM shows that it doesn't. It was most
likely fixed with adding carrier support to the lantiq ptm/atm driver.

Signed-off-by: Mathias Kresin <dev@kresin.me>
This commit is contained in:
Mathias Kresin 2017-08-03 21:11:57 +02:00
parent e5e6045130
commit a94555ce24
3 changed files with 1 additions and 4 deletions

View File

@ -45,8 +45,6 @@ start() {
return 1
}
esi $(printf '%012X' $((1+0x$(tr -d : </sys/class/net/eth0/address))))
service_start /sbin/dsl_cpe_control -i${xtu} \
-n /sbin/dsl_notify.sh \
-f ${firmware}

View File

@ -28,7 +28,7 @@ define Package/ltq-vdsl-app
CATEGORY:=Network
TITLE:=Lantiq VDSL userland tool
URL:=http://www.lantiq.com/
DEPENDS:=@TARGET_lantiq_xrx200 +libpthread +librt +atm-esi
DEPENDS:=@TARGET_lantiq_xrx200 +libpthread +librt
endef
define Package/ltq-vdsl-app/description

View File

@ -7,5 +7,4 @@ for mod in $LOAD; do
grep -q "$mod " /proc/modules || insmod "$mod"
done
esi $(printf '%012X' $((1+0x$(tr -d : </sys/class/net/eth0/address))))
exec /sbin/vdsl_cpe_control "$@"