xpp: a massive backport from DAHDI. From Xorcom branch-rel-6839-r6908 .

Sun Mar  1 2009 Oron Peled <oron@actcom.co.il> - xpp.r6795
  * Fix cases where the command_queue overflowed during initialization.
    - Also add a 'command_queue_length' parameter to xpp.ko
  * More migrations to sysfs:
    - Add a 'transport' attribute to our astribank devices which
      points to the usb device we use. E.g:
       /sys/bus/astribanks/devices/xbus-00/transport is symlinked to
       ../../../../../../devices/pci0000:00/0000:00:10.4/usb5/5-4
    - Move /proc/xpp/XBUS-??/XPD-??/span to
      /sys/bus/xpds/devices/??:?:?/span
    - Migrate from /proc/xpp/sync to:
      /sys/bus/astribanks/drivers/xppdrv/sync
    - New 'offhook' attribute in:
      /sys/bus/xpds/devices/??:?:?/offhook
  * PRI: change the "timing" priority to match the convention used by
         other PRI cards -- I.e: lower numbers (not 0) have higher
	 priority.
  * FXO: 
    - Power denial: create two module parameters instead of hard-coded
      constants (power_denial_safezone, power_denial_minlen).
      For sites that get non-standard power-denial signals from central
      office on offhook.
    - Don't hangup on power-denial, just notify Dahdi and wait for
    - Fix caller-id detection for the case central office sends it before
      first ring without any indication before.
      Asterisk's desicion.
Mon, Dec  8 2008 Oron Peled <oron@actcom.co.il> - xpp.r6430
  * PRI:
    - Match our span clocking priorities (in system.conf)
      to Digium -- this is a reversal of the previous state.
      Now lower numbers (greater than 0) are better.
    - Synchronization fixes for PRI ports other than 0.
    - Fix T1 CRC for some countries (e.g: China).
  * FXS: fix bug in VMWI detection if using old asterisk
    which does not provide ZT_VMWI ioctl().
  * FXO:
    - Improve caller_id_style module parameter. This provide a workaround
      for countries that send this information without any notification
      (reverse polarity, ring, etc.)
    - Don't force on-hook upon power-denial. So, loopstart devices
      would ignore these as expected.
  * Implement a flow-control to prevent user space (init_card_* scripts)
    from pressuring our command queue.


git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@4631 5390a7c7-147a-4af0-8ec9-7488f05a26cb

1 files changed, 23 insertions, 38 deletions

diff --git a/kernel/xpp/utils/astribank_hook b/kernel/xpp/utils/astribank_hook
index 8dd13c9..9510f7b 100755
--- a/kernel/xpp/utils/astribank_hook
+++ b/kernel/xpp/utils/astribank_hook
@@ -1,57 +1,42 @@
 #! /bin/sh
 
-# This is an example of an Astribank device hook. The xpp.rules file
-# calls /usr/share/zaptel/astribank_hook after a new Astribank is ready 
-# and after and old Astribank device has been destroyed.
-#
-
-set -e
-
 me=`basename $0`
-INIT_DIR=`dirname $0`
-XPP_BASE=/proc/xpp
-export XPP_BASE
-LOGGER="logger -s -t $me"
-
-ZAPTEL_BOOT_DEBIAN=${ZAPTEL_BOOT_DEBIAN:-/etc/default/zaptel}
-ZAPTEL_BOOT_FEDORA=${ZAPTEL_BOOT_FEDORA:-/etc/sysconfig/zaptel}
-
-# read default configuration from /etc/default/zaptel
-if [ -r $ZAPTEL_BOOT_DEBIAN ]; then . $ZAPTEL_BOOT_DEBIAN; fi
-if [ -r $ZAPTEL_BOOT_FEDORA ]; then . $ZAPTEL_BOOT_FEDORA; fi
-
-if [ "$ASTRIBANK_HOOK_DISABLED" != '' ]; then
-	$LOGGER -p kern.info "Exiting... ASTRIBANK_HOOK_DISABLED"
-	exit 0
-fi
+dir=`dirname $0`
+LOGGER="logger -i -t '$me'"
 
 # Always redirect stderr somewhere, otherwise the shell script will die
 # when it tries to do I/O related stuff on closed file descriptor.
 # Our default is to throw it down the bit-bucket.
 #exec 2> /dev/console
 ## If you wish to trace this script:
-#exec 2> "/tmp/astribank_hook_$XBUS_NAME"
+#exec 2> "/tmp/${me}_$XBUS_NAME" 1>&2
 
-# Maybe add some logging
-#$LOGGER -p kern.info "$0: $ACTION: $*."
+PATH="$dir:/usr/sbin:/sbin:/usr/bin:/bin"
+
+set -e
+
+echo "starting($ACTION): '$*'" | $LOGGER
 
 case "$ACTION" in
 add)
-	# An Astribank was added and is initialized and ready.
-	# Put your shell commands bellow
-	:
 	;;
 remove)
-	# An Astribank was Removed.
-	# Put your shell commands bellow
-	# You should not access /proc/xpp/... or run related utilities
-	# like xpp_sync, since this is likely to cause very bad race
-	# conditions during driver removal.
-	:
 	;;
-*)
+online)
+	if [ -x "$dir/twinstar_hook" ]; then
+		"$dir/twinstar_hook"
+	fi
+	;;
+offline)
+	if [ -x "$dir/twinstar_hook" ]; then
+		"$dir/twinstar_hook"
+	fi
 	;;
+*)
+	echo "$0: Unknown ACTION='$ACTION'" | $LOGGER
+	echo "$0: ARGS='$*'" | $LOGGER
+	echo "$0: ENV:" | $LOGGER
+	env | $LOGGER
+	exit 1
 esac
 
-# Maybe add some logging
-#$LOGGER -p kern.info "$0: Done: $ACTION: $*."