[dahdi-commits] tzafrir: tools/trunk r6167 - in /tools/trunk: ./ xpp/

[SVN commits to the DAHDI project]

Author: tzafrir
Date: Mon Mar 16 10:01:14 2009
New Revision: 6167

URL: http://svn.digium.com/svn-view/dahdi?view=rev&rev=6167
Log:
dahdi.init: call xpp_sync a bit later.

xpp_sync needs to only be called after dahdi_cfg was run, because the
application of system.conf may change the priority of a PRI module span
(If it is a sync provider, "NT", priority is lower).

Also some documentation-only changes for xpp_sync.

Modified:
    tools/trunk/dahdi.init
    tools/trunk/xpp/README.Astribank
    tools/trunk/xpp/xpp_sync

Modified: tools/trunk/dahdi.init
URL: http://svn.digium.com/svn-view/dahdi/tools/trunk/dahdi.init?view=diff&rev=6167&r1=6166&r2=6167
==============================================================================
--- tools/trunk/dahdi.init (original)
+++ tools/trunk/dahdi.init Mon Mar 16 10:01:14 2009
@@ -97,9 +97,6 @@
 	# when locales are missing.
 	# No register all the devices if they didn't auto-register:
 	LC_ALL=C dahdi_registration on
-
-	# this one could actually be run after dahdi_cfg:
-	LC_ALL=C xpp_sync "$XPP_SYNC"
 }
 
 
@@ -223,6 +220,9 @@
 		$FXOTUNE -s || :
 	fi
 
+	# Set the right Astribanks ticker:
+	LC_ALL=C xpp_sync "$XPP_SYNC"
+
 	hpec_start
 	;;
   stop)

Modified: tools/trunk/xpp/README.Astribank
URL: http://svn.digium.com/svn-view/dahdi/tools/trunk/xpp/README.Astribank?view=diff&rev=6167&r1=6166&r2=6167
==============================================================================
--- tools/trunk/xpp/README.Astribank (original)
+++ tools/trunk/xpp/README.Astribank Mon Mar 16 10:01:14 2009
@@ -1112,6 +1112,19 @@
   options xpp zap_autoreg=1
 
 
+Astribanks Synchronization Source
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+If there is more than one Astribank on the system, all the Astribanks
+keep their clock in sync. Optionally the Astribanks can synchronize
+their clock to the master DAHDI device (in case it is a different DAHDI
+device). Normally you just use the default init.d script or run
+explicitly:
+
+  xpp_sync auto
+
+(For now see the man page of xpp_sync for more information)
+
+
 DAHDI And Above
 ^^^^^^^^^^^^^^^
 From here you get a standard DAHDI span. The next step is to configure

Modified: tools/trunk/xpp/xpp_sync
URL: http://svn.digium.com/svn-view/dahdi/tools/trunk/xpp/xpp_sync?view=diff&rev=6167&r1=6166&r2=6167
==============================================================================
--- tools/trunk/xpp/xpp_sync (original)
+++ tools/trunk/xpp/xpp_sync Mon Mar 16 10:01:14 2009
@@ -200,14 +200,27 @@
 I<auto>, but it is possible to override that parameter (e.g: set it to
 I<dahdi>) through the value of XPP_SYNC in /etc/dahdi/init.conf .
 
+It should be run after dahdi_cfg as the configuration of a PRI module
+is set from it. It must be run after dahdi_registration as it only
+handles XPDs that are registered spans.
+
 =head1 FILES
 
 =over
 
+=item /sys/bus/astribanks/drivers/xppdrv/sync
+
+The low-level interface used by xpp_sync to set / read registration.
+
 =item /proc/xpp/sync
 
+(Deprecated: no longer supported)
 xpp_sync is essentially a nicer interface to /proc/xpp/sync . That file
 shows the current xpp sync master (and in what format you need to write
 to it to set the master).
 
+=head1 SEE ALSO
+
+dahdi_registration(1), dahdi_cfg(1), README.Astribank
+
 =back