[dahdi-commits] dahdi/linux.git branch "master" updated.
SVN commits to the DAHDI project
dahdi-commits at lists.digium.com
Thu Apr 11 10:01:21 CDT 2013
branch "master" has been updated
via be904538c78b16f24dff0fab2af717695926ad80 (commit)
via 76dda315336b48b557bf45a2c5669bb8cd794cef (commit)
via 8f07b4e019de1b061c84e8c6c6f8ef20f94ccc7e (commit)
via 9c031f66a010a4814c1e3907d231fd5af3ea5f54 (commit)
from 300446b1a1c8e17eb0cd12c0bb837e61c4c20a28 (commit)
Summary of changes:
README | 225 +++++++++++++++++++++++++++++++++++++++++++++++++---------------
1 file changed, 175 insertions(+), 50 deletions(-)
- Log -----------------------------------------------------------------
commit be904538c78b16f24dff0fab2af717695926ad80
Author: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
Date: Sun Mar 31 14:08:08 2013 +0300
README: xpp: xpd_fxo param use_polrev_firmware
Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
diff --git a/README b/README
index 42d22bf..5f6087b 100644
--- a/README
+++ b/README
@@ -624,6 +624,16 @@ Minimum interval (msec) for detection of battery off (as opposed to e.g.
a temporary power denial to signal a hangup). Defaults to 1000. As with
battery_threshold above, there's normally no need to tweak it.
+==== use_polrev_firmware
+(xpd_fxo)
+
+Enable (1, default) or disable (0) support for polarity reversal
+detection in the hardware. Only has effect with PIC_TYPE_2.hex rev. >=
+11039 and with the initialization changes (init_card_2_30) in rev.
+949aa49.
+
+This parameter is read-only. It cannot be changed at run-time.
+
Internals
---------
commit 76dda315336b48b557bf45a2c5669bb8cd794cef
Author: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
Date: Sun Mar 31 14:08:07 2013 +0300
README: xpp: xpd_fxo: new value of caller_id_style
Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
diff --git a/README b/README
index 4a72a31..42d22bf 100644
--- a/README
+++ b/README
@@ -604,7 +604,9 @@ bandwidth). This parameter allows fine-tuning the behaviour here:
* 0 (default) - Don't pass extra PCM when on-hook.
* 1 ETSI-FSK: Wait for polarity reversal to come before a ring and
then start passing PCM until the caller ID has been passed.
-* 2 Always: Always pass PCM.
+* 2 ETSI-DTMF: Always pass PCM and generate a DTMF if polarity reversal is
+ detected before ring.
+* 3 Passthrough: Always pass PCM as-is.
This parameter is read-only. It cannot be changed at run-time.
commit 8f07b4e019de1b061c84e8c6c6f8ef20f94ccc7e
Author: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
Date: Sun Mar 31 14:08:06 2013 +0300
Copy xpp module docs from README.Astribank
Copy xpp module documenttation from README.Astribank in dahdi-tools.
Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
diff --git a/README b/README
index 1f49b69..4a72a31 100644
--- a/README
+++ b/README
@@ -493,6 +493,10 @@ in README.Astribank .
logs.
* 128: DEVICES - Device instantiation, destruction and such.
* 256 - COMMANDS - Protocol commands. Tends to flood logs.
+ +
+ +
+ The script xpp_debug in the source tree can help settting them at run
+ time.
=== deftaps
(dahdi)
@@ -516,6 +520,108 @@ The default is 512.
See <<_span_assignments,Span Assignments>> below.
+XPP (Astribank) module parameters
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+==== debug
+(all modules) - see above.
+
+==== dahdi_autoreg
+(xpp)
+
+Register spans automatically (1) or not (0). Default: 0.
+Setting it simplifies operations with a single Astribank and no other
+DAHDI hardware. However if you have such systems, automatic
+registration can cause the order of spans to be unpredictable.
+The standard startup scripts use 'dahdi_registration on' instead of this.
+
+==== initdir
+(xpp)
+
+This is the directory containing the initialization scripts.
+The default is /usr/share/dahdi .
+Setting this value could be useful if that location is inconvenient for you.
+
+==== rx_tasklet
+(xpp)
+
+Enable (1) or disable (0) doing most of the packets processing in
+separate tasklets. This should probably help on higher-end systems with
+multiple Astribanks.
+
+==== vmwi_ioctl
+(xpd_fxs)
+
+Does userspace support VMWI notification via ioctl? Default: 1 (yes).
+
+Disable this (0) to have the driver attempt to detect the voicemail
+message waiting indication status for this port from FSK messages
+userspace (Asterisk) sends. Set the ports to use AC neon-lamp style
+message waiting indication. The detection from the FSK messages takes
+extra CPU cycles but is required with e.g. Asterisk < 1.6.0 .
+
+Also note that in order for this parameter to take effect, it must be
+set before the span is registered. This practically means that it
+should be set through modprobe.d files.
+
+See also Voicemail Indication in README.Astribank.
+
+==== usb1
+(xpp_usb)
+
+Enable (1) or disable (0) support of USB1 devices. Disabled by default.
+
+USB1 devices are not well-tested. It seems that they don't work at all
+for Astribank BRI. Generally they should work with the current code, but
+we expect the voice quality issues. Hence we would like to make it
+very clear that you if you have a USB1 port (rather than a USB2 one, as
+recommended) you will have to take an action to enable the device.
+
+==== poll intervals
+(various)
+
+There are various values which the driver occasionally polls the
+device for. For instance, the parameter poll_battery_interval for
+xpd_fxo to poll the battery, in order to know if the telco line is
+actually connected.
+
+The value of those parameters is typically a number in milliseconds.
+0 is used to disable polling. Under normal operation there should be
+no reason to play with those parameters.
+
+==== dtmf_detection
+(xpd_fxs)
+
+Enable (1) or disable (0) support of hardware DTMF detection by the
+Astribank.
+
+==== caller_id_style
+(xpd_fxo)
+
+Various types of caller ID signalling styles require knowing the PCM
+even when the line is on-hook (which is usually a waste of CPU and
+bandwidth). This parameter allows fine-tuning the behaviour here:
+
+* 0 (default) - Don't pass extra PCM when on-hook.
+* 1 ETSI-FSK: Wait for polarity reversal to come before a ring and
+ then start passing PCM until the caller ID has been passed.
+* 2 Always: Always pass PCM.
+
+This parameter is read-only. It cannot be changed at run-time.
+
+==== battery_threshold
+(xpd_fxo)
+
+Minimum voltage that shows there is battery. Defaults to 3. Normally you
+should not need to change this, unless dealing with a funky PSTN
+provider.
+
+==== battery_debounce
+(xpd_fxo)
+
+Minimum interval (msec) for detection of battery off (as opposed to e.g.
+a temporary power denial to signal a hangup). Defaults to 1000. As with
+battery_threshold above, there's normally no need to tweak it.
+
Internals
---------
commit 9c031f66a010a4814c1e3907d231fd5af3ea5f54
Author: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
Date: Sun Mar 31 14:08:05 2013 +0300
README: subsections for module parameters docs
Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
diff --git a/README b/README
index 67265c0..1f49b69 100644
--- a/README
+++ b/README
@@ -445,57 +445,17 @@ reside directly under /sys/module/'module_name' .
Useful module parameters:
-debug (most modules)::
- Sets debug mode / debug level. With most modules 'debug' can be either
- disabled (0, the default value) or enabled (any other value).
- +
- +
- wctdm and wcte1xp print several extra debugging messages if the value
- of debug is more than 1.
- +
- +
- Some modules have "debugging flags" bits - the value of debug is a
- bitmask and several messages are printed if some bits are set:
- - wctdm24xxp:
- * 1: DEBUG_CARD
- * 2: DEBUG_ECHOCAN
- - wct4xxp:
- * 1: DEBUG_MAIN
- * 2: DEBUG_DTMF
- * 4: DEBUG_REGS
- * 8: DEBUG_TSI
- * 16: DEBUG_ECHOCAN
- * 32: DEBUG_RBS
- * 64: DEBUG_FRAMER
- - xpp: See also README.Astribank:
- * 1: GENERAL - General debug comments.
- * 2: PCM - PCM-related messages. Tend to flood logs.
- * 4: LEDS - Anything related to the LEDs status control. The driver
- produces a lot of messages when the option is enabled.
- * 8: SYNC - Synchronization related messages.
- * 16: SIGNAL - DAHDI signalling related messages.
- * 32: PROC - Messages related to the procfs interface.
- * 64: REGS - Reading and writing to chip registers. Tends to flood
- logs.
- * 128: DEVICES - Device instantiation, destruction and such.
- * 256 - COMMANDS - Protocol commands. Tends to flood logs.
-
-deftaps (dahdi)::
- The default size for the echo canceller. The number is in "taps", that
- is "samples", 1/8 ms. The default is 64 - for a tail size of 8 ms.
- +
- +
- Asterisk's chan_dahdi tends to pass its own value anyway, with a
- different default size. So normally setting this doesn't change
- anything.
-
-max_pseudo_channels (dahdi)::
- The maximum number of pseudo channels that dahdi will allow userspace to
- create. Pseudo channels are used when conferencing channels together.
- The default is 512.
-
-auto_assign_spans (dahdi)::
- See <<_span_assignments,Span Assignments>> below.
+=== debug
+(most modules)
+
+Sets debug mode / debug level. With most modules 'debug' can be either
+disabled (0, the default value) or enabled (any other value).
+
+wctdm and wcte1xp print several extra debugging messages if the value
+of debug is more than 1.
+
+Some modules have "debugging flags" bits - the value of debug is a
+bitmask and several messages are printed if some bits are set:
To get a list of parameters supported by a module, use
@@ -503,13 +463,60 @@ To get a list of parameters supported by a module, use
Or, for a module you have just built:
- modinfo ./module_name.ko
+ modinfo ./drivers/dahdi/module_name.ko
For the xpp modules this will also include the description and default
value of the module. You can find a list of useful xpp module parameters
in README.Astribank .
+- wctdm24xxp:
+ * 1: DEBUG_CARD
+ * 2: DEBUG_ECHOCAN
+- wct4xxp:
+ * 1: DEBUG_MAIN
+ * 2: DEBUG_DTMF
+ * 4: DEBUG_REGS
+ * 8: DEBUG_TSI
+ * 16: DEBUG_ECHOCAN
+ * 32: DEBUG_RBS
+ * 64: DEBUG_FRAMER
+- xpp: See also README.Astribank:
+ * 1: GENERAL - General debug comments.
+ * 2: PCM - PCM-related messages. Tend to flood logs.
+ * 4: LEDS - Anything related to the LEDs status control. The driver
+ produces a lot of messages when the option is enabled.
+ * 8: SYNC - Synchronization related messages.
+ * 16: SIGNAL - DAHDI signalling related messages.
+ * 32: PROC - Messages related to the procfs interface.
+ * 64: REGS - Reading and writing to chip registers. Tends to flood
+ logs.
+ * 128: DEVICES - Device instantiation, destruction and such.
+ * 256 - COMMANDS - Protocol commands. Tends to flood logs.
+
+=== deftaps
+(dahdi)
+
+The default size for the echo canceller. The number is in "taps", that
+is "samples", 1/8 ms. The default is 64 - for a tail size of 8 ms.
+
+Asterisk's chan_dahdi tends to pass its own value anyway, with a
+different default size. So normally setting this doesn't change
+anything.
+
+=== max_pseudo_channels
+(dahdi)
+
+The maximum number of pseudo channels that dahdi will allow userspace to
+create. Pseudo channels are used when conferencing channels together.
+The default is 512.
+
+=== auto_assign_spans
+(dahdi)
+
+See <<_span_assignments,Span Assignments>> below.
+
+
Internals
---------
DAHDI Device Files
-----------------------------------------------------------------------
--
dahdi/linux.git
More information about the dahdi-commits
mailing list