[svn-commits] sruffell: tag linux/2.3.0.1 r8623 - in /linux/tags/2.3.0.1: .version ChangeLog

SVN commits to the Digium repositories svn-commits at lists.digium.com
Fri May 14 11:26:37 CDT 2010


Author: sruffell
Date: Fri May 14 11:26:34 2010
New Revision: 8623

URL: http://svnview.digium.com/svn/dahdi?view=rev&rev=8623
Log:
Importing files for 2.3.0.1 release.

Added:
    linux/tags/2.3.0.1/.version   (with props)
    linux/tags/2.3.0.1/ChangeLog   (with props)

Added: linux/tags/2.3.0.1/.version
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.3.0.1/.version?view=auto&rev=8623
==============================================================================
--- linux/tags/2.3.0.1/.version (added)
+++ linux/tags/2.3.0.1/.version Fri May 14 11:26:34 2010
@@ -1,0 +1,1 @@
+2.3.0.1

Propchange: linux/tags/2.3.0.1/.version
------------------------------------------------------------------------------
    svn:eol-style = native

Propchange: linux/tags/2.3.0.1/.version
------------------------------------------------------------------------------
    svn:keywords = none

Propchange: linux/tags/2.3.0.1/.version
------------------------------------------------------------------------------
    svn:mime-type = text/plain

Added: linux/tags/2.3.0.1/ChangeLog
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.3.0.1/ChangeLog?view=auto&rev=8623
==============================================================================
--- linux/tags/2.3.0.1/ChangeLog (added)
+++ linux/tags/2.3.0.1/ChangeLog Fri May 14 11:26:34 2010
@@ -1,0 +1,2308 @@
+2010-05-14 Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.3.0.1 released.
+
+2010-05-14 16:02 +0000 [r8621]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/voicebus/GpakCust.h, /,
+	  drivers/dahdi/voicebus/GpakApi.c,
+	  drivers/dahdi/voicebus/voicebus.c,
+	  drivers/dahdi/voicebus/GpakCust.c: Merged revisions
+	  8560,8575-8576 via svnmerge from
+	  https://origsvn.digium.com/svn/dahdi/linux/trunk ........ r8560 |
+	  sruffell | 2010-04-22 16:36:16 -0500 (Thu, 22 Apr 2010) | 11
+	  lines wcte12xp, wctdm24xxp: Ensure writes to I/O registers are
+	  flushed. In revision 8176 I changed register access from I/O
+	  space to memory mapped registers. Unfortunately, when I made that
+	  change, I didn't account for posted writes. This change makes
+	  sure all the registers are read back to ensure that they are
+	  posted through any intermediate bridges. The most readily
+	  observable symptom were cards that were taking 2000
+	  interrupts/second. The card reported that it handled an interrupt
+	  but the write to silence the card wasn't flushed through until
+	  the second time the interrupt handler run. DAHDI-602. ........
+	  r8575 | sruffell | 2010-04-26 18:29:16 -0500 (Mon, 26 Apr 2010) |
+	  4 lines wcte12xp, wctdm24xxp: Do not allow interruptible sleep on
+	  VPM lock. If the sleep is ever interrupted, 'up' will still be
+	  called in the GpakApi, essentially making the lock useless after
+	  that point. ........ r8576 | sruffell | 2010-04-26 18:29:17 -0500
+	  (Mon, 26 Apr 2010) | 9 lines wcte12xp, wctdm24xxp: Retry if the
+	  VPMADT032 reports not ready. CheckDspReset can return -1 if the
+	  DSP is not ready to process any new commands. In this case we
+	  should retry a few times to give the DSP a chance to become
+	  ready. While I'm not ready to say this definitely fixes recently
+	  reported cases when the wcte12xp driver constantly resets, it
+	  eliminated communication failures to the DSP module when under
+	  stress (via the vpm_firmware_version sysfs attribute). However, I
+	  haven't let it run long enough to say that the issue is resolved.
+	  DAHDI-603. ........
+
+2010-04-22 11:03 +0000 [r8551]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* /, drivers/dahdi/dahdi_echocan_jpah.c: missing #include: fixes
+	  building with 2.6.34-rc5 With kernel 2.6.34-rc5 an explicit
+	  '#include <slab.h>' is required for using kzalloc() and friends.
+	  Merged revisions 8550 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk
+
+2010-04-19 19:42 +0000 [r8540-8545]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/xpp_debug, /, drivers/dahdi/xpp/card_pri.c,
+	  drivers/dahdi/wcb4xxp/Makefile, drivers/dahdi/xpp/card_bri.c,
+	  drivers/dahdi/xpp/card_global.c, drivers/dahdi/dahdi-base.c:
+	  typos, mostly unkown Merged revisions 8539 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk
+
+	* Makefile, /: Remove generation of kernel-doc API docs It's not
+	  really useful, and it breaks building 'docs' without a kernel
+	  tree. Merged revisions 8538 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk
+
+	* /: initialize svnmerge
+
+2010-04-12 Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.3.0 released.
+
+2010-04-06 23:19 +0000 [r8473-8494]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/voicebus/voicebus.c: voicebus: Change WARN_ON_ONCE
+	  to BUG_ON. WARN_ON_ONCE is not defined in 2.6.9, and this
+	  condition would be catastrophic anyway if it were to occur.
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Load the VPM in startup,
+	  not spanconfig
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Check and
+	  dequeue/decipher the VPM commands atomically
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Make sure the interrupt
+	  is stopped before freeing the vpmadt032
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Eliminate a trailing
+	  whitespace.
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Do not reconfigure the
+	  VPMADT032 if shutting down. If we try to unload the driver soon
+	  after a high latency event, it is possible to get stuck for
+	  several seconds reloading the firmware. DAHDI-573.
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Do not restart the timer
+	  on alarm poll if shutting down.
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Expose the maximum
+	  latency as a module parameter
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Reprogram the VPM only
+	  when neccessary. Only program the VPM in spanconfig if it either
+	  is not setup, or if it fails a ping test. Also, if the channel
+	  config fails (but ping would otherwise work), force a reset /
+	  reconfiguration if the VPM module. DAHDI-573.
+
+	* drivers/dahdi/wcte12xp/base.c, drivers/dahdi/voicebus/GpakCust.c:
+	  wcte12xp: Try to reconfigure the VPM if we fail to configure the
+	  channels. Also, fall back to any software echocan configured for
+	  this channel for new calls while we're in the middle of a
+	  recovery.
+
+2010-04-04 16:14 +0000 [r8454-8468]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wcte12xp/base.c, drivers/dahdi/voicebus/voicebus.c,
+	  drivers/dahdi/wcte12xp/wcte12xp.h,
+	  drivers/dahdi/voicebus/GpakCust.c,
+	  drivers/dahdi/voicebus/GpakCust.h: wcte12xp: Poll the VPM and
+	  reset it if necessary. When the transmit descriptor runs out
+	  completely, there (appears to be) a chance for a random command
+	  to be sent that results in the VPMADT032 to no longer respond,
+	  typically resulting in one way audio. This change introduces a
+	  poll of the VPM. If it fails the poll, it will be bypassed
+	  temporarily while the driver resets and reprograms it. Also, the
+	  VPM is initially programmed in the spanconfig callback instead of
+	  at driver load. This moves the potential for underruns until
+	  later in the boot process. DAHDI-573.
+
+	* drivers/dahdi/voicebus/voicebus.c: wcte12xp, wctdm24xxp: If we're
+	  only one packet behind, just exit. This will make us two behind,
+	  which is fine, and eliminates a busy loop in atomic context.
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Use ARRAY_SIZE in a
+	  couple more places
+
+	* drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wctdm24xxp/base.c,
+	  drivers/dahdi/voicebus/GpakCust.h: wcte12xp, wtdm24xxp: Make sure
+	  the writes are retried. r8454 and r8460 introduced a change where
+	  writes are not retried when other module/framer commands are
+	  retried. This was an error and wasn't what was actually under
+	  test. This commit restores the behavior in wctdm24xxp and makes
+	  sure the vpm writes are retried in the wcte12xp.
+
+	* drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wctdm24xxp/base.c,
+	  drivers/dahdi/voicebus/GpakCust.h: wcte12xp, wctdm24xxp: Close a
+	  memory leak when processing VPM commands. Closes a memory leak
+	  when processing the VPM write commands introduced in r8454.
+
+	* drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wcte12xp/wcte12xp.h:
+	  wcte12xp: Use our own workqueue for the timer and maint events.
+	  When the latency is large and register reads can take 100s of
+	  milliseconds, the alarm polling function could tie up one of the
+	  global workqueue threads long enough to interfere with other
+	  system operations. Most noticeably the console. DAHDI-573
+
+	* drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wctdm24xxp/base.c,
+	  drivers/dahdi/voicebus/GpakCust.h: wcte12xp: Resend both framer
+	  and VPM commands when reads may have been lost. Latency
+	  conditions could cause the driver to misconfigure the VPM which
+	  would result in one way audio. DAHDI-572.
+
+2010-03-29 20:43 +0000 [r8443]  Russ Meyerriecks <rmeyerreicks at digium.com>
+
+	* drivers/dahdi/dahdi-base.c: dahdi-base: Fix a bug preventing
+	  clobbering maint state Now the errror injection code prevents
+	  placing the driver into a loopback state in a less forceful way.
+
+2010-03-25 16:23 +0000 [r8431]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/voicebus/voicebus.c,
+	  drivers/dahdi/wctdm24xxp/base.c,
+	  drivers/dahdi/voicebus/voicebus.h: wctdm24xxp: Add an 'hx8' mode
+	  for buffer processing. The Hx8 series cards do not need any idle
+	  buffers and idle_buffers complicate processing when using the
+	  timing_cable. This change adds another mode of operation for the
+	  voicebus layer for the Hx8 cards that operates without the idle
+	  buffers.
+
+2010-03-25 15:13 +0000 [r8421-8423]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/wcb4xxp/base.c, drivers/dahdi/wcb4xxp/wcb4xxp.h:
+	  wcb4xxp - add Swyx 4xS0 SX2 QuadBri PCI IDs (closes issue #16493)
+	  Reported by: nic_bellamy Patches:
+	  wcb4xxp_swyx_sx2_quadbri_pci_ids.patch uploaded by nic bellamy
+	  (license 299)
+
+	* drivers/dahdi/wcb4xxp/base.c: Some more wcb4xxp PCI IDs for
+	  Junghanns cards Resolve two open issues. One of them that
+	  accidentally wasn't closed. (closes issue #15446) (closes issue
+	  #16447) Reported by: lpistone Tested by: okrief
+
+2010-03-24 15:56 +0000 [r8410-8416]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Fix typo in last commit.
+	  Wouldn't compile on kernels >= 2.6.20.
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: t1xxp_maint is also
+	  called with interrupts disabled from dahdi_ioctl So just push all
+	  the maintenance mode processing off to the workqueue.
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: t1xxp_maint can be
+	  called from interrupt context. Since t1xxp_maint can be called
+	  from interrupt context with the DAHDI_MAINT_LOOPSTOP cmd, push
+	  the processing of that command to a workqueue since it may sleep
+	  in the t1_getreg call. DAHDI-560.
+
+2010-03-24 12:07 +0000 [r8405]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* README: document the header line of /proc/dahdi/NN
+
+2010-03-23 21:56 +0000 [r8399-8400]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Fix potential race on
+	  command handling. If we timeout a command, don't free it right
+	  away unless we are the one who removed it from whatever list it
+	  was on. Also, increase the timeout (2 seconds wasn't enough when
+	  the firmware for the VPMOCT was being loaded on a system with 4K
+	  stacks) and check the return value from t1_getreg in case there
+	  were timeouts. DAHDI-560.
+
+	* include/dahdi/kernel.h: dahdi: 'clamp' may already be backported.
+
+2010-03-23 13:41 +0000 Russ Meyerriecks <rmeyerriecks at digium.com>
+
+	* dahdi-linux version 2.2.1.1 released.
+
+2010-03-10 17:04 +0000 Russ Meyerriecks <rmeyerriecks at digium.com>
+
+	* dahdi-linux version 2.2.1.1-rc1 released.
+
+	* wct4xxp: Added support for for qfalc v3.1 framer.
+
+	* wct4xxp: Added ID tags for generation 5 firmware updates
+
+2010-01-11 Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.1 released.
+
+2010-01-11 13:40 +0000 [r7844]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/xbus-pcm.c, /: xpp: demote a message that
+	  generates some false alarms. Merged revisions 7843 via svnmerge
+	  from http://svn.digium.com/svn/dahdi/linux/trunk
+
+2010-01-10 11:40 +0000 [r7806-7816]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* /, drivers/dahdi/xpp/firmwares/USB_FW.hex: xpp: USB_FW rev 7578
+	  Fixes various minor twinstar-related bugs. Merged revisions 7815
+	  via svnmerge from http://svn.digium.com/svn/dahdi/linux/trunk
+
+	* drivers/dahdi/xpp/xbus-pcm.c, /: xpp: fixes for drift
+	  calculation. Should help for the case of multiple quad-PRI
+	  Astribanks on a single system. xpp rev: 7666. Merged revisions
+	  7807 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk
+
+	* drivers/dahdi/xpp/xbus-pcm.c, /, drivers/dahdi/xpp/xbus-pcm.h,
+	  drivers/dahdi/xpp/xbus-sysfs.c: xpp: Improved inter-Astribank
+	  drift calculation. Merged revisions 7625 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk
+
+2009-12-28 19:16 +0000 [r7733]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/dahdi-base.c: dahdi-base: change
+	  dahdi_kernel_fpu_end to kernel_fpu_end dahdi_kernel_fpu_end is
+	  part of the MMX changes in trunk that was not committed into the
+	  2.2 branch. This change snuck in as part of revision 6864 with
+	  the master span processing changes.
+
+2009-12-22 17:53 +0000 [r7723]  Shaun Ruffell <sruffell at digium.com>
+
+	* voicebus, wcte12xp: Only define SLAB_STORE_USER when CONFIG_SLUB
+	  is defined. On 2.6.22, there is was a bug in the SLUB allocator
+	  that required defining SLAB_STORE_USER, however this setting is
+	  only valid when CONFIG_SLUB is defined and not when using the
+	  previous slab allocator. DAHDI-424. 
+
+2009-12-11 23:22 +0000 [r7683-7684]  Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.1-rc2 released.
+
+	* dahdi-base: Do not wait for impulse when echotraining.  Waiting
+	  here for the impulse on the transmit can cause the echotraining
+	  logic to stick the channel into muted state. This is especially
+	  apparent on systems that regularly do not service the interrupts
+	  every millisecond. DAHDI-387. 
+
+	* dahdi-base: Reduce the max allocation size in dahdi_reallocbufs.
+	  Lower the maximum contiguous chunk that DAHDI asks for from
+	  DAHDI_MAX_BUFFER_SIZE*2 to DAHDI_MAX_BUFFER_SIZE.  With 4K pages,
+	  this can allow the kernel to try a little harder to find the
+	  memory it needs since the request goes from order 4 to order 3. 
+
+2009-11-23 19:20 +0000 [r7636]  Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.1-rc1 released.
+
+	* Even if we are debouncing the LOS declaration, we still expect
+	  the LED to turn red as soon as we unplug the physical cable. This
+	  impliments this on the wcte12xp just as it already does on the
+	  wct4xxp. 
+
+2009-11-22 11:43 +0000 [r7616-7620]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* xpp firmware: fix FXS indirect register reading. xpp rev: 7498
+	  Merged revisions 7614 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk
+
+2009-11-19 22:52 +0000 [r7610]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/xpp.rules, /: xpp: rules for loading USB
+	  firmware into 1163 devices as well Merged revisions 7595 via
+	  svnmerge from http://svn.digium.com/svn/dahdi/linux/trunk
+
+2009-11-12 23:45 +0000 [r7572-7584]  Shaun Ruffell <sruffell at digium.com>
+
+	* voicebus: Fix race when enabling/disabling hardware echocan. This
+	  closes a race condition where it was possible for the driver to
+	  believe it has enabled the VPMADT032 when in fact, it really has
+	  not. This fixes a regression introduced in dahdi-linux 2.2.0.
+	  (issue #15724)
+	  
+2009-11-10 15:47 +0000 [r7539-7550]  Shaun Ruffell <sruffell at digium.com>
+
+	* wcte12xp: Export features and operations for VPMADT032. Fixes a
+	  regression in dahdi-linux 2.2.0 where it was impossible for
+	  userspace to reset the state of a channel in the VPM. (issue
+	  #15724) Patches: mantis-15724-2.patch uploaded by sruffell
+	  (license 456) Tested by: alecdavis 
+	  
+	* Use the same mutex lock for channel allocation and license
+	  checking in dahdi_echocan_hpec, so that channel allocation won't
+	  happen while the license is being checked (or rechecked) 
+	  
+	* dahdi_dynamic: Release the dlock before calling accross modules.
+	  Resolves a hard lock due to a recursive spinlock grab at startup.
+	  Reported by: mapacheco (closes issue #15210) 
+	  
+	* echocan: Properly keep the reference counts for the echocan
+	  modules. (closes issue #13504) (closes issue #15327) Reported by:
+	  sruffell, tzafrir 
+	  
+	* wcb4xxp: support for other HFC-xS cards (info, not code) This
+	  commit includes skeleton for the support of other
+	  HFC-[248]S-based cards. It still does not include all the
+	  different cases for different cards. 
+	  
+	* wcb4xxp: B410P differences: Clock and NT/TE. * The B410P reads
+	  the NT/TE switches the other way around from other cards. * Its
+	  clock is also 1/2 of that of other cards, which causes wierd PCM
+	  on an unmodified driver. 
+	  
+	* wcb4xxp: Fix PCM handling for various cards. HFC-8S cards behave
+	  quite differently than HFC-4S cards here. 
+	  
+	* wcb4xxp: Fix LED handling in OpenVox cards (maybe also others)
+	  This commit adds extra functions to handle LEDs in the non-B410P
+	  cards. Only tested on OpenVox cards. OpenVox cards are known to
+	  have slightly different LEDs so this is likely to be slightly
+	  broken for others. 
+	  
+	* wctdm: Change proslic linefeed register setting Insure that
+	  proslic linefeed register is not transitioned from Active to
+	  On-Hook Transmission while the channel is off-hook. Replaced
+	  magic numbers assigned to linefeed associated variables with more
+	  descriptive constants. (issue #15352) Reported by: alecdavis
+	  Patches: wctdm_prevent_ohttimer_click.diff3.txt uploaded by
+	  dbailey (license 819) Tested by: alecdavis, dbailey, vmikhelson 
+	  
+	* wctdm24xxp, wctdm: Detect if our hookstate has been set back to
+	  the initial state. Check if our hookstate has been set back to
+	  the initial state, typically the result of a chanconfig, and if
+	  so, if we're an FXO port, forget our current battery state. This
+	  allows the driver to determine and report again what the hook
+	  state of the port is. (related to issue #14577) (closes issue
+	  #15429) 
+	  
+	* wcfxo: Reset the DAA on module initialization. The X100p and
+	  clones will sometimes work and sometimes not depending on wether
+	  the DAA powers up in running state- this seems to be related to
+	  the power supply. This problem is caused by the driver not
+	  reseting the DAA and may be the source of a great many
+	  intermittent problems with this card.  (closes issue #14232)
+	  Reported by: tallen8840 Patch by: tallen8840 Tested by:
+	  explidous, Flavio 
+	  
+	* Silence spurious warnings when trying to remove Zaptel
+	  directories during install. (closes issue #15479) Reported by:
+	  pprindeville Patches: dahdi-linux-rm.patch uploaded by
+	  pprindeville (license 347) 
+	  
+	* dahdi-base: Reduce the stack usage of dahdi_common_ioctl.  Split
+	  the DAHDI_GETGAINS and DAHDI_SETGAINS ioctls into their own
+	  functions and dynamically allocate the 'struct dahdi_gains'
+	  structure to reduce the pressure on the stack. 
+	  
+	* Fixed issue where the clear channel flags were not being set at
+	  the appropriate time causing a channel re-configure to mis-set
+	  the last channel in each span 
+	  
+	* wctdm24xxp: Race condition in handling writes to proslic LINEFEED
+	  register (64) The wctdm24xxp driver has a problem where a VMWI
+	  IOCTL call followed immediately by a ONHOOKTRANSFER IOCTL call
+	  will cause the ONHOOK transfer request to be dropped. This occurs
+	  if the write to the proslic's LINEFEED register for the VMWI ICTL
+	  call is not completed when the ONHOOK transfer request IOCTL is
+	  processed. I also cleaned out some magic numbers used in setting
+	  the linefeed register.  (closes issue #15875) Reported by:
+	  dbailey Patches: 15875-wctdm24xxp.diff uploaded by dbailey
+	  (license 819) Tested by: dbailey 
+	  
+	* wctdm: WCTDM SPI clock off state polarity and read timing Change
+	  the off state of the SPI clock to high and provide more time for
+	  data to settle out on SPI reads.  (closes issue #15261) Reported
+	  by: alecdavis Patches: wctdm_spi_clocking.diff2.txt uploaded by
+	  alecdavis (license 585) Tested by: alecdavis, dbailey 
+	  
+	* wct4xxp: Check the alarm state if we're debouncing a red alarm.
+	  This fixes a problem where if you set the alarmdebounce module
+	  parameter on gen2+ cards, you never detect when you go into red
+	  alarm.
+	  
+	* dahdi-base: dahdi_ioctl_[get|set]gains should return the res
+	  value. In function dahdi_ioctl_getgains() and
+	  dahdi_ioctl_setgains() return value assigned to res variable, but
+	  these function always return 0 which is an error. (closes issue
+	  #15916.) Patch by: ys 
+	  
+	* wctdm: Add missing break A break was missing that caused
+	  DAHDI_ONHOOKTRANSFER ioctl call to fall into DAHDI_SETPOLARITY
+	  ioctl call. (issue #14261) Reported by: alecdavis Patches:
+	  wctdm_fix_ONHOOKTRANSFER.diff.txt uploaded by alecdavis (license
+	  585) Tested by: alecdavis 
+	  
+	* dahdi-base: Do not allow jumps in system time to lock up the
+	  system w/core_timer Since dahdi coretimer uses the number of
+	  milliseconds that has actually passed to determine how many times
+	  to call dahdi_receive, it is possible that if the system time
+	  shifts after dahdi is started, that the system can appear to lock
+	  up while the core timer attempts to catch up. This change
+	  prevents soft lock ups under these conditions. This is brings the
+	  dahdi_dummy changes in r6933 into dahdi-base. (related to issue
+	  #15647) 
+	  
+	* wcte12xp, wctdm24xxp: VPMADT032 firmware update to 1.20. 
+	  
+	* wct4xxp: Debounce alarms by default for wct4xxp per AT&T 54016.
+	  Also, the various alarm conditions can be debounced separately. 
+	  
+	* voicebus: Increase the NLP converged threshold to 18. Brings in
+	  the change from r7065 that was on the
+	  team/sruffell/dahdi-linux-vpm119 branch. 
+	  
+	* wcte12xp: Adding alarm debounce to single span driver (wcte12xp).
+	  Debounce yellow alarm also. Change check alarm frequency to 100ms
+	  for better debounce granularity. Fix lines over 80 cols from last
+	  alarm debounce commit. 
+	  
+	* voicebus: Send 'idle' buffers when the transmit descriptor
+	  underruns. Previously, when the host system fails to service the
+	  interrupt in a timely fashion, the transmit descriptor ring for
+	  the voicebus card would "go empty" since the interface wouldn't
+	  have another descriptor to read in. The driver only knows that it
+	  went empty, not how far behind it actually was. Therefore, the
+	  driver could just increase the latency by a millisecond and keep
+	  going waiting for another bump.  Additionally, when the transmit
+	  descriptor actually goes empty, there are some cases where an in
+	  process SPI transaction to one of the modules is interrupted,
+	  which may result in corrupted module register writes on rare
+	  occassions. This now makes it possible for the voicebus drivers
+	  to coexist with some devices that periodically lock interrupts
+	  for longer than 25ms. Before this patch, the latency would
+	  constantly increase until either the modules received a corrupted
+	  frame. This patch preconfigures all the receive descriptors to
+	  send an "idle" packet that will be transmitted to the onboard
+	  modules when the host doesn't service the interrupt within
+	  (latency - 2)ms. There are now two kinds of underruns,
+	  softunderuns where the driver can detect that these idlebuffers
+	  have made it to the TX FIFO, and the normal hard underrun where
+	  the part signals a transmit descriptor unavailable interrupt.
+	  DAHDI-278. 
+	  
+	* voicebus: Add function to lock the latency. Now that increases in
+	  the latency produce less undefined behavior on the SPI busses,
+	  provide an interface for client drivers to inform the voicebus
+	  library to not increase the latency if underruns are detected.
+	  This can speed up loads of the driver since latency bumps do not
+	  trigger a restart of the driver initialization. DAHDI-278. 
+
+	* wctdm24xxp, wcte12xp: Lock latency when loading We no longer need
+	  to retry board initialization if the latency would have increased
+	  during the initialization. DAHDI-278 
+	  
+	* voicebus, wctdm24xxp, wcte12xp: Move a print out of the interrupt
+	  handler. This can be handled just as well in process context and
+	  printing to a serial console from the interrupt handler has the
+	  potential to cause long latencies. 
+	  
+	* voicebus: Be just a little more graceful if we cannot grab our
+	  interrupt line. 
+	  
+	* wcte12xp: use the dev_xxx macro for the debounce messages. We
+	  want to know which device is reporting the debounce when there
+	  are more than one card in the system.
+
+2009-11-05 12:06 +0000 [r7485-7493]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* backport a number of build fixes from trunk to 2.2 Merged
+	  revisions 7226,7356,7392 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk 
+	  
+	* xpp: Use proper get/set for device->driver_data 2.6.32-rc1 broke
+	  direct access to the member 'driver_data' of 'struct device'.
+	  However direct access to wasn't proper in the first place. This
+	  commit replaces direct access to dev->driver_data with
+	  dev_get_drvdata() and dev_set_drvdata(). 
+	  
+	* dahdi-base: Include linux/sched.h Commit a99bba to the mainline
+	  kernel removed sched.h from poll.h. So dahdi-base.c needs to
+	  include sched.h directly now.
+	  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a99bba
+	  
+	* headers: sched.h was also removed from interrupts.h Commit d43c36
+	  made it necessary to add sched.h to more of the board drivers.
+	  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d43c36
+
+	* xpp: Add sysfs xpd attribute 'timing_priority' Merged revisions
+	  7237 via svnmerge from http://svn.digium.com/svn/dahdi/linux/trunk
+
+	* T1 CAS support in the xpp "pri" module Merged revisions
+	  7244-7245,7266,7276,7457 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk
+
+	* xpp: make card_hooksig an optional card method. Done in
+	  preperation for T1 CAS support, as the PRI module will use RBS
+	  instead.
+
+	* xpp: refactor pcm mask handling.
+	  
+	* xpp: PRI PIC firmware: T1-CAS fixes 
+
+	* xpp: More E1/T1 CAS fixes. Mostly connect/disconnect xpp revs:
+	  mostly 7458, 7466
+
+2009-08-19 16:44 +0000 [r7039]  Kevin P. Fleming <kpfleming at digium.com>
+
+	* Ensure that dahdi_scan correctly reports VPM presence. The
+	  wct4xxp driver (for the dual/quad span T1/E1 cards) and the
+	  wcte12xp driver (for the single span VoiceBus-based T1/E1 cards)
+	  did not properly update the 'devicetype' field reported by
+	  dahdi_scan when a VPM was found during the card startup process.
+	  As a result, dahdi_scan did not show that a VPM was present on
+	  the card, even if it was.
+
+2009-08-13 22:04 +0000 [r7001]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* xpp firmware: Fixes PCM issue with FXO that is not a timing
+	  source Fixes PCM issue with an Astribank2 (116x) FXO module that
+	  is installed alongside a PRI/BRI module. xpp: FPGA_1161.hex r7276
+	  .  Merged revisions 6938,6966 via svnmerge from
+	  http://svn.digium.com/svn/dahdi/linux/trunk
+
+2009-08-06 17:35 +0000 [r6950]  Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-base: Reduce the stack usage of ioctl_load_zone.
+
+	* dahdi-base: Update formatting in ioctl_load_zone. Fixes
+	  checkpatch.pl formatting errors from the previous commit.
+
+2009-08-04 16:38 +0000 [r6934-6937]  Shaun Ruffell <sruffell at digium.com>
+
+	* wctc4xxp: Update to use struct net_device_ops. Accomodates a
+	  change in the linux kernel network device interface.
+	  
+	* wctc4xxp: Make the wctc4xxp_netdev_ops structure static.
+
+	* dahdi_dummy: Do not allow jumps in system time to lock up the
+	  system. Since dahdi_dummy uses the number of milliseconds that
+	  has actually passed to determine how many times to call
+	  dahdi_receive, it is possible that if the system time shifts
+	  after dahdi is started, that the system can appear to lock up
+	  while dahdi_dummy attempts to catch up. This change prevents soft
+	  lock ups under these conditions. (closes issue #15647) Reported
+	  by: missnebun
+
+2009-07-21 18:11 +0000 [r6864]  Shaun Ruffell <sruffell at digium.com>
+
+	* wcte12xp: Disable vpmadt032 companding by default. This fixes a
+	  regression in 2.2.0 where certain configurations will fail
+	  patloop test or have repeated HDLC aborts because the VPMADT032
+	  is modifying the clear channel or d channel data streams. This
+	  restores the behavior to how it was in dahdi-linux 2.1.0.4.
+	  (closes issue #15498) Reported by: alecdavis Tested by: alecdavis
+
+	* tor2: allow using port4 as timing source Fix a silly regression
+	  introduced when strict check on the timing parameter was added
+	  (sync-1 is the array index, not sync itself. And 0 is a special
+	  case). (closes issue #15408) Reported by: dferrer Patches:
+	  tor2-4th_sync.patch uploaded by dferrer (license 525)
+	  
+	* Revert "wct4xxp, wcte11xp: Use the default configuration by
+	  default at startup." This reverts the change introduced by
+	  revision 6712. This change can cause problems when there is a VPM
+	  module installed on the quad-span digital cards. 
+
+	* dahdi-base: Add support for core timing. This essentially moves
+	  the function of dahdi_dummy into the core of DAHDI. It ensures
+	  that if DAHDI is loaded, it will always be able to provide
+	  timing, regardless of whether there are board drivers loaded, or
+	  if the board drivers are properly calling dahdi_receive. If there
+	  is a master span loaded which is calling dahdi_receive, then the
+	  behavior will be like it is normally.  This functionality is off
+	  by default, uncomment CONFIG_DAHDI_CORE_TIMER in
+	  include/dahdi/config_dahdi.h in order to enable it.
+
+2009-07-21 18:11 +0000 [r6858-6864]  Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.0.2 released.
+
+	* wcte12xp: Disable vpmadt032 companding by default. This
+	  fixes a regression in 2.2.0 where certain configurations will
+	  fail patloop test or have repeated HDLC aborts because the
+	  VPMADT032 is modifying the clear channel or d channel data
+	  streams. This restores the behavior to how it was in dahdi-linux
+	  2.1.0.4. (closes issue #15498) Reported by: alecdavis Tested by:
+	  alecdavis
+
+	* tor2: allow using port4 as timing source Fix a silly regression
+	  introduced when strict check on the timing parameter was added
+	  (sync-1 is the array index, not sync itself. And 0 is a special
+	  case). (closes issue #15408) Reported by: dferrer Patches:
+	  tor2-4th_sync.patch uploaded by dferrer (license 525)
+	  
+	* Revert "wct4xxp, wcte11xp: Use the default configuration by default
+	  at startup." This reverts the change introduced by revision 6712.
+	  This change can cause problems when there is a VPM module installed
+	  on the quad-span digital cards.
+	  
+	* dahdi-base: Add support for core timing. This essentially moves the
+	  function of dahdi_dummy into the core of DAHDI. It ensures that if
+	  DAHDI is loaded, it will always be able to provide timing,
+	  regardless of whether there are board drivers loaded, or if the
+	  board drivers are properly calling dahdi_receive. If there is a
+	  master span loaded which is calling dahdi_receive, then the behavior
+	  will be like it is normally. This functionality is off by default,
+	  uncomment CONFIG_DAHDI_CORE_TIMER in include/dahdi/config_dahdi.h in
+	  order to enable it.
+
+2009-06-30 Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.0.1 released.
+	
+	* Fix for kernel panic when echotraining is enabled on echocan that
+	  does not support it.
+
+	* Fix for kernel panic on RHEL4 when using VPMADT032.
+
+	* Fix to allow wct4xxp, wcb4xxp, and wcte11xp to provide early timing.
+
+2009-06-23 15:44 +0000 [r6695]  Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.0 released.
+
+	* README: Adding a known issues section to the README
+	  files.
+
+2009-06-18 18:03 +0000 [r6692]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wcfxo.c, drivers/dahdi/wctdm.c,
+	  drivers/dahdi/wctdm24xxp/base.c: Fix calls to dahdi_hooksig. When
+	  JAPAN, AUDIO_RINGCHECK, or ZERO_BATT_RING compile time options are
+	  selected it is possible to get a kernel panic due to an invalid
+	  pointer passed to the dahdi_hooksig function. (closes issue #15350)
+	  Patch by: alecdavis
+
+2009-06-12 22:30 +0000 [r6688]  Jason Parker <jparker at digium.com>
+
+	* drivers/dahdi/Kbuild: Make complex conditionals work with GNU
+	  make 3.80. Much uglier, but it works on RHEL4.
+
+2009-06-04 21:14 +0000 [r6675]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/dahdi-base.c: Fix bug in procfs
+	  handling. Fix bug in procfs handling where it was possible to get
+	  a warning in lib/vsprintf.c when reading from /proc/dahdi/x.
+	  Patch by: biohumanoid (closes issue #15252)
+
+2009-05-27 Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.0-rc5 released.
+
+2009-05-27 12:48 +0000 [r6659]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/card_pri.c, drivers/dahdi/xpp/card_bri.c,
+	  drivers/dahdi/xpp/card_fxo.c, drivers/dahdi/xpp/card_fxs.c,
+	  drivers/dahdi/xpp/card_global.c: Fix more 'owner' for 2.6.30
+	  to be happy. Finishing the work of r6642. Completely shut issue
+	  #14964.
+
+2009-05-25 08:23 +0000 [r6651-6653]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/firmwares/PIC_TYPE_3.hex,
+	  drivers/dahdi/xpp/firmwares/PIC_TYPE_4.hex,
+	  drivers/dahdi/xpp/firmwares/FPGA_1161.hex,
+	  drivers/dahdi/xpp/firmwares/PIC_TYPE_1.hex,
+	  drivers/dahdi/xpp/firmwares/PIC_TYPE_2.hex: xpp firmwares: fixes
+	  sync issues of FXO module in a BRI/PRI Astribank * Also fixes LED
+	  blinking issues in PRI modules * Various bugfixes in the PICs.
+
+	* drivers/dahdi/xpp/firmwares/USB_FW.hex: USB_FW.hex: Allow setting
+	  caps. even when FPGA is loaded. Note that They will only take
+	  effect after a reset. Firmware rev. 7071.
+
+2009-05-19 16:09 +0000 [r6635-6642]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xpp_usb.c,
+	  drivers/dahdi/xpp/xbus-core.c, drivers/dahdi/xpp/xdefs.h: xpp:
+	  'owner' property of procfs was dropped in 2.6.30. This adds a
+	  compatibility macro for older versions that is a noop for kernels
+	  >= 2.6.30. (closes issue #14964)
+
+	* drivers/dahdi/xpp/xproto.h, drivers/dahdi/xpp/xbus-sysfs.c,
+	  drivers/dahdi/xpp/xbus-core.c, drivers/dahdi/xpp/card_global.c,
+	  drivers/dahdi/xpp/xproto.c, drivers/dahdi/xpp/xbus-core.h,
+	  drivers/dahdi/xpp/xbus-pcm.c: xpp: fix the Astribank state
+	  machine This generally is a case that would not happen in the
+	  wild, though.
+
+	* drivers/dahdi/xpp/card_bri.c, drivers/dahdi/xpp/xdefs.h: xpp:
+	  report in sysfs if bri module uses hardhdlc support
+
+	* drivers/dahdi/xpp/calibrate_slics (removed): xpp: remove obsolete
+	  script calibrate_slics
+
+	* drivers/dahdi/xpp/card_pri.c, drivers/dahdi/xpp/mmapbus.c,
+	  drivers/dahdi/xpp/card_bri.c, drivers/dahdi/xpp/card_fxo.c,
+	  drivers/dahdi/xpp/mmapdrv.c, drivers/dahdi/xpp/xbus-sysfs.c,
+	  drivers/dahdi/xpp/Kbuild, drivers/dahdi/xpp/card_fxs.c,
+	  drivers/dahdi/xpp/xdefs.h: Replaece member bus_id with dev_name()
+	  and set_dev_name() As of 2.6.26 the macros dev_name() and
+	  set_dev_name() are used to read and set (respectively) the bus_id
+	  member in sysfs. As of 2.6.30 bus_id is gone. This patch provides
+	  comaptiobility macros for older kernel versions and removes
+	  direct usage of bus_id. (closes issue #14965) Patches:
+	  xpp_2630_dev_name.diff uploaded by tzafrir (license 46)
+
+	* drivers/dahdi/voicebus, drivers/dahdi/vpmadt032_loader: ignore
+	  generated files in voicebus and vpmadt032_loader
+
+2009-05-15 23:37 +0000 [r6625-6628]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/voicebus/GpakCust.c: voicebus: Use '&' not '|' when
+	  checking for a bit.
+
+	* drivers/dahdi/voicebus/GpakCust.c: voicebus: Make the
+	  enable/disable echocan messages debug again. I accidentally
+	  changed to print everytime. They should only be printed if
+	  DEBUG_ECHOCAN is specified in the debug module parameter.
+
+2009-05-14 14:49 +0000 [r6621]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Set the syncsrc in the
+	  span appropriately. Before this commit, dahdi_tool would report
+	  "Internally clocked" for boards supported by the wcte12xp driver
+	  both when receiving timing from the span and providing it to the
+	  span. Now it reports "Internally clocked" if providing timeing to
+	  the span, and the card if receiving timeing from the span.
+	  DAHDI-65.
+
+2009-05-12 22:30 +0000 [r6606-6610]  Kevin P. Fleming <kpfleming at digium.com>
+
+	* drivers/dahdi/Kbuild: use proper case for variable name :-)
+
+	* drivers/dahdi/Kbuild: Allow VPMADT032 and HPEC binary modules to
+	  be used on platforms where ARCH is set to the new 'generic' x86
+	  flavor available in recent Linux kernel releases
+
+	* drivers/dahdi/Kbuild: emit warning messages when DAHDI is being
+	  built on a CPU architecture that does not support HPEC or the
+	  VPMADT032 firmware loader, so the user will know why they are not
+	  included clean up the conditional logic for these items in the
+	  Kbuild file
+
+	* Makefile: remove another unused variable
+
+2009-05-11 17:48 +0000 [r6589-6590]  Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.0-rc4 released.
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Expose vpm parameters as
+	  module parameters. Expose the vpmnlptype, vpmnlpthresh, and
+	  vpmnlpmaxsupp as module parameters like for the wctdm24xxp.
+	  DAHDI-261
+
+	* drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wctdm24xxp/base.c,
+	  drivers/dahdi/voicebus/GpakApi.h,
+	  drivers/dahdi/voicebus/GpakCust.c,
+	  drivers/dahdi/voicebus/GpakCust.h: voicebus: Update the default
+	  vpmadt032 parameters. Move the echo can channel parameters into a
+	  common location for both the wcte12xp and wctdm24xxp drivers that
+	  use the voicebus module. This is intended to make it clearer
+	  which differences are required between the clients. Additionally,
+	  update the default parameters to the new recommended values.
+	  VPMADT032-37
+
+2009-05-07 19:42 +0000 [r6572]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wcte12xp/base.c, drivers/dahdi/wctdm24xxp/base.c,
+	  drivers/dahdi/voicebus/GpakCust.c,
+	  drivers/dahdi/voicebus/GpakCust.h: voicebus: Create workqueue for
+	  each vpmadt032 instance. Depending on the system latency, the
+	  deferred work for the vpmadt032 can take up to 200ms. This change
+	  allows each vpmadt032 to use its own workqueue, and not the
+	  global system workqueue. This prevents vpm operations from
+	  blocking the main system workqueue for extended periods. This
+	  restores the behavior to the way it was before the common
+	  vpmadt032 code was moved out of the wctdm24xxp and wcte12xp
+	  drivers. DAHDI-260 voicebus-squash: Adding the wq name.
+
+2009-05-07 19:42 +0000 [r6568-6572]  Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux version 2.2.0-rc3 released.

[... 1504 lines stripped ...]



More information about the svn-commits mailing list