[dahdi-commits] sruffell: tag linux/2.4.0-rc1 r9155 - /linux/tags/2.4.0-rc1/
SVN commits to the DAHDI project
dahdi-commits at lists.digium.com
Wed Aug 18 08:22:31 CDT 2010
Author: sruffell
Date: Wed Aug 18 08:22:27 2010
New Revision: 9155
URL: http://svnview.digium.com/svn/dahdi?view=rev&rev=9155
Log:
Importing files for 2.4.0-rc1 release.
Added:
linux/tags/2.4.0-rc1/.version (with props)
linux/tags/2.4.0-rc1/ChangeLog (with props)
Added: linux/tags/2.4.0-rc1/.version
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.4.0-rc1/.version?view=auto&rev=9155
==============================================================================
--- linux/tags/2.4.0-rc1/.version (added)
+++ linux/tags/2.4.0-rc1/.version Wed Aug 18 08:22:27 2010
@@ -1,0 +1,1 @@
+2.4.0-rc1
Propchange: linux/tags/2.4.0-rc1/.version
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: linux/tags/2.4.0-rc1/.version
------------------------------------------------------------------------------
svn:keywords = none
Propchange: linux/tags/2.4.0-rc1/.version
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added: linux/tags/2.4.0-rc1/ChangeLog
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.4.0-rc1/ChangeLog?view=auto&rev=9155
==============================================================================
--- linux/tags/2.4.0-rc1/ChangeLog (added)
+++ linux/tags/2.4.0-rc1/ChangeLog Wed Aug 18 08:22:27 2010
@@ -1,0 +1,3221 @@
+2010-08-18 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux version 2.4.0-rc1 released.
+
+2010-08-17 17:15 +0000 [r9144-9145] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wcte12xp/base.c: wcte12xp: Clean up -vpm workqueue
+ if there is not a VPMADT032 installed. DAHDI-681.
+
+ * drivers/dahdi/wcte12xp/base.c,
+ drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+ drivers/dahdi/voicebus/voicebus.c,
+ drivers/dahdi/wctdm24xxp/base.c,
+ drivers/dahdi/wcte12xp/wcte12xp.h,
+ drivers/dahdi/voicebus/voicebus.h: wcte12xp, wctdm24xxp: Add
+ compile time option CONFIG_VOICEBUS_ECREFERENCE. Add compile time
+ option to improve the reference signal provided to software echo
+ cancelers. The intent here is for this functionality to become
+ the default behavior but more testing and work on the edge cases
+ is needed. It's being brought in now as a compile time option
+ since there have been reports that it helps in some environments.
+ Instead of using two buffers, which means that at best we're two
+ milliseconds behind, use a circular buffer where audio data is
+ written on the transmit side and read on the receive path. In
+ this way high latency values will not interfere with the
+ operation of software echo cancelers. DAHDI-291. DAHDI-387. This
+ work was originally on:
+ http://svn.asterisk.org/svn/dahdi/linux/team/sruffell/improved_ecreference@9143
+ and includes a generic kfifo replacement by Matt Fredrickson.
+
+2010-08-16 21:43 +0000 [r9143] Russ Meyerriecks <rmeyerreicks at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Set the companding
+ mode on the analog ports in fixup. Fixes a regression from 9101
+ 'wctdm24xxp: Added "auto" companding option' where the analog
+ modules were not defaulted to alaw properly when a digital module
+ is on an Hx8. This could result in very poor audio since the
+ modules were providing ulaw data, but dahdi-base believed the
+ audio was in alaw when converting to signed linear.
+
+2010-08-16 18:43 +0000 [r9142] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi_transcode.c: dahdi_transcode: No need for
+ ioctl when unlocked_ioctl is available More work to kill the BKL
+ (Big Kernel Lock)
+ http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=10041d2d14688e207d0d829095147aa82c1f211b
+
+2010-08-13 19:38 +0000 [r9130-9138] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/oct612x/include/oct6100api/oct6100_mixer_pub.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_tsst_inst.h
+ (added), drivers/dahdi/oct612x/apilib/bt (added),
+ drivers/dahdi/oct612x/include/apilib/octapi_largmath.h (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tone_detection.c
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_miscellaneous.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_playout_buf_pub.h
+ (added), drivers/dahdi/oct612x/include/digium_unused.h (added),
+ drivers/dahdi/oct612x/include/apilib/octapi_llman.h (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.c
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_events_inst.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_debug_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_tlv_inst.h
+ (added), drivers/dahdi/oct612x/include/octtypewin.h (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_phasing_tsst_inst.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_memory.c
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_playout_buf_priv.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_chip_stats_pub.h
+ (added), drivers/dahdi/oct612x/include/octosdependant.h (added),
+ drivers/dahdi/oct612x/include/octrpc/oct6100_rpc_protocol.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_chip_open_pub.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_adpcm_chan_inst.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_phasing_tsst_pub.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_chip_stats_priv.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_channel_pub.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_tone_detection_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_mixer.c
+ (added), drivers/dahdi/oct612x/get_discards (added),
+ drivers/dahdi/oct612x/include/apilib/octapi_bt0.h (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_apimi
+ (added), drivers/dahdi/oct612x/apilib/llman (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsst.c
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_interrupts_priv.h
+ (added), drivers/dahdi/oct612x/apilib/bt/octapi_bt0_private.h
+ (added), drivers/dahdi/oct612x/include/oct6100api/oct6100_apimi.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.c
+ (added), drivers/dahdi/oct612x/include/octdef.h (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tsi_cnct.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_tsi_cnct_inst.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_api_inst.h
+ (added), drivers/dahdi/oct612x/include (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_tsst_priv.h
+ (added), drivers/dahdi/oct612x/apilib/llman/octapi_llman.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_tsi_cnct_pub.h
+ (added), drivers/dahdi,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_miscellaneous_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_events_priv.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_mixer_inst.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_tlv_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_phasing_tsst_priv.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_adpcm_chan_pub.h
+ (added), drivers/dahdi/oct612x/octdeviceapi (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_memory_priv.h
+ (added), drivers/dahdi/oct612x (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_adpcm_chan_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.c
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_conf_bridge_inst.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_remote_debug_inst.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_chip_open_inst.h
+ (added), drivers/dahdi/oct612x/include/octrpc (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_channel_inst.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_tone_detection_pub.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_events_pub.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_errors.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_apimi/oct6100_mask_interrupts.c
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_tsi_cnct_priv.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_debug_inst.h
+ (added), drivers/dahdi/oct612x/apilib/largmath (added),
+ drivers/dahdi/oct612x/apilib (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_interrupts_pub.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_playout_buf_inst.h
+ (added), drivers/dahdi/oct612x/octasic-helper (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_debug_pub.h
+ (added), drivers/dahdi/oct612x/include/octrpc/rpc_protocol.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_remote_debug.c
+ (added), drivers/dahdi/oct612x/include/oct6100api (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_chip_stats_inst.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api
+ (added), drivers/dahdi/oct612x/apilib/bt/octapi_bt0.c (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_tone_detection_inst.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_mixer_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_version.h
+ (added), drivers/dahdi/oct612x/Makefile (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_apiud.h (added),
+ drivers/dahdi/oct612x/include/octtypevx.h (added),
+ drivers/dahdi/oct612x/apilib/largmath/octapi_largmath.c (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.c
+ (added), drivers/dahdi/oct612x/include/octmac.h (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_remote_debug_pub.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_conf_bridge_pub.h
+ (added), drivers/dahdi/oct612x/include/apilib (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_adpcm_chan.c
+ (added), drivers/dahdi/oct612x/include/oct6100api/oct6100_api.h
+ (added), drivers/dahdi/oct612x/octdeviceapi/oct6100api (added),
+ drivers/dahdi/oct612x/apilib/llman/octapi_llman_private.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_user.c
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_interrupts_inst.h
+ (added),
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_defines.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_conf_bridge_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_remote_debug_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_chip_open_priv.h
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_debug.c
+ (added),
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_channel_priv.h
+ (added), drivers/dahdi/oct612x/include/octtype.h (added),
+ drivers/dahdi/oct612x/test.c (added): wct4xxp: Move 'oct612x'
+ from an svn:external directly into dahdi-linux. From
+ http://svn.digium.com/svn/octasic_api/oct612x/tags/PR49-03/software@44
+ This is only currently maintained as part of DAHDI linux so it
+ makes sense to have it directly in DAHDI linux. This obliterates
+ any chance of having 0 checkpatch.pl errors between the 2.3.0 and
+ 2.4.0 releases. Oh well... Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/xhfc.c, drivers/dahdi/wctdm24xxp/base.c:
+ wctdm24xxp: Set the 'spantype' for the digital spans. Defaults to
+ "TE" but can be set by software to "NT" by dahdi_cfg.
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: 'is_span_digital' ->
+ 'dahdi_is_span_digital' Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+ * include/dahdi/user.h, include/dahdi/kernel.h: dahdi: Make it
+ clear that 'linecompat' can be used to identify analog spans. The
+ linecompat member can be used by a span to identify the
+ global-to-the-span signalling types supported. Analog spans do
+ not support any span-global signalling and therefore linecompat
+ should always be 0. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+2010-08-12 19:38 +0000 [r9127] Matthew Fredrickson <creslin at digium.com>
+
+ * drivers/dahdi/wcb4xxp/base.c: Timing fix where handling math in
+ find_sync_src() would return -2 instead of -1 in cases where
+ automatic timing sync was specified.
+
+2010-08-11 05:21 +0000 [r9120-9124] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Do not error when uncrossing a
+ channel if there is no 'dacs' callback. The previous commit was
+ making all chan configs fail on a span that did not have a dacs
+ callback. Also add some documentation for 'dahdi_chan_dacs' and
+ make it more explicit when we're disabling cross connect.
+
+ * drivers/dahdi/dahdi-base.c: dahdi: "Unable" -> "Unable to".
+ Proper sentences are always preferred. Thanks kpfleming :)
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Fix oops when trying to dacs
+ channels with a null dacs function.
+
+2010-08-09 14:43 +0000 [r9117] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * include/dahdi/kernel.h: work around RHEL backport of strcasecmp
+ RHEL/Centos 5.4 kernels broke after the latest strcasecmp
+ backport. So skip them.
+
+2010-08-06 22:12 +0000 [r9097-9105] Russ Meyerriecks <rmeyerreicks at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: minor checkpatch changes
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Added card level timing
+ information in sysfs For kernels >= 2.6.18, each individual card
+ has it's local timing hung off the pci device in the sysfs tree.
+ dahdi-626
+
+ * drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+ drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Added "auto"
+ companding option Added the "auto" option for the module
+ parameter "companding". In auto mode its left up to each card to
+ decide what companding mode it should be in. If a BRI module is
+ installed, it set everything to alaw; ulaw is selected if no BRI
+ module is installed. Also fixed a bug where forcing companding
+ one way or the other wasn't affecting the BRI modules. dahdi-673
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xp: Replaced alawoverride
+ with companding Added the module parameter "companding" to
+ eventually replace the current alawoverride parameter. Added some
+ deprecated messages so current users will know to move over
+ before we remove it entirely. dahdi-673
+
+ * drivers/dahdi/wcb4xxp/base.c: wcb4xxp: Renamed module parameter
+ "alawoverride" to "companding" Renamed the module parameter
+ "alawoverride" to "companding". The valid values for "companding"
+ are now the strings "alaw" or "ulaw", instead of integers.
+ dahdi-673
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: module param
+ "extendedreset" now a compile option Due to the very small number
+ of affected customers we have removed the module parameter
+ "extendedreset" in favor of a compile time option
+ "CONFIG_EXTENDED_RESET". dahdi-673
+
+ * include/dahdi/kernel.h: dahdi: Backport strcasecmp for kernels <
+ 2.6.22 strcasecmp was brought into the kernel at v2.6.22
+
+2010-08-06 18:27 +0000 [r9094] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Trivial spelling change.
+
+2010-08-05 21:05 +0000 [r9090] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/dahdi-base.c: don't crash on disconnecting of AB
+ This is a regression from r8985 . The temporary 'module' was
+ there because the pointer 'chan' may become invalid after the
+ close function.
+
+2010-08-04 00:18 +0000 [r9087] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/xhfc.c,
+ drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+ drivers/dahdi/wctdm24xxp/base.c, drivers/dahdi/wctdm24xxp/xhfc.h:
+ wctdm24xxp: 'struct dahdi_span' is already embedded in the
+ 'struct wctdm_span'. We cannot also embed it in struct b400m_span
+ structure and expect container_of to work. This fixes a
+ regression introduced in r8984.
+
+2010-08-03 13:16 +0000 [r9082] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * README: Proper Mantis category to use
+
+2010-07-31 04:00 +0000 [r9059-9073] Alec L Davis <sivad.a at paradise.net.nz>
+
+ * drivers/dahdi/wctdm.c: wctdm: Prevent FXS Proslic staying in
+ "Forward/Reverse OnHookTransfer" during call Since the 3 second
+ click after answering the call on an FXS port has been fixed
+ issue# 15352, the side effect is that the Proslic during a call,
+ still has the audio signal paths still powered on. Reading the
+ Si3215 specs it reads that an extra ~20mA is consumed while in
+ OHT mode. (issue #17764) Reported by: alecdavis Patches:
+ wctdm_fxs_offhook.diff.txt uploaded by alecdavis (license 585)
+ Tested by: alecdavis
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Prevent FXS Proslic
+ staying in "Forward/Reverse OnHookTransfer" during call
+ [One-liner summary of changes] Now that the 3 second click after
+ answering the call on an FXS port has been fixed, the side effect
+ is that the Proslic during a call, still has the audio signal
+ paths still powered on. Reading the Si3215 specs it reads that an
+ extra ~20mA is consumed while in OHT mode. (closes issue #17764)
+ Reported by: alecdavis Patches: wctdm24xxp_fxs_offhook.diff.txt
+ uploaded by alecdavis (license 585) Tested by: alecdavis
+
+ * drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+ drivers/dahdi/wctdm24xxp/base.c: SLIC_LF_OPPENDING confict
+ between wctdm_proslic_recheck_sanity() and
+ set_lasttxhook_interruptible() Problem:
+ 'wctdm_proslic_recheck_sanity()' is executed (4 times??) every
+ ~256ms which monitors and clears the SLIC_LF_OPPENDING on
+ fxs->lasttxhook when the LF state has been reached.
+ 'set_lasttxhook_interruptible()' times out after 100ms waiting
+ from the previous write to the SLIC_LF register, by waiting for
+ SLIC_LF_OPPENDING to be cleared, thus the write will fail.
+ Solution: adds wctdm_proslic_check_oppending which does the
+ monitoring and clearing of SLIC_LF_OPPENDING, which is execute
+ every 1ms. It also if the correct state is not reached within
+ 100ms, resends the lasttxhook state. (closes issue #17724)
+ Reported by: alecdavis Patches: wctdm24xxp_fxs_answer.diff4.txt
+ uploaded by alecdavis (license 585) Tested by: alecdavis,
+ sruffell
+
+ * drivers/dahdi/wcb4xxp/Makefile, drivers/dahdi/wctdm.c: reverting:
+ add curly braces to _write_8bits Against Kernel Coding Guidelines
+
+ * drivers/dahdi/wctdm.c: add curly braces to _write_8bits
+
+2010-07-29 21:51 +0000 [r9049-9056] Kinsey Moore <kmoore at digium.com>
+
+ * drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wct4xxp/base.c:
+ wct4xxp, wcte12xp: restrict signaling and line combinations to
+ what actually works
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: reference B400Ms as
+ BRI, correct a module alias, make the module description more
+ accurate
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: only allow B400M
+ modules on hybrid cards
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: correct references
+ to "wildcard" and display the number of BRI spans and analog
+ channels after detection
+
+ * drivers/dahdi/dahdi-base.c: dahdi-base: display Reserved when a
+ channel is unusable (has a sigcap of 0)
+
+ * drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wct4xxp/base.c:
+ wct4xxp, wcte12xp: remove loobpack parameter, functionality
+ provided by dahdi_maint
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: don't report about
+ VPM100s if none are present and warn the user when flashing
+ firmware
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: increase consistency and
+ decrease verbosity of kernel logging
+
+2010-07-28 15:32 +0000 [r9034-9046] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/voicebus/GpakApi.c: wcte12xp, wctdm24xxp: Minor
+ cleanup 0 -> NULL
+
+ * drivers/dahdi/tor2.c: tor2: Do not directly dereference I/O
+ memory. Mainly to quiet a sparse warning, but this could be a
+ real problem on some non x86 platforms.
+
+ * drivers/dahdi/wctdm.c: wctdm: Fix signed one-bit fields. Thanks
+ sparse.
+
+ * drivers/dahdi/wcte12xp/base.c: wcte12xp: Add __user annotation in
+ copy_to_user call. Quiets sparse.
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Several minor changes to
+ make sparse/checkpatch.pl happy. Make setup_chunks static,
+ eliminate a dynamic array in the interrupt handler, don't cast
+ away a memory region specifier, and don't initialize statics to
+ 0.
+
+ * drivers/dahdi/wcb4xxp/base.c: wcb4xxp: Trivial removal of some
+ whitespace at the end of a line. Fixing formatting errors that
+ have snuck in since the 2.3.0 release.
+
+ * drivers/dahdi/wcte12xp/base.c: wcte12xp: Trival formatting
+ changes. Fixing up some of the formatting errors that crept in
+ since the 2.3.0 release.
+
+ * README: README: Trivial removal of whitespace at the end of
+ lines.
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Unlock the dahdi_span.lock
+ when passed an invalid DAHDI_MAINT command. Fixes the following
+ sparse warning "warning: context imbalance in 'dahdi_ctl_ioctl' -
+ different lock contexts for basic block". Thank you sparse!
+
+ * drivers/dahdi/wctc4xxp/base.c: wctc4xxp: Add compile-time option
+ to always poll the interface. Added as a workaround for a system
+ which was not routing interrupts properly and therefore is off by
+ default. Candidate for reversion in a couple of years. DAHDI-627.
+
+ * drivers/dahdi/wctc4xxp/base.c: wctc4xxp: Move from I/O space to
+ memory-mapped registers. Certain platforms have trouble with the
+ registers mapped from I/O space. DAHDI-627.
+
+ * drivers/dahdi/wctc4xxp/base.c: wctc4xxp: Do not ACK response
+ packets without a corresponding request. Closes a small window of
+ opportunity where system conditions prevent the driver from
+ servicing it's receive ring within the timeout period of a
+ request, and then in the middle of retrying the request (after
+ the request was already removed from the "waiting_for_response"
+ list) the driver process the response, it's possible for the
+ driver to ACK the response without ever pairing it up with the
+ original request. The result being that the DTE will then ignore
+ our attempts to retry the original request. DAHDI-430.
+
+ * drivers/dahdi/wctc4xxp/base.c: wctc4xxp: Allow read to return
+ more than one packet of data. As of this writing codec_dahdi
+ (Asterisk module) will not call 'read' on a transcoder channel
+ more often than it calls 'write'. When a translation path is
+ setup that will transcode from g723 to g729, write is called
+ every 30ms and each 'read' returns only 20ms of data. The end
+ result is audio that slowly becomes increasing delayed. Since
+ codec_dahdi calls the system read function with a buffer large
+ enough to hold more than one packet this can prevents packets
+ from backing up on the channel. DAHDI-582
+
+2010-07-28 10:30 +0000 [r9025-9028] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_pri.c: Ignore Reg. 0x70 messages at E1.
+
+ * drivers/dahdi/xpp/card_pri.c: demote a notice that will happen at
+ registration We might as well ignore this, as we will get this at
+ span registration time anyway.
+
+2010-07-27 01:31 +0000 [r8997-9019] Russ Meyerriecks <rmeyerreicks at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Enabled network facing
+ looping for E1 Added the abililty to loop the line back towards
+ the network for E1 modes. This supports both network loop and
+ network payload loop.
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Fixed error injection bug
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Error counter injection
+ for E1 mode Added support for error counter injection for E1 mode
+
+ * include/dahdi/user.h, drivers/dahdi/wct4xxp/base.c: wct4xxp:
+ Removed card level event handler Upon review the event introduced
+ in r8998 seemed to be redundant, as the same information was
+ already available. Performance issues were also a concern. This
+ reverts r8998.
+
+ * include/dahdi/user.h, drivers/dahdi/wct4xxp/base.c,
+ drivers/dahdi/dahdi-base.c: Added hardware transformer check
+ QuadFalc has the ability to test if the transformer is performing
+ correctly. If the components between the framer and the physical
+ span interface are shorted out or opened for any reason we can
+ now detect it. Possible causes for tripping this error could be a
+ broken transformer from an electrical spike or a board
+ manufacturing error.
+
+ * include/dahdi/user.h, drivers/dahdi/wct4xxp/base.c,
+ drivers/dahdi/dahdi-base.c: Added card level event handler When a
+ loss of syncronization signal occurs on one of the spans, it
+ affects all spans on that card. Since we do not have a span or
+ card level event system, we have to queue up a global event on
+ all channels for that card The new event is DAHDI_EVENT_SYNC
+
+ * drivers/dahdi/wct4xxp/wct4xxp.h, include/dahdi/user.h,
+ drivers/dahdi/wct4xxp/base.c, drivers/dahdi/dahdi-base.c: Added
+ the ability to trigger alarm simulation states in the qfalc
+ framer. Added some more verbose red alarm states in the upper
+ byte of the alarm member of the dahdi_span structure Removed some
+ unnecessary instrumentation regarding the enabling of the errored
+ second and 1 second counters for performance collecting. Also
+ added a couple comments.
+
+2010-07-26 00:30 +0000 [r8979-8986] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/tor2.c, drivers/dahdi/wcfxo.c,
+ drivers/dahdi/wcte12xp/base.c, include/dahdi/kernel.h,
+ drivers/dahdi/xpp/card_pri.c, drivers/dahdi/pciradio.c,
+ drivers/dahdi/wct4xxp/base.c, drivers/dahdi/xpp/card_fxo.c,
+ drivers/dahdi/wctdm24xxp/base.c, drivers/dahdi/xpp/card_fxs.c,
+ drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/wcb4xxp/base.c,
+ drivers/dahdi/wcte11xp.c, drivers/dahdi/xpp/card_bri.c,
+ drivers/dahdi/dahdi_dynamic.c, drivers/dahdi/wctdm.c,
+ drivers/dahdi/wct1xxp.c, drivers/dahdi/dahdi-base.c,
+ drivers/dahdi/dahdi_dummy.c: dahdi: Move the 'owner' field from
+ dahdi_span to dahdi_span_ops. One more thing that can be moved
+ out of the per-span structure.
+
+ * drivers/dahdi/tor2.c, drivers/dahdi/wcfxo.c,
+ drivers/dahdi/wcte12xp/base.c, include/dahdi/kernel.h,
+ drivers/dahdi/pciradio.c, drivers/dahdi/xpp/card_pri.c,
+ drivers/dahdi/wct4xxp/base.c, drivers/dahdi/wctdm24xxp/base.c,
+ drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/wcb4xxp/base.c,
+ drivers/dahdi/wcte11xp.c, drivers/dahdi/xpp/card_bri.c,
+ drivers/dahdi/xpp/xpp_dahdi.h, drivers/dahdi/dahdi_dynamic.c,
+ drivers/dahdi/wct1xxp.c, drivers/dahdi/wctdm.c,
+ drivers/dahdi/dahdi-base.c: dahdi: Move the callbacks in
+ dahdi_span into its own structure. Part of preparation for adding
+ additional callbacks to allow board drivers to advertise and
+ support gathering pre-echocan data from hardware echocans.
+
+ * drivers/dahdi/tor2.c, drivers/dahdi/wcfxo.c,
+ drivers/dahdi/wcte12xp/base.c, include/dahdi/kernel.h,
+ drivers/dahdi/xpp/card_pri.c, drivers/dahdi/pciradio.c,
+ drivers/dahdi/wct4xxp/base.c, drivers/dahdi/wctdm24xxp/base.c,
+ drivers/dahdi/xpp/xbus-pcm.c, drivers/dahdi/xpp/xpp_dahdi.c,
+ drivers/dahdi/wcb4xxp/base.c, drivers/dahdi/wctdm24xxp/xhfc.c,
+ drivers/dahdi/wcte11xp.c, drivers/dahdi/xpp/card_bri.c,
+ drivers/dahdi/dahdi_dynamic.c,
+ drivers/dahdi/wctdm24xxp/wctdm24xxp.h, drivers/dahdi/wctdm.c,
+ drivers/dahdi/wct1xxp.c, drivers/dahdi/wctdm24xxp/xhfc.h,
+ drivers/dahdi/dahdi_dummy.c: dahdi: Remove the 'pvt' member from
+ dahdi_span. The vast majority of board drivers already keep the
+ dahdi_span structure in a driver specific structure. The others
+ were easily converted. This way board drivers can use the
+ container_of macro to find what was previously pointed to by the
+ "pvt" member of the span. One less thing to think about in the
+ span structure.
+
+ * drivers/dahdi/firmware/Makefile,
+ drivers/dahdi/voicebus/GpakApi.c,
+ drivers/dahdi/voicebus/gpakenum.h,
+ drivers/dahdi/voicebus/GpakApi.h,
+ drivers/dahdi/voicebus/GpakCust.c,
+ drivers/dahdi/voicebus/gpakErrs.h: wcte12xp, wctdm24xxp: Updating
+ VPMADT032 firmware to version to 1.25 The echo canceler will now
+ monitor if the receive signal goes over a certain threshold, and
+ if so, freezes its adaptation to prevent loss of convergence.
+ I.e. Fixes conditions where blowing into your handset could
+ result in echo. Additionally, 1.25 includes improvements for
+ handling when line conditions change from echo free to containing
+ echo.
+
+ * drivers/dahdi/voicebus/voicebus.c,
+ drivers/dahdi/voicebus/voicebus.h: wcte12xp, wctdm24xxp: Return
+ buffer processing to interrupt handler. In revision 8095, I had
+ moved most of the buffer processing out of the interrupt handler
+ and into a tasklet. The intended result was to enable multiple
+ cards to interleave with one another. But once again I was bitten
+ by the fact that there are some systems that for one reason or
+ another do not process their tasklets in a timely enough manner
+ for the real-time nature of TDM processing. This commit moves
+ this processing back into the interrupt handler by default. It
+ also limits the number of frames that the interrupt handler will
+ process at any given time which appears to achieve the same
+ intended result. (closes issue #17289) Tested by: alecdavis
+
+ * drivers/dahdi/wcte12xp/base.c, drivers/dahdi/voicebus/voicebus.c,
+ drivers/dahdi/wctdm24xxp/base.c,
+ drivers/dahdi/voicebus/voicebus.h: wcte12xp, wctdm24xxp:
+ spin_lock_bh -> spin_lock_irqsave Will add an option to allow
+ calling the deferred processing callback directly in the
+ interrupt handler. It appears there are some systems which still
+ are unable to process their tasklets in a timely fashion,
+ especially if they get pushed out to the ksoftirqd daemon.
+
+ * drivers/dahdi/wcte12xp/base.c: wcte12xp: Do not call
+ destory_workqueue if the workqueue was not yet created.
+
+ * drivers/dahdi/wcte12xp/base.c, drivers/dahdi/voicebus/voicebus.c,
+ drivers/dahdi/wctdm24xxp/base.c: wcte12xp, wctdm24xxp: Add
+ shutdown handlers. Make the drivers a little more kexec friendly.
+
+2010-07-25 16:43 +0000 [r8975] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_pri.c: No need to worry about accidental
+ "changes" in reg. 0x70 in E1
+
+2010-07-22 15:28 +0000 [r8968-8969] Matthew Fredrickson <creslin at digium.com>
+
+ * drivers/dahdi/wcb4xxp/base.c: Make sure we also change the deflaw
+ of the span to ulaw if alawoverride is disabled.
+
+ * drivers/dahdi/wct4xxp/base.c: Make sure we check max_latency to
+ see if it's greater than the minimum required latency for the
+ board in question.
+
+2010-07-19 13:49 +0000 [r8943-8944] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * README: Copy README section of kernel sources from Zaptel. Still
+ needs some simplifications. Anybody?
+
+ * drivers/dahdi/xpp/card_fxs.c: FXS - fix VMWI compatibility mode:
+ * If we have vmwi_ioctl=N, we should initialize the vmwi_type of
+ all channels. We initialize it to HVAC * Fix a regression, where
+ curly braces around empty if()'s were removed. * Also fix the
+ VMWI_TYPE() macro, so it actually uses the 3'rd parameter. (this
+ didn't cause damage yet, as we only used HVAC so far)
+
+2010-07-16 16:25 +0000 [r8939] Matthew Fredrickson <creslin at digium.com>
+
+ * drivers/dahdi/wcb4xxp/base.c: Add alawoverride parameter to the
+ wcb4xxp module to allow for ulaw and alaw mode.
+
+2010-07-14 20:15 +0000 [r8935] Matthew Fredrickson <creslin at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: Make noburst parameter override
+ burst flag.
+
+2010-07-14 11:50 +0000 [r8872-8931] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/PIC_TYPE_4.hex: PIC 4 rev. 7381: fix
+ T1 returning signaling register in non-CAS This is the second
+ part of the partial fix in r8872, though each of the two should
+ work independently.
+
+ * drivers/dahdi/xpp/firmwares/USB_FW.hex: Allow reading caps when
+ twinstar watchdog set Fixes reading capabilities when the
+ watchdog is set. In that case most of the data, as seen, e.g. in
+ output of 'astribank_allow', was 0xFF. Xorcom rev: 7809
+
+ * drivers/dahdi/xpp/init_card_4_30, drivers/dahdi/xpp/card_pri.c:
+ Set Astribank PRI before initialization This avoids most cases of
+ sending garbage at startup by setting each port to tristate mode
+ at init time (in the init script) and enable it back at
+ DAHDI_STARTUO (end of dahdi_cfg). Upgrade note: if you have
+ upgraded the files (including init script) but old module is
+ still loaded, you may end up with the port not getting ever
+ enabled and the line practically dead. In such a case, reload the
+ new module.
+
+ * drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xbus-core.c,
+ drivers/dahdi/xpp/xbus-core.h, drivers/dahdi/xpp/xbus-pcm.c:
+ start migrating from xbus_num() to get_xbus()/put_xbus() * Now
+ get_xbus() receive and xbus number (not poiner) and uses
+ xbus_num() internally to map it to an xbus pointer + refcount
+ increment. (this is atomic) * Migrate all obvious places that
+ used xbus_num() to map bus number into a pointer, so now they use
+ get_xbus() + put_xbus() to aquire and release an xbus.
+
+ * drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xproto.h,
+ drivers/dahdi/xpp/card_pri.c, drivers/dahdi/xpp/xbus-pcm.h,
+ drivers/dahdi/xpp/card_bri.c, drivers/dahdi/xpp/card_fxo.c,
+ drivers/dahdi/xpp/xbus-core.c, drivers/dahdi/xpp/card_fxs.c,
+ drivers/dahdi/xpp/xbus-core.h, drivers/dahdi/xpp/xbus-pcm.c: PRI
+ Astribanks always sync AB (and independent) * PRI devices always
+ get SYNC-AB (never PLL, not even for NT) * Fix Timing priority
+ calculation accordingly. * On PRI layer1 changes, elect_syncer()
+ is called, so we have re-election.
+
+ * drivers/dahdi/xpp/xbus-core.c, drivers/dahdi/xpp/card_global.c,
+ drivers/dahdi/xpp/xbus-core.h: prevent handling of duplicate
+ Astribanks Don't let AB which are unplugged/replugged create
+ duplicate XBUS's (if asterisk don't close the original channels).
+
+ * drivers/dahdi/xpp/xbus-sysfs.c: Create /sys/devices/astribanks: *
+ Astribank devices now reside under their own top-level device. *
+ The USB device is still used as the 'transport'. * This means the
+ astribanks parents are NOT the USB devices. * As a result, even
+ after a USB disconnect, we have valid sysfs representation.
+
+ * drivers/dahdi/xpp/xpd.h, drivers/dahdi/xpp/xpp_dahdi.c,
+ drivers/dahdi/xpp/xbus-sysfs.c, drivers/dahdi/xpp/xbus-core.c,
+ drivers/dahdi/xpp/xbus-core.h: Keep SYSFS objects after
+ disconnect When the USB device disconnects, we keep references to
+ them to make sure they don't disappear.
+
+ * drivers/dahdi/xpp/card_pri.c: Don't reset span flag RBS on pri
+ module Don't attempt to reset the span flag DAHDI_FLAG_RBS. At
+ pre-registration we don't yet know if we're CAS or not.
+
+ * drivers/dahdi/xpp/card_pri.c: don't send "duplicates" in E1 as in
+ D4 Make sure we only consider T1-s to be potentially D4 (which
+ requires sending the bits twice). This fixes occasional
+ command-queue floods in E1 CAS.
+
+ * drivers/dahdi/xpp/card_fxs.c: Put a space where it belongs
+
+ * drivers/dahdi/xpp/xpd.h, drivers/dahdi/xpp/xpp_dahdi.c,
+ drivers/dahdi/xpp/card_fxs.c: Basic support for DAHDI_VMWI_CONFIG
+ * Supports only our current NEON notification. * No more global
+ 'vmwineon' parameter: - We expect asterisk to tell us by channel.
+ - If 'vmwi_ioctl' is not set (it is by default), that we revert
+ to FSK searching (expensive) and call directly our NEON code (as
+ before).
+
+ * drivers/dahdi/xpp/xbus-core.c, drivers/dahdi/xpp/card_global.c:
+ Solve race xbus_populate Fixes a crash resulting from a race
+ between disconnecting and connecting Astribanks (on multi-core
+ systems) * Use get_xbus()/put_xbus() arround xbus_populate(), so
+ a disconnect in the middle won't release the xbus too early. *
+ Aquire all XPDs before starting initialization and release them
+ after it finishes (so we don't have up/down races among XPDs)
+
+ * drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xbus-sysfs.c,
+ drivers/dahdi/xpp/xbus-core.c, drivers/dahdi/xpp/card_global.c,
+ drivers/dahdi/xpp/xbus-core.h: put xbus->worker in xbus;
+ wake_up_interruptible_all() * The worker member of 'struct xbus'
+ is now an embedded struct xbus_workqueue. * Replace wake_up() to
+ wake_up_interruptible_all().
+
+ * drivers/dahdi/xpp/xpd.h, drivers/dahdi/xpp/xpp_dahdi.c,
+ drivers/dahdi/xpp/xbus-sysfs.c, drivers/dahdi/xpp/xbus-core.c:
+ Cleanup: refcount_xpd() * Change refcount_xpd(): instead of
+ returning a pointer to the atomic counter, return directly its
+ value (just like refcount_xbus()) * Add a refcount_xbus and
+ refcount_xpd attributes to sysfs (for debugging)
+
+ * drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xpp_usb.c,
+ drivers/dahdi/xpp/xbus-pcm.h, drivers/dahdi/xpp/card_bri.c,
+ drivers/dahdi/xpp/card_fxo.c, drivers/dahdi/xpp/xbus-core.c,
+ drivers/dahdi/xpp/card_fxs.c, drivers/dahdi/xpp/xbus-core.h,
+ drivers/dahdi/xpp/xbus-pcm.c: Fix building without CONFIG_PROC_FS
+ defined This changeset should have no functional changes.
+
+ * drivers/dahdi/xpp/init_card_4_30: Don't assume hardwired
+ pri_protocol is E1 When initializing registers for the "PRI"
+ (E1/T1) module, in the case the user has not explicitly asked for
+ E1/T1 settings in xpp.conf (pri_protocol) fall back to the
+ current value, which is the build-time fall-back. The value is
+ read from sysfs. Previously we implicitly assumed this value is
+ E1.
+
+ * drivers/dahdi/xpp/init_card_4_30: partial fix of T1 returning
+ signaling register in non-CAS mode
+
+2010-07-12 18:45 +0000 [r8868] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c, drivers/dahdi/dahdi_dummy.c: dahdi:
+ Explicitly ensure we don't schedule a timer for the current tick.
+ As best as I can tell, when CONFIG_NO_HZ is set along with
+ CONFIG_HZ < 250, it is possible for the system timer to exceed
+ MAX_SOFTIRQ_RESTART. Tony Mountifield alluded that this might be
+ a problem in the below mailing list posting, but when I was
+ originally testing, I wasn't using CONFIG_NO_HZ and HZ < 250.
+ http://www.mail-archive.com/asterisk-dev@lists.digium.com/msg37384.html
[... 2457 lines stripped ...]
More information about the dahdi-commits
mailing list