As I mentioned earlier I am already running with very minimal configuration. My control process parameters list looks like this:
/sbin/vdsl_cpe_control -i -n /sbin/dsl_notify.sh -f /lib/firmware/vdsl.bin -A /lib/firmware/vdsl.scr -i is required, but actual initialization bits are not (in my case). As far as I know this selects operation mode of the firmware (VDSL/ADSL). Not sure if firmware can autodetect this, or if it just defaults to VDSL. I am passing -A vdsl autoboot script just for peace of mind (it was included with firmware). My connection seems to work exactly the same without it. We indeed could use some more testing. Preferably not only on different annexes but different ISPs as well. On Sat, Jun 6, 2015 at 1:49 PM, Martin Blumenstingl <martin.blumensti...@googlemail.com> wrote: > On Fri, Jun 5, 2015 at 4:56 AM, Aleksander Wałęski <olewa...@gmail.com> wrote: >> Try playing with /etc/init.d/dsl_control when you'll have a moment to >> spare to see if all parameters it passes to control application are >> necessary. > It seems that the lowlevel configuration is indeed not required > anymore. > Removing the "autoboot" configurations also did not make any > difference. > DSL is still coming up fine, and still syncing at the same speed. > > I have updated my patch yet again: [0] > > Maybe you can give it a go again with your VDSL connection? > Someone testing with ADSL and Annex A would be good as > well. > > > [0] https://gist.github.com/xdarklight/2986587133d97892a4b3 _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
