[svn-commits] sruffell: tag linux/2.4.1 r9785 - in /linux/tags/2.4.1: .version ChangeLog
SVN commits to the Digium repositories
svn-commits at lists.digium.com
Thu Mar 3 14:05:55 CST 2011
Author: sruffell
Date: Thu Mar 3 14:05:53 2011
New Revision: 9785
URL: http://svnview.digium.com/svn/dahdi?view=rev&rev=9785
Log:
Importing files for 2.4.1 release.
Added:
linux/tags/2.4.1/.version (with props)
linux/tags/2.4.1/ChangeLog (with props)
Added: linux/tags/2.4.1/.version
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.4.1/.version?view=auto&rev=9785
==============================================================================
--- linux/tags/2.4.1/.version (added)
+++ linux/tags/2.4.1/.version Thu Mar 3 14:05:53 2011
@@ -1,0 +1,1 @@
+2.4.1
Propchange: linux/tags/2.4.1/.version
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: linux/tags/2.4.1/.version
------------------------------------------------------------------------------
svn:keywords = none
Propchange: linux/tags/2.4.1/.version
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added: linux/tags/2.4.1/ChangeLog
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.4.1/ChangeLog?view=auto&rev=9785
==============================================================================
--- linux/tags/2.4.1/ChangeLog (added)
+++ linux/tags/2.4.1/ChangeLog Thu Mar 3 14:05:53 2011
@@ -1,0 +1,3700 @@
+2011-03-03 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux version 2.4.1 released.
+
+2011-02-11 17:52 +0000 [r9757-9760] Shaun Ruffell <sruffell at digium.com>
+
+ * build_tools/make_version: make_version: Use 'git rev-parse' if
+ only looking for a sha5. Different versions of git have
+ variability in how the log output looks. Instead of git log, we
+ can use git rev-parse directly. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9475
+
+ * build_tools/make_version: make_version: svn and git metadata
+ directory not checked properly. (closes issue #16143) Reported
+ by: Max Khon Signed-off-by: Kinsey Moore <kmoore at digium.com>
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9418
+
+ * build_tools/make_version: make_version: '[[' -> '[' since it's
+ not a bash script. '[[' is a bash construct specifically, yet
+ #!/bin/sh is at the top of the file. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Acked-by: Kinsey Moore <kmoore at digium.com>
+ Acked-by: Russ Meyerriecks <rmeyerriecks at digium.com> Acked-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Review:
+ https://reviewboard.asterisk.org/r/940/ Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9408
+
+ * Makefile, build_tools/make_version: dahdi: Generate
+ include/dahdi/version.h when building in a git repository. If
+ building within a git repository search the last log message for
+ a 'git-svn-id'. If found, the commit has a corresponding svn
+ revision number and we will use the SVN-xxx-rxxx revision form.
+ Otherwise use the output of 'git describe --long --always --tags
+ --dirty=M' as the version. 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=9396
+
+2011-02-10 16:29 +0000 [r9746-9755] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wct4xxp/vpm450m.c: wct4xxp: Do not lock interrupts
+ while loading the VPM firmware. Since the oct6100 API consumes
+ less stack there is no longer a danger of overflowing our stack
+ during load. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=9752
+
+ * drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_tlv.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_phasing_tsst.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_playout_buf.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_interrupts.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_stats.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_conf_bridge.c,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_miscellaneous_priv.h,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_events.c:
+ wct4xxp: Reduce stack usage in oct612x API. Reduce the stack
+ usage by replacing the mOCT6100_RETRIEVE_NLP_CONF_DWORD and
+ mOCT6100_SAVE_NLP_CONF_DWORD macros with functions. Some
+ compilers do a better job of optimizing the local variables
+ declared in those macros than others. For example, with gcc
+ 4.3.0, running ]# make stackcheck | grep Oct6100 | head -n 20 |
+ sed -e 's/^0\S* //g' | uniq Before: Oct6100ApiWriteVqeNlpMemory
+ [wct4xxp]: 1112 Oct6100ApiInvalidateChanPlayoutStructs
+ [wct4xxp]:520 Oct6100ApiSetChannelLevelControl [wct4xxp]: 392
+ Oct6100ApiBridgeEventRemove [wct4xxp]: 344
+ Oct6100ApiDebugChannelOpen [wct4xxp]: 312
+ Oct6100ApiWriteVqeAfMemory [wct4xxp]: 296
+ Oct6100ApiSetChannelTailConfiguration [wct4xxp]:264
+ Oct6100ApiRandomMemoryWrite [wct4xxp]: 248
+ Oct6100ApiTransferToneEvents [wct4xxp]: 248
+ Oct6100ApiModifyChannelStructs [wct4xxp]: 232 After:
+ Oct6100ApiBridgeEventRemove [wct4xxp]: 344
+ Oct6100ApiDebugChannelOpen [wct4xxp]: 312
+ Oct6100ApiRandomMemoryWrite [wct4xxp]: 248
+ Oct6100ApiTransferToneEvents [wct4xxp]: 248
+ Oct6100ApiInvalidateChanPlayoutStructs [wct4xxp]:248
+ Oct6100ApiModifyChannelStructs [wct4xxp]: 232
+ Oct6100ApiBridgeRemoveParticipantFromChannel [wct4xxp]:216
+ Oct6100ApiWriteVqeNlpMemory [wct4xxp]: 200 Oct6100ApiInitChannels
+ [wct4xxp]: 168 Oct6100ApiProgramNLP [wct4xxp]: 168 Signed-off-by:
+ Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9751
+
+ * drivers/dahdi/oct612x/include/oct6100api/oct6100_chip_open_inst.h,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_channel.c,
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_channel_inst.h,
+ drivers/dahdi/wct4xxp/vpm450m.c,
+ drivers/dahdi/oct612x/include/oct6100api/oct6100_defines.h,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_miscellaneous_priv.h,
+ drivers/dahdi/oct612x/octdeviceapi/oct6100api/oct6100_api/oct6100_chip_open.c:
+ wct4xxp: Reduce the memory footprint of the hardware
+ echocanceler. This saves ~300K of kernel memory for each quad or
+ dual span VPM. Due to the fact that this change disables caching
+ of the NLP words (among other things), the time to disable the
+ echocans appears to have increased by ~1ms. Before this change:
+ =======================================================================
+ 0) ! 356.498 us | vpm450m_setecmode(); <--- disable 0) ! 387.762
+ us | vpm450m_setecmode(); <--- enable 0) ! 429.839 us |
+ vpm450m_setecmode(); <--- disable ]# echo 1 >
+ /proc/sys/vm/drop_caches && free -k total used free shared
+ buffers cached Mem: 2005352 228368 1776984 0 132 5540 -/+
+ buffers/cache: 222696 1782656 Swap: 983036 0 983036 After this
+ change:
+ =======================================================================
+ 0) ! 1109.515 us | vpm450m_setecmode(); <--- disable 0) ! 339.017
+ us | vpm450m_setecmode(); <--- enable 0) ! 1431.460 us |
+ vpm450m_setecmode(); <--- disable ]# echo 1 >
+ /proc/sys/vm/drop_caches && free -k total used free shared
+ buffers cached Mem: 2005352 228080 1777272 0 112 5484 -/+
+ buffers/cache: 222484 1782868 Swap: 983036 0 983036
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9750
+
+ * include/dahdi/kernel.h: dahdi: Add '#include <linux/kobject.h>'
+ in dahdi/kernel.h linux/kobject.h was removed from linux/fs.h in
+ upstream commit 57cc721. Add it back in in order to pick up the
+ linux/kref.h include. Reported-by: Raoul Bönisch
+ <jkl345 at alice-dsl.net> Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9697
+
+2011-02-09 12:45 +0000 [r9745] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * build_tools/live_dahdi: live_dahdi: Fix regression from r9508
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9532
+
+2011-01-31 18:09 +0000 [r9723-9726] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Experimentally remove
+ dependency on the Big Kernel Lock. With the release of Linux
+ 2.6.37, the Big Kernel Lock is now a compile time option. This
+ change adds a mutex around the one place in the code that we
+ already knew was dependent on the lock_kernel/unlock_kernel calls
+ for serialization and drops the other calls to
+ lock_kernel/unlock_kernel if CONFIG_BKL is not defined. This is
+ *mostly* the dahdi-no-bkl.patch with a few minor whitespace
+ changes, the global_dialparmslock made static, and a warning
+ added to let people know they are running an experimental
+ configuration. (issue #18604) Reported by: jkroon Patches:
+ dahdi-no-bkl.patch uploaded by jkroon (license 714)
+ Signed-off-by: Jaco Kroon <jaco at uls.co.za> Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9721
+
+ * drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+ drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Remove code for
+ unsupported modules. The VPM100 and S100M modules are no longer
+ supported. Analog cards supported by the wctdm24xxp are still
+ compatible with the S110 and VPMADT032 modules. DAHDI-302
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9720
+
+ * Makefile: dahdi: Add '+' on KMAKE definition to enable parallel
+ make. Now 'make -j 5' works the way it's supposed to on multi
+ core machines. On one test machine build times went from ~33
+ seconds to ~11 seconds. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Acked-by: Kinsey Moore <kmoore at digium.com>
+ Acked-by: Russ Meyerriecks <rmeyerriecks at digium.com> Acked-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Review:
+ https://reviewboard.asterisk.org/r/940/ Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9409
+
+2011-01-27 21:09 +0000 [r9702] Matthew Fredrickson <creslin at digium.com>
+
+ * drivers/dahdi/wcb4xxp/base.c: Fix for bugs in timing selection
+ when B410P card is not the first configured card in system.
+
+2011-01-21 05:35 +0000 [r9652-9696] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Perform an extended reset
+ on PCI-Express cards by default. Extended reset is needed
+ primarily with the PCI express version of the dual and quad-span
+ cards. Enable it by default for those cards and allow it to be
+ forced on or off globally for the driver as a compile time
+ option. The options to force it should be able to come out if
+ there aren't any further reports that the compile time option
+ needs to be set. DAHDI-773 Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9635
+
+ * README: README: clarify required kernel configuration
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9619
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Add error if CONFIG_BKL is not
+ defined Might help when someone wonders why they are now getting
+ errors about "lock_kernel" being undefined. Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Acked-by: Kinsey Moore
+ <kmoore at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9592
+
+ * drivers/dahdi/wcte12xp/base.c: wcte12xp: Remove unused functions
+ from t1_span_ops. 'open' and 'close' were already empty.
+ 't1xxp_shutdown' only cleared DAHDI_FLAGBIT_RUNNING which is
+ already done in dahdi-base.c after calling shutdown. Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9318
+
+ * drivers/dahdi/wcfxo.c, drivers/dahdi/tor2-hw.h,
+ drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wcb4xxp/base.c,
+ drivers/dahdi/pciradio.c, include/dahdi/kernel.h,
+ drivers/dahdi/wct4xxp/base.c, drivers/dahdi/wcte11xp.c,
+ drivers/dahdi/wct1xxp.c, drivers/dahdi/wctc4xxp/base.c,
+ drivers/dahdi/wctdm.c, drivers/dahdi/wctdm24xxp/base.c: "struct
+ pci_device_id[]" -> "DEFINE_PCI_DEVICE_TABLE" 2.6.25 added the
+ DEFINE_PCI_DEVICE_TABLE macro to make sure that the pci_device_id
+ tables are put into the correct section in the binary. Convert
+ all the places where the tables were defined to use them. This is
+ linux-2.6 commit where the change went in along with the
+ rationale: 90a1ba0c5e39eeea278f263c28ae02166c5911c8
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+ Kinsey Moore <kmoore at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9584
+
+ * include/dahdi/kernel.h: dahdi: If mutexes are not available use
+ semaphores instead. Mutexes were added in 2.6.16. This will allow
+ future changes to use the mutex API without breaking on pre
+ 2.6.16 kernels. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Acked-by: Kinsey Moore <kmoore at digium.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=9579
+
+ * drivers/dahdi/wcb4xxp/base.c: wcb4xxp: HDLC packets do not pass
+ over D-channel. dahdi/wcb4xxp driver used with Digium Wildcard
+ B410 quad-BRI PCI card unable to communicate with another ISDN
+ device (ISDN phone, another port of B410). It appears that
+ B-channels are capable to transport data, but D-channel is not.
+ Debug output added into the driver shows that packets are
+ transmitted to the D-channel, but no packets are received.
+ Further investigation shows that no interrupts received from Rx
+ FIFO associated with D-channel, although packets are delivered to
+ the FIFO. I've found that problem is in improper usage of
+ chan->chanpos while indexing the fifo index (bspan->fifos):
+ chanpos starts from 1 and fifos starts from 0. Therefore, garbage
+ read instead of fifo number. (closes issue #14834) Reported by:
+ vvv Patches: dahdi-linux-complete-2.2.0-rc1.patch uploaded by vvv
+ (license 741) Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=9555
+
+ * drivers/dahdi/vpmadt032_loader/dahdi_vpmadt032_loader.c:
+ wcte12xp, wctdm24xxp: Do not call pci_set_drvdata after device
+ initialization. Instead of using pci_set_drvdata embed the
+ 'struct voicebus_operations' directly in the context so we can
+ use container_of to find the context. This resolves a problem
+ where the 'remove_one' callback gets an invalid pointer to
+ 'struct t1' if the VPMADT032 is in the middle of a reload when
+ the module is unloading. DAHDI-783. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9554
+
+ * drivers/dahdi/voicebus/voicebus.c: wctdm24xxp, wcte12xp: Disable
+ PCI read-line multiple command. There are some platforms where
+ the read-line multiple transaction causes packets to be dropped
+ in the voicebus pipeline. The only observable behavior is that
+ packets just go "missing" in the pipeline. This also only appears
+ to affect PCI cards. A typical 'symptom' of this problem is you
+ may see IRQ misses increasing without any corresponding "bumps"
+ in latency in the kernel message log. Normally, IRQ misses are
+ correlated to latency bumps since that is an indication that the
+ host was not able to service the card interrupt in a timely
+ fashion. DAHDI-510 DAHDI-774 Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Signed-off-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Acked-by: Kinsey Moore
+ <kmoore at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9542
+
+ * drivers/dahdi/wct4xxp/vpm450m.c: wct4xxp: Close a memory leak in
+ the VPM450 error path. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Acked-by: Kinsey Moore <kmoore at digium.com>
+ Acked-By: Russ Meyerriecks <rmeyerriecks at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9539
+
+ * drivers/dahdi/voicebus/voicebus.c: wctdm24xxp, wcte12xp: Lock
+ interrupts when recovering from an underrun. This reduces the
+ chance that another interrupt will interfere with the recovery
+ process. Otherwise it is possible that the hardware advances past
+ the position that we think it is currently at. Signed-off-by:
+ Shaun Ruffell <sruffell at digium.com> Acked-by: Kinsey Moore
+ <kmoore at digium.com> Acked-By: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9535
+
+ * drivers/dahdi/voicebus/voicebus.c: wctdm24xxp, wcte12xp: Add more
+ descriptive message on a failed reset. Reading 0xffffffff from
+ the registers is a different error than just not coming out of
+ reset. Add a little extra debugging information. Signed-off-by:
+ Shaun Ruffell <sruffell at digium.com> Acked-by: Kinsey Moore
+ <kmoore at digium.com> Acked-By: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9534
+
+ * drivers/dahdi/wcte12xp/base.c, include/dahdi/kernel.h: wcte12xp:
+ Use interruptible waits to decrease impact on load average. The
+ wcte12xp does all the checking for alarm in a user space
+ workqueue. Most of this time is spent sleeping waiting for reads
+ from the framer to complete. Tasks in uninterruptible sleeps are
+ added to running tasks for the purposes of calculating load
+ average. This change makes the sleeps interruptible so as to not
+ affect the load average as much. For example, the following
+ command will load and configure the driver and then print the
+ load average every 10 seconds. ]# modprobe wcte12xp && dahdi_cfg
+ && ((x=12)); while [[ $x -gt 0 ]]; do cat /proc/loadavg; sleep
+ 10; let x=$x-1; done With this change: 0.29 0.10 0.02 1/101 29945
+ 0.24 0.10 0.02 1/101 29967 0.20 0.09 0.02 1/101 30019 0.17 0.09
+ 0.02 1/101 30041 0.15 0.09 0.02 1/101 30062 0.12 0.08 0.02 1/101
+ 30085 0.10 0.08 0.02 1/101 30107 0.09 0.08 0.02 1/101 30129 0.07
+ 0.08 0.02 1/101 30151 0.14 0.09 0.02 1/101 30173 0.12 0.09 0.02
+ 1/101 30195 0.10 0.08 0.02 1/101 30217 (and I've seen it get down
+ to 0.0) Before this change: 0.57 0.22 0.07 1/101 31920 0.48 0.21
+ 0.07 1/101 31942 0.48 0.22 0.07 1/101 31964 0.48 0.23 0.08 1/101
+ 31986 0.41 0.22 0.07 1/101 32008 0.42 0.23 0.08 1/101 32030 0.43
+ 0.24 0.08 1/101 32054 0.45 0.25 0.09 1/101 32076 0.45 0.25 0.09
+ 1/101 32098 0.46 0.26 0.10 1/101 32120 0.47 0.27 0.10 1/101 32172
+ 0.39 0.26 0.10 1/101 32194 (closes issue #18142) Reported by:
+ foxfire Tested by: foxfire Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9512
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Prevent unloadable module on
+ failed open. If chan->span->ops->open() fails then the reference
+ count of the module implementing the board driver will not be
+ decremented. The result is a module that would always be "in use"
+ and unloadable. This change makes sure to release that reference
+ when open failed. (closes issue #18422) Reported by: avarvit
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+ Angelos Varvitsiotis <avarvit at admin.grnet.gr> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9510
+
+ * build_tools/live_dahdi: live_dahdi: fix usage of xpp.conf Link
+ live/usr/share/dahdi/xpp.conf from live/etc/dahdi/xpp.conf in
+ 'config'. This makes the 'live' xpp.conf used rather than the
+ global xpp.conf . Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9508
+
+ * drivers/dahdi/xpp/card_pri.c: xpd_pri: Remove pointless hooksig
+ span op If the span reports that it supports hooksig, DAHDI may
+ fail to use RBS. So remove a call to that stub function.
+ Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9506
+
+ * drivers/dahdi/xpp/card_pri.c: xpd_pri: ignore DAHDI_VMWI and
+ DAHDIVMWI_CONFIG This fixes an annoying, though harmless issue:
+ if Asterisk decides to send voicemail messages to a channel (CAS,
+ configured as FXS), We can't do anything useful with them. So
+ ignore them to avoid scary-looking messages (from
+ report_bad_ioctl()). Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9505
+
+ * drivers/dahdi/voicebus/voicebus.c: wctdm24xxp, wcte12xp: Close a
+ few potential resource assignment leaks. There were some routes
+ through the failure paths in __voicebus_init() where a registered
+ memory region was not subsequently released. This change closes
+ those paths. The result would be on subsequent loads of the
+ driver after hitting the failure condition you would see "IO
+ Registers are in use by another module." in dmesg.
+ request_mem_region/release_mem_region should most likely be
+ converted to devm_request_region and devm_release_region
+ introduced in 2.6.20 (commit
+ 9ac7849e35f705830f7b016ff272b0ff1f7ff759) which was introduced
+ for reasons just such as this. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9503
+
+ * build_tools/live_dahdi: live_dahdi: only check for TOOLS_DIR when
+ used Only check that TOOLD_DIR is valid when it is actually
+ needed (configure, install, config). This allows not checking for
+ it with *load on a rsync-ed copy. Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9479
+
+ * drivers/dahdi/hpec/dahdi_echocan_hpec.c,
+ drivers/dahdi/xpp/xpp_usb.c, include/dahdi/kernel.h,
+ drivers/dahdi/wctdm24xxp/xhfc.c,
+ drivers/dahdi/voicebus/voicebus.c, drivers/dahdi/wctc4xxp/base.c,
+ drivers/dahdi/wctdm24xxp/base.c, drivers/dahdi/xpp/xbus-core.c:
+ Remove mutex emulation Using semaphores as mutexes was removed
+ from the kernel in 4882720b267b. Just use straight semaphores
+ now. 'DECLARE_MUTEX()' -> 'DEFINE_SEMAPHORE()' and 'init_MUTEX()'
+ -> 'sema_init()'. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> LKML-Reference:
+ <20100907125057.562399240 at linutronix.de> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9464
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Detect FXS modules
+ based on the 3210 SLIC. Fixes a regression introduced in revision
+ 5916 where FXS modules based on the 3210 were not properly
+ detected. (closes issue #18184) Reported by: bsexton Patches:
+ dahdi-fxo-detect.diff uploaded by bsexton (license 1133)
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9456
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Leave FXO (DAA)
+ always in full-wave ring detect mode. In zaptel commit 4096 [1],
+ all the debouncing of ring signals were moved into software as
+ opposed to using the ring validation circuit in DAA. That commit
+ failed to remove the initial check and set of the ring validation
+ circuit. [1]
+ http://svn.digium.com/view/zaptel?view=revision&revision=4096
+ (closes issue #16894) Reported by: rde42 Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Acked-by: Kinsey Moore
+ <kmoore at digium.com> Acked-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9441
+
+ * drivers/dahdi/firmware/Makefile: dahdi: '-o' -> '--no-same-owner'
+ in drivers/dahdi/firmware/Makefile It appears that in Centos 4,
+ the version of tar doesn't like the -o flag, but will honor the
+ --no-same-owner flag. (closes issue #16063) Reported by: tzafrir
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+ Kinsey Moore <kmoore at digium.com> Acked-by: Russ Meyerriecks
+ <rmeyerriecks at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9434
+
+ * drivers/dahdi/voicebus/voicebus.c: wcte12xp, wctdm24xxp: Do not
+ rely on polling main memory. The voicebus library by default
+ configures the PCI interface to poll the descriptor ring for
+ available buffers. There are some platforms like the Intel
+ SG3420P motherboard where this does not appear to be sufficient.
+ Writing to the transmit demand poll register resolves this
+ problem on these troublesome platforms. DAHDI-700 DAHDI-702.
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9397
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Drop usage of 'volatile'
+ qualifier. The registers on the device are already accessed with
+ readl/writel and the readchunk and writechunk are mapped into
+ coherent DMA region. The contents of those buffers should not be
+ changing in the middle of any transmit/receive prep call.
+ 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=9400
+
+ * include/dahdi/dahdi_config.h: dahdi: Make CONFIG_DAHDI_PPP off by
+ default. Before CONFIG_DAHDI_PPP can be on by default, some more
+ work needs to be done to ensure that the ppp_generic module is
+ not always loaded and that all channels do not carry around all
+ the PPP members unnecessarily. (issue #17990) Signed-off-by:
+ Shaun Ruffell <sruffell at digium.com> Acked-by: Kevin P. Fleming
+ <kpfleming at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9392
+
+ * include/dahdi/dahdi_config.h: dahdi: Fix for when PPP support is
+ compiled as a kernel module. When compiling dahdi-linux I expect
+ ppp support to be compiled in even if the kernel config has PPP
+ configured as a module. (closes issue #17990) Reported by: jkroon
+ Patches: dahdi-config-ppp.diff uploaded by jkroon (license 714)
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=9328
+
+ * drivers/dahdi/voicebus/GpakCust.c: vpmadt032: Remove potential
+ endless waits when resetting. It is possible to softlock if the
+ board stops delivering interrupts in the middle of a reset.
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9332
+
+ * drivers/dahdi/voicebus/GpakCust.c: vpmadt032: Honor the
+ CONFIG_DAHDI_NO_ECHOCAN_DISABLE flag. Setting this configuration
+ option would not have had any impact when a hardware echo
+ canceler was in use. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Acked-by: Kinsey Moore <kmoore at digium.com>
+ Acked-by: Russ Meyerriecks <rmeyerriecks at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9432
+
+ * drivers/dahdi/xpp/init_card_4_30: xpp: Fixes init error for PRI
+ devices with < 4 ports Fixes a regression singce r8873: if
+ pri_protocol is not explicitly set (in /etc/dahdi/xpp.conf) and
+ the device has (licences for) less than 4 "PRI" (E1/T1) ports,
+ the initialization script will attempt to read from a
+ non-existing SysFS file, and bail out, resulting in a the device
+ failing to initialize. For those non-existing ports we can just
+ skip that part of the initialization. So we just skip it. Work
+ around: explicitly set pri_protocol to E1 or T1, as needed.
+ Xorcom Rev: 8047. Ticket: 1334. Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9430
+
+ * drivers/dahdi/dahdi-base.c, include/dahdi/kernel.h: dahdi:
+ Anonymous member in dahdi_echocan_events union. Make explicit
+ what part of the union is being accessed. (closes issue #15908)
+ Reported by: ys Patches: dahdi-dahdi_echocan_events.diff uploaded
+ by ys (license 281) Signed-off-by: Kinsey Moore
+ <kmoore at digium.com> Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9421
+
+ * drivers/dahdi/dahdi-base.c, drivers/dahdi/dahdi_echocan_kb1.c,
+ drivers/dahdi/dahdi_echocan_mg2.c: dahdi: Fix 'void *' pointer
+ arithmetic warnings. (closes issue #15927) Reported by: Max Khon
+ Patches: dahdi_echocan2.diff uploaded by Max Khon (license 884)
+ void2.diff uploaded by Max Khon (license 884) Signed-off-by:
+ Kinsey Moore <kmoore at digium.com> Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9420
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Add optional FXO
+ digital loopback if DEBUG is defined. This module parameter will
+ allow patgen/pattest to be used only on FXO ports. *ALL* FXO
+ ports will be placed in digital loopback mode when set. The
+ current intent is for this to be removed as an optional module
+ parameter when there is a channel by channel representation in
+ sysfs. Otherwise, a new IOCTL would have to be defined and a tool
+ written in order to support this. DAHDI-696. Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9391
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Be more tolerant of surprise
+ removal of channels. Enable DAHDI to detect if an operation on a
+ file handle refers to a channel that may have been unregistered.
+ This can occur, for example, when a board driver is hot-swapped
+ out in a live system. This patch ensures that file->private_data
+ is always properly set for any open channel, and it's set back to
+ NULL when a channel is unregistered. This way file->private_data
+ can be used to check whether it's valid to perform an operation
+ on the channel. (NOTE: There is still a race condition here if
+ the driver was unbound on one processor during the window of time
+ between when file->private_data was checked and the system call
+ finishes). Also, since DAHDI should only return -ENODEV on read
+ or write when there was a surprise device removal on a running
+ system this sleep can prevent the system from becoming
+ unresponsive if the userspace application does not check for the
+ -ENODEV error and constantly tries to call read with elevated
+ privileges. (issue #17669) Reported by: tzafrir Tested by:
+ sruffell Review: https://reviewboard.asterisk.org/r/905/
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9353
+
+ * drivers/dahdi/voicebus/voicebus.c: wcte12xp, wctdm24xxp: Add call
+ to 'pci_set_mwi' on initialization. I have yet to personally come
+ across a system where this actually changes the observable
+ behavior, but it certainly seems like the sane thing to do and I
+ would rather not let this float around as a patch when I can just
+ merge it in. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=9326
+
+ * drivers/dahdi/voicebus/voicebus.c: wcte12xp, wctdm24xxp: Remove
+ redundant vb_enable_io_access. These three bits are already set
+ by 'pci_enable_device' and 'pci_set_master' calls. Signed-off-by:
+ Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9325
+
+ * drivers/dahdi/dahdi-base.c: dahdi-base: All channels for a span
+ are now unconfigured on shutdown Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9317
+
+ * drivers/dahdi/dahdi_dummy.c: dahdi_dummy: #include <linux/slab.h>
+ for kzalloc and friends. Fix the same issue as in r8550 for
+ dahdi_dummy.c (closes issue #17959) Reported by: glen201 Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9307
+
+ * drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wcte11xp.c:
+ wcte11xp, wcte12xp: Fix a long-standing issue with shutdown Upon
+ shutdown, both drivers would attempt to power down external
+ interfaces, but never attempted to bring them back up when the
+ span was restarted. Removing that code allows the driver to work
+ properly until a better solution can be found. Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9316
+
+ * README: README: Remove references to dahdi_dummy. Since
+ dahdi_dummy is no longer required remove the references from
+ README. (issue #17959) Reported by: glen201 Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9308
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Fix compilation error when
+ CONFIG_DAHDI_NET is defined. Kernel interface for network devices
+ changed. This is the patch from issue plus a few trivial
+ checkpatch.pl formatting changes (minus the >80 column warnings).
+ (closes issue #17857) Reported by: msink Patches:
+ dahdi_net-v2.patch uploaded by msink (license 1103)
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9247
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Update span-local struct
+ with timing info dahdi_tool was incorrectly reporting all spans
+ to be in local timing mode. This is because the driver tracks
+ which span it's timing syncs to, within the card local struct
+ "wc". We have to manually go through and copy timing updates to
+ the span local structs because this is what dahdi_tool actually
+ reads. dahdi-526 Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=9312
+
+2010-08-31 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux version 2.4.0 released.
+
+2010-08-27 21:59 +0000 [r9204-9205] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Moving the transmit short
+ detection behind debug module param. This needs some more testing
+ before it's on by default. If the card is otherwise functioning,
+ these messages may be confusing to the user. If the card is not
+ functioning, the driver can be reloaded with debug to check for
+ this condition. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com>
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Removed transmit line open
+ fault detection The transmit line open detection was pretty weak
+ in that it trips upon receiving 32 consecutive zeroes. We were
+ getting false positives from looping and other miscellaneous
+ functions. Removing this feature, but leaving the transmit line
+ short detector as it actually detects physical shorts. From: Russ
+ Meyerriecks <rmeyerriecks at digium.com>
+
+2010-08-24 18:44 +0000 [r9188] Russ Meyerriecks <rmeyerreicks at digium.com>
+
+ * drivers/dahdi/wcb4xxp/base.c: wcb4xxp: 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
+
+2010-08-20 01:12 +0000 [r9168] Russ Meyerriecks <rmeyerreicks at digium.com>
+
+ * drivers/dahdi/dahdi-base.c: dahdi: Uncross dest if dacs is not
+ supported between two different chans. This removes a confusing
+ message introduced in 9120 when bridging channels on two differnt
+ cards. i.e. "dahdi: unable to cross connect 'TE4/0/2/2' with
+ 'WCTDM/0/0'" "dahdi: unable to cross connect 'WCTDM/0/0' with
+ 'TE4/0/2/2'"
+
+2010-08-19 18:03 +0000 [r9167] Shaun Ruffell <sruffell at digium.com>
+
+ * include/dahdi/kernel.h, drivers/dahdi/wctdm24xxp/base.c: dahdi:
+ move 'dahdi_is_digital_span' back into wctdm24xp driver. Older
+ kernels do not like the 'bool' type and I cannot just add it into
+ include/dahdi/kernel.h without compile messages in the xpp driver
+ where bool is defined directly. Since the wctdm24xxp driver is
+ the only place using that function, I just moved it back there
+ for now. This fixes a regression introduced in 9130.
+
+2010-08-18 16:56 +0000 [r9162-9163] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * build_tools/live_dahdi: live_dahdi: shutdown dynamic spans to to
+ avoid panic If we fail to shutdown the dynamic spans, we may get
+ a panic on the next load. This attempts to guess when we need to
+ unload spans at unload.
+
+ * build_tools/live_dahdi: live_dahdi: allow testing dynamic local
+ spans Adds support for configuring dynamic spans through
+ live_dahdi. To enable, set in live/live.conf: DYNAMIC_LOC="yes"
+ It will generate an extra live/etc/dahdi/dynamic.conf (if one
+ does not exist) and use it to configure extra dynamic spans in
+ the system. Note that ATM this will make the system hang pretty
+ easily at 'load' time.
+
+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>
+
+ * 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.
[... 3009 lines stripped ...]
More information about the svn-commits
mailing list