r47933 revealed that the driver/app in combination with the chosen
firmware does a good job in selecting a working xtse.
Use this probing mode if no annex is specified.
Signed-off-by: Mathias Kresin <open...@kresin.me>
---
Since a predefined annex isn't required, what about using 'auto' when
creating the initial config?
Any opinions?
package/network/config/ltq-vdsl-app/files/dsl_control | 3 ---
1 file changed, 3 deletions(-)
diff --git a/package/network/config/ltq-vdsl-app/files/dsl_control
b/package/network/config/ltq-vdsl-app/files/dsl_control
index 9bd4eb5..8578c0b 100644
--- a/package/network/config/ltq-vdsl-app/files/dsl_control
+++ b/package/network/config/ltq-vdsl-app/files/dsl_control
@@ -35,8 +35,6 @@ xtse_adsl_b="10_00_10_00_00_04_00_07"
# G.993.2 Annex A/B/C
xtse_adsl_j="10_00_10_40_00_04_01_07"
-xtse_vdsl="00_00_00_00_00_00_00_07"
-
service_triggers() {
procd_add_reload_trigger network
}
@@ -68,7 +66,6 @@ start_service() {
esac
eval "xtse=\"\${xtse_xdsl_$annex}\""
- [ -z "${xtse}" ] && xtse=$xtse_vdsl
[ -z "${firmware}" ] && firmware=/lib/firmware/vdsl.bin
[ -f "${firmware}" ] || {
--
1.9.1
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
