[svn-commits] sruffell: tag linux/2.5.0.2 r10258 - in /linux/tags/2.5.0.2: .version ChangeLog
SVN commits to the Digium repositories
svn-commits at lists.digium.com
Fri Oct 21 17:16:02 CDT 2011
Author: sruffell
Date: Fri Oct 21 17:15:58 2011
New Revision: 10258
URL: http://svnview.digium.com/svn/dahdi?view=rev&rev=10258
Log:
Importing files for 2.5.0.2 release.
Added:
linux/tags/2.5.0.2/.version (with props)
linux/tags/2.5.0.2/ChangeLog (with props)
Added: linux/tags/2.5.0.2/.version
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.5.0.2/.version?view=auto&rev=10258
==============================================================================
--- linux/tags/2.5.0.2/.version (added)
+++ linux/tags/2.5.0.2/.version Fri Oct 21 17:15:58 2011
@@ -1,0 +1,1 @@
+2.5.0.2
Propchange: linux/tags/2.5.0.2/.version
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: linux/tags/2.5.0.2/.version
------------------------------------------------------------------------------
svn:keywords = none
Propchange: linux/tags/2.5.0.2/.version
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added: linux/tags/2.5.0.2/ChangeLog
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.5.0.2/ChangeLog?view=auto&rev=10258
==============================================================================
--- linux/tags/2.5.0.2/ChangeLog (added)
+++ linux/tags/2.5.0.2/ChangeLog Fri Oct 21 17:15:58 2011
@@ -1,0 +1,5096 @@
+2011-10-21 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux 2.5.0.2 released.
+
+2011-10-21 19:48 +0000 [r10253-10254] Shaun Ruffell <sruffell at digium.com>
+
+ * include/dahdi/kernel.h, drivers/dahdi/wctc4xxp/base.c: dahdi:
+ Move WARN_ON_ONCE from wctc4xxp driver to include/dahdi/kernel.h
+ I only generally test on RHEL 4 when testing against kernels
+ older than 2.6.18. Apparently OpenSUSE 10.1 runs with 2.6.16 and
+ doesn't have WARN_ON_ONCE backported. I took the patch Richard
+ Miller originally attached to the issue and moved it to
+ include/dahdi/kernel.h so it would be available for all the board
+ drivers in the future. Internal-Issue-ID: DAHLIN-260 Reported-by:
+ Richard Miller Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=10252
+
+ * drivers/dahdi/wcb4xxp/base.c: wcb4xxp: Do not show LASVEGAS2 as
+ echocan name if vpmsupport is set to 0 This fixes an issue where
+ "EC: LASVEGAS2" was displayed in /proc/dahdi/x for a B410P span
+ even though vpmsupport was disabled with the module parameter.
+ Internal-Issue-ID: DAHLIN-247 Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10251
+
+2011-10-12 16:32 +0000 [r10221] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Fix condition where
+ hardware echo canceler erroneously mutes DTMF. Commit r9750
+ "wct4xxp: Reduce the memory footprint of the hardware
+ echocanceler.", as part of reducing the non-pageable memory
+ required to support the VPMOCT064 and VPMOCT128, disabled caching
+ of some hardware echocan registers. This resulted in more
+ physical reads to the echo canceler. These new read transactions
+ exposed an existing issue where sometimes reads could be turned
+ into writes which put a channel into an unintended state
+ preventing Asterisk from detecting any DTMF. This issue is
+ resolved by ensuring that the write signal to the Octasic part is
+ explicitly cleared between when the address is presented on the
+ bus and when the read and chip select signals are asserted. The
+ cost is an increase in the average time to enable / disable echo
+ cancellation by about 5 us on one Intel Xeon X3220 test machine
+ (~250ns increase per read from the Octasic part and 20 reads to
+ enable / disable a channel). This commit resolves a behavioral
+ regression first introduced in 2.5.0 and 2.4.1 which could take
+ many calls before revealing itself. This change only affects
+ cards with a VPMOCT128 or VPMOCT064 installed. Signed-off-by:
+ Shaun Ruffell <sruffell at digium.com> Acked-by: Doug Bailey
+ <dbailey at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10220
+
+2011-09-30 19:23 +0000 [r10219] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctc4xxp/base.c: wctc4xxp: Allow G723 SID frames to
+ pass to the hardware decoder. The driver has, until now, dropped
+ G723 SID frames even though the firmware on the TC400/TCE400 can
+ handle them. Now let them on through. Reported-and-Tested-by:
+ Angel Carhuas <acarhuas at colinanet.com> Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10218
+
+2011-09-27 22:10 +0000 [r10211] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Set
+ dahdi_span.devicetype string in one place. Currently the
+ devicetype string was set both when the device was first
+ allocated and updated when an echocanceler was detected. For
+ simplicity, combine both these steps into a single function. This
+ change also replaces an improper use of strncat with strlcat.
+ Additionally, on the 2.5 branch, this change actually makes
+ r10206 "wctdm24xxp, wcte12xp: Advertise VPMOCT032 presence in
+ dahdi_span.devicetype", work the way it was originally intended.
+ That change was only functioning properly previously on trunk.
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10210
+
+2011-09-25 08:59 +0000 [r10208] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: fxs: bugfix for 2fxs+6fxo
+ cards * Bug sympthoms: wrong FSK VMWI sent few seconds after
+ offhook. That was caused because the driver kept polling the
+ (physically unconnected) digital inputs. [note: a workaround for
+ drivers without this patch is to zero the
+ 'xpd_fxs.poll_digital_inputs' parameter.] * Also, the
+ digital_inputs/digital_output masks were calculate using a
+ different condition. * Now we determine number of channels,
+ digital inputs and digital outputs in a single place and use this
+ info later to calculate the correct masks. * We poll only if
+ there are digital_inputs * We added a sanity check in
+ process_digital_inputs, so we get a notice if it's called on an
+ xpd without digital inputs (e.g: hypothetic firmware bug).
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com> Acked-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+2011-09-23 20:23 +0000 [r10206-10207] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Check for master in
+ DAHDI_STARTUP / resolves MeetMe regression. There were a couple
+ of reports that MeetMe conferences were not working in 2.5.0.1
+ and that downgrading to 2.4.1.2 resolved the issue. This could
+ occur if there were no analog spans in a system, and all the
+ digital spans were out of alarm before DAHDI_STARTUP ioctl was
+ called by dahdi_cfg. If the spans were *not* out of alarm, they
+ would be marked master when the span changes it's alarm state.
+ This would result in a condition where no spans were marked as
+ the "master" and so the core timer was handling conferencing. The
+ core timer runs by default at 4ms and most board drivers run at
+ 1ms intervals, but a channel currently only buffers up 2ms of
+ data when conferenced. Therefore, 2ms of audio from a board was
+ continuously dropped from the conference every 4ms by default.
+ This fixes a regression first introduced in 2.5.0 which was
+ specifically added in revision r9611 "dahdi: Do not locate new
+ master in interrupt context." Internal-reference-ID: DAHDI-894
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Tested-by:
+ Dennis Martinez <dmartinez at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10205
+
+ * drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wctdm24xxp/base.c:
+ wctdm24xxp, wcte12xp: Advertise VPMOCT032 presence in
+ dahdi_span.devicetype. A "(VPMADT032)" string is appended to the
+ devicetype (as shown by dahdi_scan) for the span if one is
+ installed. Now append '(VPMOCT032)' if one is installed as well.
+ Also, for the wcte12xp driver append the VPM name to the device
+ type after initially probing as opposed to only after the span is
+ configured. (Related to issue DAHDI-890) Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10203
+
+2011-09-13 18:38 +0000 [r10201] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Decrease the initial coretimer
+ delay to 4ms from 1 second. DAHDI currently waits a second before
+ checking if a board driver is calling dahdi_receive and switching
+ to internal timing. Some versions of Asterisk (I was looking at
+ 1.4.42 when writing this) only wait 300ms for a timer to expire
+ when first starting and verifying that DAHDI is properly
+ configured. This can result in a "ERROR[27673] asterisk.c:
+ Asterisk has detected a problem with your DAHDI configuration and
+ will shutdown for your protection. You have options:" message if
+ asterisk is started soon after loading DAHDI. This change sets
+ the inital polling interval to the same as that used during
+ normal coretimer operation, 4ms. The interval will still be
+ slowed to 1 second if a board driver starts calling
+ dahdi_receive(). DAHDI-892. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10200
+
+2011-09-05 10:29 +0000 [r10180] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/PIC_TYPE_1.hex,
+ drivers/dahdi/xpp/firmwares/PIC_TYPE_2.hex,
+ drivers/dahdi/xpp/firmwares/FPGA_1161.hex: xpp: firmware to
+ detect the new 2+6 module New firmwares to handle the new
+ 2FXS/6FXO module. FPGA_1161.hex, PIC_TYPE_1.hex, PIC_TYPE_2.hex
+ of internal rev. 9732 Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-09-06 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux 2.5.0.1 released.
+
+2011-09-05 10:29 +0000 [r10180] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/PIC_TYPE_1.hex,
+ drivers/dahdi/xpp/firmwares/PIC_TYPE_2.hex,
+ drivers/dahdi/xpp/firmwares/FPGA_1161.hex: xpp: firmware to
+ detect the new 2+6 module New firmwares to handle the new
+ 2FXS/6FXO module. FPGA_1161.hex, PIC_TYPE_1.hex, PIC_TYPE_2.hex
+ of internal rev. 9732 Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-08-30 21:06 +0000 [r10173] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/firmware/Makefile: wcte12xp, wctdm24xxp: Update
+ VPMOCT032 firmware to 1.11.0. Firmware version 1.11.0 resolves an
+ issue where the driver fails to detect certain VPMOCT032 modules
+ after a cold boot. Signed-off-by: Doug Bailey
+ <dbailey at digium.com> Acked-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10172
+
+2011-08-28 09:45 +0000 [r10157] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: FXS: new 2+6 module has no
+ digital I/O ports This module is recognized via subtype==4
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+2011-08-19 22:53 +0000 [r10149-10150] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Set 'fastoffhook'
+ counter to 8ms and turn off calibration delay. r10006
+ "wctdm24xxp: Add 'fastpick' module parameter." copied the
+ fast-off hook module parameter from the wctdm.c driver, but the
+ setting in that driver does not match the data sheet. The
+ previous commit did not actually change any of the significant
+ bits in that register. Also, that commit changed the timer, but
+ did not disable the callibration delay which is necessary for
+ Type-II callerid. The fastpickup option in the wctdm24xxp driver
+ should now match the fastpickup option in the wctdm driver.
+ DAHDI-224. Reported-By: Kinnith Wallace <kwallace at digium.com>
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10148
+
+ * drivers/dahdi/wctdm.c: wctdm: Set 'fastpickup' counter to 8ms
+ This fixes what looks like a typo in r1055 [1]. [1]
+ http://svnview.digium.com/svn/dahdi?view=revision&revision=1055
+ Reported-by: Kinnith Wallace <kwallace at digium.com> Signed-off-by:
+ Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10147
+
+2011-08-18 19:35 +0000 [r10145-10146] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+ drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Use our own free
+ list for IRQ commands. Really only *necessary* when SLAB
+ debugging is enabled, but in that case, can reduce the chance of
+ latency bumps when first loading the driver. Otherwise the
+ constant slab poisoning / checking in interrupt context from the
+ kmalloc / kfrees is too much. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Acked-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10144
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Bug in timing cable with
+ different span density cards The logic loops through the static
+ cards[] array to determine timing, but the subloop was based off
+ the current card's numspans member. This could cause a null
+ dereference in the case where two cards of different span
+ densities were connected via timing cables. Reported-by: Doug
+ Bailey <dbailey at digium.com> Signed-off-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10140
+
+2011-08-15 21:55 +0000 [r10139] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctc4xxp/base.c: wctc4xxp: Fix lock imbalance in
+ wctc4xxp_watchdog. r10082 "wctc4xxp: Cleanup in-flight commands
+ when halting due to hardware error." introduced a lock imblance
+ on the error path where the cmd_list_lock would be unlocked twice
+ when the board is halted due to a hardware error. Thanks sparse.
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10138
+
+2011-08-12 16:06 +0000 [r10115-10119] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/voicebus/voicebus.c: wcte12xp, wctdm24xxp: Force
+ local interrupts off in the interrupt handler. r10066
+ "wctdm24xxp, wcte12xp: Run the ISR with interrupts disabled."
+ requested that the interrupt handler be run in "fast" mode
+ (disabled) but this isn't necessarily guaranteed. This patch
+ makes the interrupt handler itself disable all the interrupts.
+ Linux commit 470c66239ef0336429b35345f3f615d47341e13b [1]
+ contains a comment about why this is necessary. [1]
+ http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=470c66239ef03364
+ (closes issue DAHLIN-248) Reported-and-Tested-by: Vladimir
+ Mikhelson <vlad at mikhelson.com> Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10118
+
+ * include/dahdi/kernel.h: dahdi: Define HAVE_NET_DEVICE_OPS on
+ kernels > 2.6.29 HAVE_NET_DEVICE_OPS was defined in the mainline
+ kernel in commit 47fd5b83 which was first released in 2.6.29. Any
+ kernels after that will have those fields defined. Mainline
+ commit e2270ea62ae4d7a removed the feature test macros, so the
+ easiest thing to do is define HAVE_NET_DEVICE_OPS ourselves on
+ the kernels since it was committed. This change is needed to
+ compile against the 3.1 kernel. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10109
+
+ * drivers/dahdi/dahdi_dynamic.c: dahdi_dynamic: Call dahdi_receive
+ in rx packet handler. Currently dahdi_receive is called on all
+ channels in the context of the master dynamic span. If one span
+ (not the master) receive two packets before the master span
+ received a packet, the older packet on the dynamic span would end
+ up lost because the "readchunk" for the channels would be
+ overwritten by the new packet. DAHLIN-245 Signed-off-by: Wagner
+ Gegler <wagner at aligera.com.br> (License #6268) Changed
+ dahdi_ec_chunk to dahdi_ec_span. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10110
+
+ * drivers/dahdi/voicebus/voicebus_net.c,
+ drivers/dahdi/wctc4xxp/base.c: wctc4xxp, wcte12xp, wctdm24xxp:
+ Remove check for HAVE_NETDEV_PRIV DAHDI currently supports
+ kernels >= 2.6.9. netdev_priv() has been in the mainline kernel
+ since versions 2.6.6 so it's available in all the supported
+ kernels. This change is needed to compile against the 3.1 kernel.
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10096
+
+2011-08-09 12:26 +0000 [r10098-10100] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/FPGA_1161.hex: FPGA_1161 rev 9605: EC
+ related bug fixes Astribank II FPGA firmware rev 9605. Includes
+ two bug fixes: * Error in checking EC licenses when the license
+ was for exactly 64 or 128 channels. * Proper handling of a slave
+ FXO Astribank (in line with the quirks handling from r10019).
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * / (added): A stable branch for DAHDI-linux 2.5
+
+2011-08-05 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux 2.5.0 released.
+
+2011-07-26 20:19 +0000 [r10082] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctc4xxp/base.c: wctc4xxp: Cleanup in-flight
+ commands when halting due to hardware error. On one system I was
+ seeing the board reset in the middle of a transaction. Any
+ commands that were on the response list when this would happen
+ would never be completed and the process would then be stuck in
+ an uninterruptible sleep. This change also prevents the driver
+ from sleeping in timer context, which would result in a kernel
+ panic. This change at least lets an error message propogate back
+ to the user. DAHDI-880 Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+2011-07-22 17:56 +0000 [r10079] Russ Meyerriecks <rmeyerreicks at digium.com>
+
+ * drivers/dahdi/wcb4xxp/base.c: wcb4xxp: Prevent null pointer
+ dereference on spanconfig In the rare case where spanconfig is
+ called while there is pending data on the hdlc channel, the
+ hdlc_getbuf interrupt could try to read from the hdlc buffer
+ before the channel was fully setup. This could potentially result
+ in a null pointer dereference. This condition has existed since
+ the creation of the wcb4xxp driver. Signed-off-by: Russ
+ Meyerriecks <rmeyerriecks at digium.com> Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com>
+
+2011-07-21 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux version 2.5.0-rc2 released.
+
+2011-07-21 16:26 +0000 [r10066-10070] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Drivers that do not support
+ hwec should not report hwec is available. When attaching software
+ echocans to a channel, if there is a hardware echocan available
+ always give preference to them. Revision 9995 "dahdi: Always
+ attach hwec to a channel if available" had an error where if a
+ driver did not even support an option of hardware echocan,
+ dahdi-base would take that to mean there always was a hardware
+ echocan available on the channel. DAHLIN-246 Reported-by: Michael
+ L. Young Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Acked-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/voicebus/voicebus.c: wctdm24xxp, wcte12xp: Run the
+ ISR with interrupts disabled. Revision 9886, "wcte12xp: Use the
+ in-hardirq versions of dahdi_receive/dahdi_transmit", changed the
+ call into dahdi_receive and dahdi_transmit to use versions that
+ assume local interrupts are already disabled. Not all versions of
+ the kernel run interrupt service routines with all interrupts
+ disabled and therefore it was possible to lock up a CPU with a
+ recursive grab of the chan_lock. When LOCKDEP was enabled (on
+ debug kernels) interrupt handlers were run atomically so this
+ problem would only occur on pre 2.6.35 kernels that did not have
+ lockdep enabled. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+2011-07-20 21:32 +0000 [r10063-10064] Russ Meyerriecks <rmeyerreicks at digium.com>
+
+ * drivers/dahdi/wcte12xp/base.c: wcte12xp: Fix bug when not
+ recognizing loopup codes The wcte12xp wasn't recognizing
+ loopup/loopdown signals. The debounce was so long that it was
+ preventing the loopup/loopdown signals from being registered
+ properly. Removed the debounce entirely as it was unnecessary to
+ the operation. Signed-off-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Acked-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Fixed a bug where it sent
+ loopdown signals forever The wct4xxp driver was resetting it's
+ maint state to NONE prematurely. Signed-off-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Acked-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+2011-07-20 17:24 +0000 [r10060-10061] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Fix compilation when
+ VPM_SUPPORT is not defined. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+ * drivers/dahdi/oct612x/include/oct6100api/oct6100_channel_inst.h:
+ oct612x: Increase the size of some of the instance variables.
+ Revision 9750 "wct4xxp: Reduce the memory footprint of the
+ hardware echocanceler" reduced the number of bits used to store
+ some structure members. Some of the new field lengths were unable
+ to store all the possible values the API as used assigned to the
+ fields, resulting in channels never entering power down mode when
+ they were disabled like they were previously. The change for
+ byEchoOperationMode was found in testing the operation of the
+ VPMOCT032 which currently uses the same code. The others were
+ done via a review of the API doc. This change represents
+ negligable risk and contains no logic changes. It only increases
+ the memory footprint of the API instance in the kernel.
+ Signed-off-by: Doug Bailey <dbailey at digium.com> Acked-by: Shaun
+ Ruffell <sruffell at digium.com> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-07-20 16:50 +0000 [r10050-10058] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * README: README: KVERS, KSRC in live.conf Signed-off-by: Tzafrir
+ Cohen <tzafrir.cohen at xorcom.com>
+
+ * build_tools/live_dahdi: live_dahdi: symlink_ast live_dahdi: Add a
+ new command: symlink_ast, to make the system's
+ /etc/asterisk/dahdi-channels.conf a symlink to the one generated
+ by 'reload' / 'genconf'. If the system dahdi-channels.conf is a
+ generated one and has not edited, there's no real harm with
+ running this. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/dahdi-base.c: get registration_mutex at free_pseudo
+ Make sure that the call to dahdi_chan_unreg() in free_pseudo() is
+ protected by the registration_mutex, like the other calls to that
+ function. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+ Acked-By: Oron Peled <oron.peled at xorcom.com> Acked-by: Shaun
+ Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/xpp/xbus-core.c: xpp: increase command queue lenge
+ to 1000 Required by CAS in latest (2.5) DAHDI versions.
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xbus-core.h: xpp: make quirk bit flags unsigned
+ This avoids a nag about a meaningless single-bit signed int.
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_pri.c: xpp: PRI_timing_priority can be
+ static. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xframe_queue.c: xpp: rate limit queue overflow
+ messages If the CPU becomes overly busy, merely printing the
+ "Overflow in the recieve_queue" messages becomes CPU-intensive on
+ its own right. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+ * build_tools/live_dahdi: live_dahdi: xpp_fxloader: use live
+ xpp.conf xpp_fxloader also reads /etc/dahdi/xpp.conf in one
+ specific case. Make it use the live copy.
+
+ * build_tools/live_dahdi: live_dahdi: no need to create asterisk at
+ genconf /etc/asterisk already gets generated at config. No need
+ to re-create it at genconf time. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-07-18 23:32 +0000 [r10047] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wcte12xp/base.c: wcte12xp: Close a potential race
+ on driver unload. The shutdown logic requires that all CPUs see
+ that the INITIALIZED bit has been cleared. Otherwise it may be
+ possible for the workqueue to run after the hardware resources
+ have been released. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Acked-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com>
+
+2011-07-12 18:15 +0000 [r10036-10038] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/Makefile: xpp: install Octasic
+ frmware if it's there If the OCT6104E-256D.ima Octasic firmware
+ was downloaded to the build directory, install it over with the
+ rest of the firmware files. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xpp_dahdi.c: xpp: Demote notices for HWEC
+ create/free to debug Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Add dynamic dahdi parameter
+ hwec_overrides_swec. If set to true (default) a HWEC, if
+ available on the channel, takes priority over any software
+ echocan configured in /etc/dahdi/system.conf. This has
+ historically been the default behavior in all released versions
+ of DAHDI that support module echocans. Otherwise,
+ hwec_overrides_swec is set to false, HWEC is chosen only via the
+ "echocanceller=hwec" directive. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Signed-off-By: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Acked-By: Oron Peled
+ <oron.peled at xorcom.com>
+
+2011-07-07 13:43 +0000 [r10028] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * build_tools/live_dahdi: live_dahdi: create asterisk in the live
+ tree Make sure you have etc/asterisk in the live tree before
+ generating configuration. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-07-05 17:23 +0000 [r10024] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.c:
+ oct612x: Eliminate some compiler warnings. Eliminate "large
+ integer implicitly truncated to unsigned type" warnings from
+ r10010. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Acked-by: Doug Bailey <dbailey at digium.com> Acked-by: Tzafrir
+ Cohen <tzafrir.cohen at xorcom.com>
+
+2011-07-04 14:05 +0000 [r10019-10022] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: xpd_fxs: ring_trapez parameter
+ This adds module parameter 'ring_trapez'. When set, the wave form
+ of the ring tone is set to be a trapezoid, rather than sine. Thus
+ making the ring stronger. This is a boolean parameter of the
+ module xpd_fxs. Takes effect at the beginning of the next ring.
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_pri.c, drivers/dahdi/xpp/card_bri.c: A
+ number of cases of testing for unsigned int < 0 Signed-off-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_bri.c, drivers/dahdi/xpp/card_echo.c: xpp:
+ Eliminate "set but unused" compiler warnings. gcc 4.6 complains
+ about variables that are assigned values but then never used.
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-By:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xbus-core.c,
+ drivers/dahdi/xpp/xbus-core.h: xpp: add FXO HWEC quirks handling
+ In some cases the hardware echo canceller cannot be used. Mostly
+ related to an FXO module. * FXO module if the first module is BRI
+ or PRI * FXS module if the Astribank has another FXO, no PRI/BRI,
+ and is a sync slave. Signed-off-by: Oron Peled
+ <oron.peled at xorcom.com> Acked-By: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-07-01 15:45 +0000 [r10016-10017] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wcb4xxp/base.c: wcb4xxp: Return NULL if there is
+ not a hardware EC on installed. r9943 enabled the presence of
+ hardware EC to be probed on a card. That change did not account
+ for wcb4xxp based cards that did not have a hardware echocan on
+ board. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Acked-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Add module parameter to
+ ignore rotary switch settings. The dual and quad span cards have
+ a rotary switch onboard which controls the order that cards
+ serviced by this driver are registered with the core of DAHDI.
+ This commit adds a module parameter 'ignore_rotary' which, when
+ set to 1, causes the driver to ignore the position of the rotary
+ switch and only consider the physical slot when registering with
+ DAHDI. Ignoring the rotary switch settings also permits the PCI
+ device to be bound and unbound from the driver at runtime since
+ registration with DAHDI no longer only happens when the module is
+ first initialized. By default, the rotary switch will still be
+ used to determine registration order. This commit does not change
+ the default behavior. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+2011-06-30 22:02 +0000 [r10010-10014] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * build_tools/live_dahdi: Also loca xpd_echo in live_dahdi, if
+ available Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/FPGA_1161.hex,
+ drivers/dahdi/xpp/firmwares/USB_FW.hex: xpp: FPGA_1161 rev 9252,
+ USB_FW rev 8826: HWEC New Astribank II FPGA firmware and USB
+ firmwares that add support for the hardware echo canceller
+ module. Note that due to a bug in previous FPGA firmwares, an
+ Astribank with such older firmware and with a hardware echo
+ canceller module will not have any functioning audio at all.
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/init_card_5_30 (added),
+ drivers/dahdi/xpp/firmwares/Makefile: xpp: also install init
+ (non)script for xpd_echo
+
+ * drivers/dahdi/oct612x/include/oct6100api/oct6100_defines.h,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.c,
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_channel_inst.h:
+ oct612x: Fixes for Octasic user space compilation: * Don't assume
+ a pointer diff is 16 bits only. * cOCT6100_INVALID_VALUE should
+ be used against 32 unsigned values * Make 3 constants adjustable
+ via '-Dmacro=value': - cOCT6100_INTERNAL_SUPER_ARRAY_SIZE -
+ cOCT6100_MAX_ECHO_CHANNELS - cOCT6100_MAX_MIXER_EVENTS
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Signed-off-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Acked-by: Doug Bailey
+ <dbailey at digium.com> Acked-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+2011-06-29 22:15 +0000 [r10000-10008] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Fix typo in previous
+ commit for fastpickup mode. I failed to compile the commit
+ exactly as it was committed. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Add 'fastpick'
+ module parameter. When true / 1 the FXO port will use a shorter
+ off-hook calibration delay. This is sometimes necessary in order
+ to properly decode Type-II Caller ID information which is sent
+ shortly after an FXO port goes off hook. Defaults to 0 unless
+ opermode is "JAPAN" then it will default to 1. This functionality
+ was ported from the wctdm.c driver. DAHDI-854. Signed-off-by:
+ Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Ensure battery drops
+ on FXS hangups honor the channel otimer. If an FXS port is
+ configured to use kewl start signalling, when the FXS port is
+ "hungup" it should drop battery for 500ms so that any attached
+ devices can detect that the remote side has disconnected. The
+ wctdm24xxp driver since version 2.4.0 was only dropping battery
+ for ~5-10 ms because it would set "open" on the line, but then
+ the next time it read the line feed register state, it was
+ setting the LINE feed register to the idle state. This change
+ checks if the line is forced open before setting the FXS port
+ back "onhook" so as to not turn on battery prematurely. This
+ fixes a regression introduced in r9070 "wctdm24xxp: Prevent FXS
+ Proslic staying in "Forward/Reverse OnHookTransfer...".
+ DAHDI-849. Checking for open on the line feed registered was
+ originally suggested by Alec Davis. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+ * include/dahdi/user.h, include/dahdi/kernel.h: Revert "dahdi: Use
+ enumeration for maintenance modes." This reverts commit r9879.
+ Asterisk commit r264249 [1], which was committed after the switch
+ to enumerations, requires the maintenance modes to be Changing
+ the test in configure.ac from: AST_C_DEFINE_CHECK([DAHDI],
+ [DAHDI_RESET_COUNTERS], [dahdi/user.h], [230]) to:
+ AST_C_COMPILE_CHECK([DAHDI], [int foo = DAHDI_RESET_COUNTERS],
+ [dahdi/user.h]) Would allow the maintenance modes to stand as
+ enumerations but the potential for users to run incompatible
+ versions does not seem worth it at this point. [1]
+ http://svnview.digium.com/svn/asterisk?view=revision&revision=264249
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by: Russ
+ Meyerriecks <rmeyerriecks at digium.com>
+
+2011-06-28 22:29 +0000 [r9997-9998] Russ Meyerriecks <rmeyerreicks at digium.com>
+
+ * drivers/dahdi/voicebus/vpmoct.c, drivers/dahdi/wcte12xp/base.c,
+ drivers/dahdi/voicebus/vpmoct.h, drivers/dahdi/wctdm24xxp/xhfc.c,
+ drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+ drivers/dahdi/wctdm24xxp/base.c,
+ drivers/dahdi/wcte12xp/wcte12xp.h: wcte12xp, wctdm24xxp: Load
+ VPMOCT032 firmware in background. The firmware load has been
+ moved into a workqueue to prevent the module load from blocking
+ for the duration of the firmware upload. This could be up to 40
+ seconds. Driver prevents configuration until firmware load is
+ finished and is_initialized() returns true. Signed-off-by: Russ
+ Meyerriecks <rmeyerriecks at digium.com> Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/voicebus/vpmoct.c (added),
+ drivers/dahdi/wcte12xp/base.c, drivers/dahdi/firmware/Makefile,
+ drivers/dahdi/voicebus/Kbuild, drivers/dahdi/voicebus/vpmoct.h
+ (added), drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+ drivers/dahdi/wctdm24xxp/base.c,
+ drivers/dahdi/wcte12xp/wcte12xp.h: wcte12xp, wctdm24xxp: Add
+ support for the VPMOCT032 hardware echocanceler. Support enabled
+ for the vpmoct032 echo cancellation module for the wctdm24xxp and
+ wcte12xp drivers. Signed-off-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+2011-06-28 21:29 +0000 [r9995] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Always attach hwec to a
+ channel if available. In previous releases of DAHDI if dahdi_cfg
+ attached a software echocan to a channel and a hardware echocan
+ was available, the hardware echocan would be used instead of the
+ software echocan. Since the 2.4 branch was created a new feature
+ was merged into dahdi-linux where it was possible to mix software
+ echocan and hardware echocan on a channel. This required using
+ "hwec" as the echocan in the /etc/dahdi/system.conf file so that
+ what was specified in the configuration file is what was actually
+ used. This has resulted in users upgrading to the trunk of dahdi
+ without updating their /etc/dahdi/system.conf file and just
+ suddenly not using any hardware echocans any longer. The
+ capability to mix software and hardware echocans on a span will
+ be revisted when running dahdi_cfg on any preexisting
+ configuration files doesn't just silently turn off hardware
+ echocan. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+2011-06-28 18:23 +0000 [r9993] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_pri.c, drivers/dahdi/xpp/card_fxo.c,
+ drivers/dahdi/xpp/xbus-sysfs.c, drivers/dahdi/xpp/card_fxs.c,
+ drivers/dahdi/xpp/Kbuild, drivers/dahdi/xpp/xproto.c,
+ drivers/dahdi/xpp/xpp_debug, drivers/dahdi/xpp/xbus-pcm.c,
+ drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xpd.h,
+ drivers/dahdi/xpp/xproto.h, drivers/dahdi/xpp/xbus-pcm.h,
+ drivers/dahdi/xpp/xpp_dahdi.h, drivers/dahdi/xpp/card_bri.c,
+ drivers/dahdi/xpp/xbus-core.c, drivers/dahdi/xpp/card_echo.c
+ (added), drivers/dahdi/xpp/card_echo.h (added),
+ drivers/dahdi/xpp/xbus-core.h: xpd_echo: XPP Octasic echo
+ canceler module * xpd_echo (card_echo.c) - a module to handle an
+ Astribank hardware echo canceller module. * All other XPDs are
+ now of type 'telephony_device'. Only a telephony device XPD
+ provides a span to register. * The EC module will typically show
+ up as XPD-40 and will always show up as Unregistered in
+ 'dahdi_hardware -v' Signed-off-by: Oron Peled
+ <oron.peled at xorcom.com> Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-06-28 15:55 +0000 [r9989-9991] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: Revert "dahdi: Group dahdi timers
+ into "rates" for improved CPU utilization." This reverts commit
+ r9891 and is part of two commits to revert all the timer changes.
+ Grouping the timer into rates did not allow a timers rate to be
+ changed after another thread is already blocked on the poll call
+ The problem that was reported was if a sip call was made to a
+ DAHDI channel and the sip call was disconnected before answer,
+ the DAHDI channel would never stop rining. Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Acked-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: Revert "dahdi: If a timer is not
+ configured then we should block indefinitely." This reverts
+ commit r9937 and is part of two commits to revert all the timer
+ changes. Grouping the timer into rates did not allow a timers
+ rate to be changed after another thread is already blocked on the
+ poll call Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Acked-by: Russ Meyerriecks <rmeyerriecks at digium.com>
+
+ * include/dahdi/kernel.h: kernel.h: Define __packed if not already
+ defined. Linux kernel v2.6.22 introduced the __packed macro to
+ allow the gcc specific __attribute__((packed)) extension to be
+ overridden if required and checkpatch.pl will complain if you
+ don't use it. For some strange reason gcc doesn't complain when
+ you use non-existant decorators. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Signed-off-by: Russ Meyerriecks
[... 4385 lines stripped ...]
More information about the svn-commits
mailing list