[dahdi-commits] sruffell: tag linux/2.5.1-rc1 r10582 - /linux/tags/2.5.1-rc1/
SVN commits to the DAHDI project
dahdi-commits at lists.digium.com
Wed Mar 21 17:03:46 CDT 2012
Author: sruffell
Date: Wed Mar 21 17:03:42 2012
New Revision: 10582
URL: http://svnview.digium.com/svn/dahdi?view=rev&rev=10582
Log:
Importing files for 2.5.1-rc1 release.
Added:
linux/tags/2.5.1-rc1/.version (with props)
linux/tags/2.5.1-rc1/ChangeLog (with props)
Added: linux/tags/2.5.1-rc1/.version
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.5.1-rc1/.version?view=auto&rev=10582
==============================================================================
--- linux/tags/2.5.1-rc1/.version (added)
+++ linux/tags/2.5.1-rc1/.version Wed Mar 21 17:03:42 2012
@@ -1,0 +1,1 @@
+2.5.1-rc1
Propchange: linux/tags/2.5.1-rc1/.version
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: linux/tags/2.5.1-rc1/.version
------------------------------------------------------------------------------
svn:keywords = none
Propchange: linux/tags/2.5.1-rc1/.version
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added: linux/tags/2.5.1-rc1/ChangeLog
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.5.1-rc1/ChangeLog?view=auto&rev=10582
==============================================================================
--- linux/tags/2.5.1-rc1/ChangeLog (added)
+++ linux/tags/2.5.1-rc1/ChangeLog Wed Mar 21 17:03:42 2012
@@ -1,0 +1,5426 @@
+2012-03-21 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux 2.5.1-rc1 tagged.
+
+2012-03-21 20:40 +0000 [r10577-10578] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: FXS: added a
+ 'lower_ringing_noise' parameter * Adds a new parameter,
+ 'lower_ringing_noise', to module xpd_fxs. * Makes the
+ "power-down" behaviour that was added in upstream svn r10478,
+ switchable in runtime. * By default (false), makes the vbat_h
+ behave like it did before the power-down change. - I.e: vbat_h is
+ held throughout the ringing period (during both
+ ring-up/ring-down) - So this patch revert part of r10478 * When
+ switched to true, activate the "power-down" behaviour. - I.e:
+ vbat_h follows the ring-up/ring-down. - This behaviour lowers the
+ noise caused by group ringing of FXS channels in the same unit,
+ but causes problems with CallerID. Signed-off-by: Oron Peled
+ <oron.peled at xorcom.com> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10574
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: FXS: atomic vbat_h power
+ handling * In do_chan_power() make vbat_h changes atomic. * As a
+ result we can ignore duplicate requests. This will allow cleaner
+ logic in the next commit. * Added proper debug messages.
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10573
+
+2012-03-20 11:19 +0000 [r10551] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/USB_FW.hex,
+ drivers/dahdi/xpp/firmwares/FPGA_1161.201.hex,
+ drivers/dahdi/xpp/firmwares/USB_RECOV.hex: xpp: firmwares:
+ useless 0x1A at EOF Remove a mostly harmless 0x1A (^Z) at the end
+ of the file. If you add a NL after it, it breaks the firmware
+ loading. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=10550
+
+2012-03-18 19:07 +0000 [r10539-10540] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/Makefile,
+ drivers/dahdi/xpp/firmwares/FPGA_1161.201.hex (added),
+ drivers/dahdi/xpp/firmwares/USB_FW.201.hex (added): xpp:
+ firmwares to support E-Main 4 USB firmware (USB_FW.201.hex 10402)
+ and FPGA firmware (FPGA_1161.201.hex 10480) with support of the
+ new E-Main 4 Astribank mainboard. (This was accidentally labeled
+ as 'E-Main 3' in some previous commit messages) Also includes
+ Makefile fixes from r10536. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10535
+
+ * drivers/dahdi/xpp/firmwares/USB_FW.hex: xpp: USB_FW rev 10401:
+ minor 6FXS/2FXO caps issue Fixes an issues with the 6FXS/2FXO
+ module: if an extra FXS or FXO module is added to a system with
+ such a module, an excessive number of port licenses was
+ accidentally required (as if the 6FXS/2FXO module required
+ 8FXS/8FXO licenses). Internal-Issue-ID: #1371 Signed-off-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10534
+
+2012-03-16 16:11 +0000 [r10527-10529] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/xpp/xproto.c: xpp: '%d' -> '%lu' when displaying
+ module_refcount on kernel versions >= 3.3 Upstream commit
+ bd77c047 "module: struct module_ref should contains long fields"
+ changed the return of module_refcount from int to unsigned long.
+ This change eliminates a warning from the string format
+ specifier. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Acked-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10485 Conflicts:
+ drivers/dahdi/xpp/xproto.c
+
+ * drivers/dahdi/xpp/xpd.h: xpp: Use 'bool' type for boolean module
+ parameters on kernel versions >= 2.6.31. Eliminates warnings that
+ are a result of upstream commit 72db395ffa "module_param: check
+ that bool parameters really are bool." Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10484 Conflicts:
+ drivers/dahdi/xpp/xpd.h
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Fix bug if hook
+ state on FXS changes before channel configuration. If the hook
+ state on an FXS port changes before the channel is configured
+ with dahdi_cfg it is possible to erroneously force the line feed
+ register open without setting a timer to clear it. The result
+ would be a "dead" channel that cannot be cleared unless the
+ driver is reloaded and warning in the kernel log that "0 is an
+ invalid signaling state for an FXS module". This change makes the
+ OFF_HOOK to ON_HOOK change behave just as the ON_HOOK to OFF_HOOK
+ change has. Internal-Issue-ID: DAHLIN-272 Reported-and-Tested-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10396
+
+2012-03-15 17:33 +0000 [r10487-10488] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: FXS: better power-down to
+ lower noise * Now every linefeed control command which is not
+ RING'ing powers-down the SLIC. This reduce audible noise when
+ several channels are ringing. * Simplify code by removing
+ redundant calls to do_chan_power() before linefeed_control() *
+ Manage vbat_h state so we skip do_chan_power() calls when there
+ isn't a state change * Export vbat_h state to /proc/.../fxs_info
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10478
+
+ * drivers/dahdi/xpp/card_global.c, drivers/dahdi/xpp/card_global.h:
+ xpp: reset Astribank SPI busses * A driver reload should reset
+ Astribank hardware * This patch send an SPI reset after we get
+ AB_DESCRIPTION reply from Astribank Signed-off-by: Oron Peled
+ <oron.peled at xorcom.com> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10474
+
+2012-02-07 22:17 +0000 [r10456] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/Makefile,
+ drivers/dahdi/xpp/firmwares/USB_RECOV.hex (added): USB_RECOV.hex:
+ recovering from xpp hardware issues USB_RECOV.hex, rev. 9760. It
+ may be used to recover from certain issues of the USB controller
+ of the Astribank (when an Astribank is not detected as such) by
+ Support staff. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10455
+
+2012-01-25 19:56 +0000 [r10444] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/FPGA_FXS.hex,
+ drivers/dahdi/xpp/firmwares/FPGA_1141.hex,
+ drivers/dahdi/xpp/firmwares/FPGA_1151.hex: Astribank I firmwares
+ rev. 7107 A slightly newer firmware (Xorcom rev. 7107) for older
+ (non Astribank II) Astribank modules. Was accidentally left
+ uncommited. Includes minor bug fixes. No change for any
+ relatively recent (Astribank II) Astribank. Signed-off-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10443
+
+2012-01-17 14:46 +0000 [r10441] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * README, drivers/dahdi/Kbuild: Build OSLEC EC if in the tree Build
+ the OSLEC echo canceller (drivers/staging/echo and
+ dahdi_echocan_oslec) if the code of oslec is present in the tree.
+ Also closing another issue regarding documentation of building
+ OSLEC, as it is now even clearer than before. Patch has been used
+ in the Debian package for quite some time. Signed-off-by: Tzafrir
+ Cohen <tzafrir.cohen at xorcom.com> (closes issue DAHLIN-110)
+ Reported by: biohumanoid (Pavel Selivanov) Patches:
+ oslec_auto.diff uploaded by tzafrir (license 5035) (closes issue
+ DAHLIN-261) Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10440
+
+2012-01-11 12:03 +0000 [r10420] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xpp_dahdi.c: xpp: bugfix: fix bad refcount Code
+ path called in error condition contained an superflous put_xpd()
+ call Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-By:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10408
+
+2012-01-03 22:55 +0000 [r10391-10398] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/Kbuild: Avoid building PCI devices if kernel has no
+ PCI Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_bri.c: xpp: BRI: batch D-Channel packets
+ to fix frag. * We need to split the BRI D-Channel (HDLC) frames
+ to smaller packets, limitation of the FPGA. * This changes
+ batches BRI D-channel packets of the same HDLC frame to a single
+ XPP frame. * Avoids an accidental fragmantion in case we were
+ delayed for a few ms-s. * Also improves efficiency.
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-By:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_global.c, drivers/dahdi/xpp/card_bri.c:
+ xpp: BRI: split multibyte functionality * The zero lenth case
+ (Magic request) was split into send_magic_request() function. It
+ was not possible to move it into card_bri.c, because it is called
+ directly from the general interface we provide for register
+ read/write via sysfs/proc. * The normal case
+ (send_multibyte_request) was moved from card_global.c into
+ card_bri.c * This sets the stage to enable bundling of multibyte
+ packets into frames (like we do for PCM). Signed-off-by: Oron
+ Peled <oron.peled at xorcom.com> Acked-By: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_bri.c: xpp: BRI: remove trivial BRISTUFF
+ wrappers Now that legacy BRISTUFF code is gone, some wrapper
+ functions became trivial. Removed these wrappers and inlined
+ their contents. Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+ Acked-By: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/card_bri.c: xpp:
+ BRI: remove legacy BRISTUFF code Signed-off-by: Oron Peled
+ <oron.peled at xorcom.com> Acked-By: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-12-21 18:38 +0000 [r10385-10386] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xbus-core.h: xpp: Allow up to 128 Astribanks on
+ a system This is also a work around the bug fixed in the previous
+ commit. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xbus-core.c: xpp: bad module_put() when too
+ many Astribanks module_put() that was added while developing the
+ sysfs code. The real module_get()/module_put() pair were already
+ removed at the time of developing code for this branch. It was
+ only triggered when using a system with more than 32 (MAX_BUSES)
+ Astribanks. Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+ Acked-By: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+2011-12-12 18:28 +0000 [r10378] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Do not call
+ voicebus_release() before wctdm_back_out_gracefully()
+ voicebus_release is already called as part of the
+ wctdm_back_out_gracefully() call. If an Hx8 card fails to
+ initialize, this will eliminate warnings from the kernel such as:
+ WARNING: at kernel/irq/manage.c:904 __free_irq+0x94/0x173()
+ Trying to free already-free IRQ 18 Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10377
+
+2011-12-07 19:45 +0000 [r10374-10376] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_bri.c: xpp: BRI: fix timing priority
+ calculation Use similar caculation as in the PRI module: * Save
+ timing_priority from spanconfig and elect syncer when spanconfig
+ is called. * Create custom timing_priority() function that
+ returns the value or error if span is disconnected.
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by: :
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: FXS: mwi and search_fsk fixes
+ * We must not block PCM during from 'search_fsk_pattern'
+ channels. * We must vmwi_search() not only on
+ FXS_LINE_POL_ACTIVE, but also during 'neon_blinking' -- so we
+ notice the message to turn it off. * Also added
+ 'search_fsk_pattern' and neon_blinking to /proc/.../fxs_info
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by: :
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xpp_dahdi.c: xpp: bugfix -- manage xpd refcount
+ for EC module Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-12-02 20:06 +0000 [r10362-10363] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/voicebus/GpakCust.h, include/dahdi/kernel.h: dahdi:
+ #include <linux/module.h> in dahdi/kernel.h and GpakCust.h Commit
+ de47725, first released in 3.2-rc1 removed module.h from some
+ kernel headers. Include it explicitly now. Resolves compilation
+ errors like: error: implicit declaration of function
+ 'try_module_get' error: 'THIS_MODULE' undeclared (first use in
+ this function) error: implicit declaration of function
+ 'module_put' Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=10361
+ Conflicts: include/dahdi/kernel.h
+
+ * drivers/dahdi/wctc4xxp/base.c: wctc4xxp: Replace
+ 'ndo_set_multicast_list' with 'set_rx_mode' The
+ ndo_set_multicast_list callback was removed in b81693d9, which
+ was first released in Linux Kernel 3.2-rc1 Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10360
+
+2011-11-30 10:22 +0000 [r10351-10353] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_pri.c: xpp: pri: fix RS1 init in E1 CAS
+ mode Force some reserved bits to really be 1 in E1 mode
+ (otherwise terrorists will win). (Closes issue DAHLIN-264)
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: fxs: demote SETPOLARITY
+ message to DBG() Signed-off-by: Oron Peled
+ <oron.peled at xorcom.com>
+
+ * drivers/dahdi/xpp/card_global.c, drivers/dahdi/xpp/xbus-core.h,
+ drivers/dahdi/xpp/init_card_1_30, drivers/dahdi/xpp/xpp_usb.c:
+ xpp: Adaptations for E-Main-3 * An xbus transport now have a
+ "model_string" member * The xpp_usb driver fills this with
+ "usb:<idVendor>/<idProduct>/<bcdDevice>" * It is passed via
+ environment to the "init_card_<type>_<protocol>" scripts * The
+ FXS script uses this to condition two registers according to the
+ power supply model. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+2011-11-16 12:17 +0000 [r10342] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/xbus-core.c: xpp: increase command queue length
+ to 1500 A length of 1000 commands is not enough is some cases
+ with CAS. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+2011-11-13 15:11 +0000 [r10336-10340] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/USB_FW.hex: xpp: USB_FW rev 10085:
+ fix regression from r10324 Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/PIC_TYPE_1.hex: xpp: PIC_TYPE_1 rev
+ 9841: followup to r10324 An extra fix that was accidentally not
+ included in r10324. Minor bug fixes. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_pri.c: xpp: silence some bad ioctl()
+ reporting Ignore some FXS-specific ioctl-s in xpd_pri.
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+2011-11-07 15:55 +0000 [r10324] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/USB_FW.hex: xpp: USB firmware r9964:
+ minor bugfixes USB_FW rev 9964: includes a few stability
+ bugfixes. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+2011-11-02 20:01 +0000 [r10305] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: First span registered becomes
+ master by default. r10205 "dahdi: Check for master in
+ DAHDI_STARTUP / resolves MeetMe regression." did not handle the
+ case for the wcb4xxp driver since it would set DAHDI_FLAG_RUNNING
+ as part of the probe. Therefore, the DAHDI_STARTUP ioctl was
+ never processed for it, creating a situation where audio is
+ missing on channels that are conferenced with channels on the BRI
+ spans. Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10304
+
+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>
+
[... 4706 lines stripped ...]
More information about the dahdi-commits
mailing list