[svn-commits] sruffell: tag linux/2.6.0 r10400 - in /linux/tags/2.6.0: .version ChangeLog

SVN commits to the Digium repositories svn-commits at lists.digium.com
Tue Jan 3 17:17:43 CST 2012


Author: sruffell
Date: Tue Jan  3 17:17:39 2012
New Revision: 10400

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

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

Added: linux/tags/2.6.0/.version
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.6.0/.version?view=auto&rev=10400
==============================================================================
--- linux/tags/2.6.0/.version (added)
+++ linux/tags/2.6.0/.version Tue Jan  3 17:17:39 2012
@@ -1,0 +1,1 @@
+2.6.0

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

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

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

Added: linux/tags/2.6.0/ChangeLog
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.6.0/ChangeLog?view=auto&rev=10400
==============================================================================
--- linux/tags/2.6.0/ChangeLog (added)
+++ linux/tags/2.6.0/ChangeLog Tue Jan  3 17:17:39 2012
@@ -1,0 +1,6075 @@
+2012-01-03 Shaun Ruffell <sruffell at digium.com>
+
+        * dahdi-linux 2.6.0 released.
+
+2012-01-03 22:44 +0000 [r10397]  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>
+
+2012-01-03 19:25 +0000 [r10395-10396]  Shaun Ruffell <sruffell at digium.com>
+
+	* 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>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Reduce time spent waiting
+	  for auth done bit on TE820. It is not necessary to wait a full
+	  second for the donebit. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com> Acked-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com>
+
+2012-01-02 14:07 +0000 [r10387-10390]  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_bri.c, drivers/dahdi/xpp/card_global.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:10 +0000 [r10383-10384]  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-14 19:27 +0000 [r10381]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/dahdi-base.c: DAHDI-linux: Fix "surprise removal"
+	  problems * Added a nodev_*() file_operations that handle system
+	  calls from user-space after surprise device removal.
+	  Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by:
+	  Tzafrir Cohen <tzafrir.cohen at xorcom.com> Acked-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+2011-12-14 19:02 +0000 [r10379-10380]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Fail startup if not
+	  generating interrupts. I've seen some platforms that do not
+	  properly route the interrupt from the card to the host CPU. In
+	  these cases the card potentially could appear to be greened up
+	  even though no data is flowing over the spans. This change allows
+	  dahdi_cfg to return an error when this occurs, and also ensures
+	  that all the spans are in RED alarm. For example, dahdi_cfg
+	  output when the card is not generating interrupts: # dahdi_cfg
+	  DAHDI startup failed: Input/output error And the kernel log will
+	  contain a string like: wct4xxp 0000:02:08.0: Interrupts not
+	  detected. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/dahdi-base.c: dahdi: Return dahdi_span_ops.startup
+	  callback errors to userspace. Allows dahdi_cfg to return an error
+	  code if a board driver fails it's startup call for any reason.
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+	  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+2011-12-12 18:18 +0000 [r10377]  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>
+
+2011-12-07 19:34 +0000 [r10372-10373]  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>
+
+2011-12-02 22:48 +0000 [r10364-10365]  Russ Meyerriecks <rmeyerreicks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Revise vpm struct due to
+	  product name changes Renamed most of the "vpm450m" references to
+	  just "vpm". Signed-off-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com> Acked-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Handle incorrect vpm
+	  module/card pairings Signed-off-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com> Acked-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+2011-12-02 19:56 +0000 [r10360-10361]  Shaun Ruffell <sruffell at digium.com>
+
+	* include/dahdi/kernel.h, drivers/dahdi/voicebus/GpakCust.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>
+
+	* 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>
+
+2011-11-29 23:38 +0000 [r10345-10347]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/card_pri.c: xpp: PRI: restore pri_protocol to
+	  R/W: Restores the pri_protocol attribute of the XPD node in SysFS
+	  to be writable. Fixes a minor regression from the pinned-spans
+	  fix, similar to r10334. * This attribute was made R/O in digium
+	  r10280 as part of the pinned-spans changes: - The E1/T1 settings
+	  were changed via new set_spantype() method which was called from
+	  dahdi when the 'spantype' dahdi attribute was written to. - This
+	  fails our init_card_4_* trying to write E1/T1 into our private
+	  attribute. * Restored our old code (with minor modifications) so
+	  we can set E1/T1 the old way (writing to our 'pri_protocol'
+	  attribute) as well as the new way (when it will be used
+	  eventually). Signed-off-by: Oron Peled <oron.peled 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>
+
+2011-11-16 12:10 +0000 [r10341]  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:04 +0000 [r10337-10339]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/firmwares/USB_FW.hex: xpp: USB_FW rev 10085:
+	  fix regression from r10013 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 r10013 An extra fix that was accidentally not
+	  included in r10013. Minor bug fixes. Signed-off-by: Tzafrir Cohen
+	  <tzafrir.cohen at xorcom.com>
+
+2011-11-10 16:56 +0000 [r10334-10335]  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>
+
+	* drivers/dahdi/xpp/xbus-sysfs.c, drivers/dahdi/xpp/xbus-core.c,
+	  drivers/dahdi/xpp/xbus-core.h: xpp: restore backward compat
+	  dahdi_registration This restores a somewhat limited functionality
+	  of the "span" write interface in the SysFS node of the span,
+	  broken by the pinned-spans code. * PROBLEM: dahdi-linux
+	  pinned-spans should work with existing dahdi-tools specifically
+	  the dahdi_registration tool. * As a result, we should still be
+	  able to control dahdi registration order. However, registration
+	  is now in complete devices and not spans * Restored
+	  dahdi_autoreg=[0/1] xpp module parameter: - It now refers to
+	  complete astribanks and not individual spans * The xpp module
+	  sysfs "span" attribute: - Implemented write method (for
+	  dahdi_registration tool) - The first write of [1/0] to this
+	  attribute, registers/unregisters the complete astribank - Further
+	  writes are ignored (with DBG messages) * Also, implemented new
+	  xbus_is_registered() function * Once the new dahdi-tools are
+	  merged, we should turn deprecation messages from DBG() to
+	  NOTICE() Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+	  Acked-by Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+2011-11-07 22:40 +0000 [r10330-10332]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Wait for background
+	  threads to complete on failed load. Some of the VPM loading /
+	  probing threads use global system workqueues. They might now be
+	  running when we abort early so we should wait for them to
+	  complete their runs before freeing memory that may be in use.
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/dahdi-base.c: dahdi: Unregister dahdi_device from
+	  sysfs if we fail to auto assign spans. Otherwise, if the
+	  _dahdi_assign_span call fails, the dahdi_device will never be
+	  removed from the dahdi_devices virtual bus and the board drivers
+	  will not be reloadable. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* drivers/dahdi/dahdi-base.c: dahdi: Fix typo in previous commit
+	  which forced some spans to always fail assignment. I misssed a
+	  small typo in r10328 "Extra debugging aids and messages" that
+	  would force any span that supports a hardware preechocan to
+	  always fail assignment with -EFAULT. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+2011-11-07 17:48 +0000 [r10323-10328]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* include/dahdi/kernel.h, drivers/dahdi/dahdi-sysfs.c,
+	  drivers/dahdi/dahdi-base.c: Extra debugging aids and messages *
+	  Added dahdi_dev_dbg() macro to print when we don't (yet) have a
+	  span number. * Added a new debug category: DAHDI_DBG_ASSIGN *
+	  Made sure error return code paths prints helpfull messages *
+	  Promote error messages from INFO to NOTICE * Change some errno
+	  values from EINVAL to EFAULT (internal errors not caused by user
+	  input) Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by
+	  Tzafrir Cohen <tzafrir.cohen at xorcom.com> Acked-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* drivers/dahdi/dahdi-base.c: bugfix: off-by-one in span assignment
+	  The test in _check_spanno_and_basechan() was off by one (used '<'
+	  instead of '<=') Signed-off-by: Tzafrir Cohen
+	  <tzafrir.cohen at xorcom.com> Acked-by: Shaun Ruffell
+	  <sruffell at digium.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 Shaun Ruffell <sruffell at digium.com>
+
+	* dahdi-linux 2.6.0-rc1 released.
+
+2011-11-02 21:46 +0000 [r10310]  Russ Meyerriecks <rmeyerreicks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: minor: Removed unnecessary
+	  instrumentation Removed a couple prints of instrumentation that
+	  was cluttering up the log output. Signed-off-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com> Acked-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+2011-11-02 19:46 +0000 [r10303-10304]  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>
+
+	* include/dahdi/kernel.h: dahdi: Define POLLRDHUP on kernels <
+	  2.6.17 Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+2011-11-02 17:05 +0000 [r10299-10302]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/card_pri.c,
+	  drivers/dahdi/xpp/card_bri.c, drivers/dahdi/xpp/xpp_dahdi.h: xpp:
+	  bugfix: clear NOTOPEN span alarm on assign The NOTOPEN span alarm
+	  flag is set at span unassignment time. * It needs to be cleared
+	  when the span is reassigned. * That is: only if the span is
+	  actually connected. Signed-off-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>
+
+	* drivers/dahdi/xpp/xpp_usb.c, drivers/dahdi/xpp/card_global.c,
+	  drivers/dahdi/xpp/xbus-core.h, drivers/dahdi/xpp/init_card_1_30:
+	  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>
+
+	* drivers/dahdi/xpp/card_fxo.h, drivers/dahdi/xpp/card_fxs.h: xpp:
+	  remove leftovers of old XPD_STATE method Signed-off-by: Tzafrir
+	  Cohen <tzafrir.cohen at xorcom.com>
+
+2011-11-01 20:35 +0000 [r10290-10296]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/voicebus/GpakCust.c: wctdm24xxp, wcte12xp: Allow
+	  VPMADT032 commands more time to complete. Since "wctdm24xxp:
+	  Probe for and configure modules in parallel." the check for the
+	  VPMADT032 module was moved closer to after when the interface was
+	  initialized. The 200ms timeout did not provide enough time for
+	  the system to settle out after initial start. The result was that
+	  sometimes after a cold boot the driver would fail to detect any
+	  VPMADT032 modules. This fixes a race condition that is not in any
+	  released branches. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* drivers/dahdi/firmware/Makefile: wctdm24xxp, wcte12xp: Update
+	  VPMOCT032 firmware to 1.12.0. - Cleaned up the OCT6114 interface
+	  . - Relaxed the timeout waiting for OCT6114 bus cycle completion
+	  to 100 mS and added a 2 mS delay time from OCT6114 reset to
+	  initialization. This change only addresses issues that were
+	  created in the lab and not in the field. Signed-off-by: Doug
+	  Bailey <dbailey at digium.com> Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Expose serial number in
+	  dahdi_device and kernel log. This will allow the serial number to
+	  be exposed in sysfs and also allow span assignment rules to use
+	  the serial number. Signed-off-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com> Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* drivers/dahdi/firmware/Makefile, drivers/dahdi/wct4xxp/base.c:
+	  wct4xxp: Add field upgradable firmware support for TE820. This
+	  commit adds field upgradeable support for the TE820 firmware.
+	  Firmware can now be silently upgraded as part of updating drivers
+	  like most of the existing DAHDI firmware. Previous versions of
+	  dual and quad span cards did not support upgrading firmware in
+	  the field. Signed-off-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com> Fixed up some checkpatch issues:
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wct4xxp/wct4xxp.h, drivers/dahdi/firmware/Makefile,
+	  drivers/dahdi/wct4xxp/vpm450m.c, drivers/dahdi/wct4xxp/Kbuild,
+	  drivers/dahdi/wct4xxp/base.c,
+	  drivers/dahdi/oct612x/include/oct6100api/oct6100_defines.h,
+	  README: wct4xxp: Add support for TE820 and VPMOCT256. TE820 is an
+	  8-span PCI-express digital interface card. VPMOCT256 is a
+	  hardware echo canceler that is able to provide echo cancelation
+	  on all 8-spans. From: Matthew Fredrickson <creslin at digium.com>
+	  Signed-off-by: Russ Meyerriecks <rmeyerriecks at digium.com>
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+2011-10-27 19:59 +0000 [r10270-10289]  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* README: README: Minor additions regarding pinned-spans
+	  Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* README: README: initial update for span assignments
+	  Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xbus-core.c:
+	  xpp: cleanup some printk()'s * Also demote them to DBG()
+	  Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+
+	* drivers/dahdi/dahdi-sysfs.c: added 'basechan' and 'channels'
+	  attributes to spans * So we can: - Generate 'pinned-spans.conf'
+	  from existing state - Run dahdi_cfg from udev (on specific span +
+	  its channels) Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+
+	* drivers/dahdi/dahdi-base.c: dahdi: Give userspace a chance to
+	  respond to surprise removal. * We try very hard to help asterisk
+	  understand that we unassign spans. * Implement disable_span(): -
+	  Set span + channels to DAHDI_ALARM_NOTOPEN - qevent
+	  DAHDI_EVENT_REMOVED * Use disable_span(): - in
+	  dahdi_unassign_span() and dahdi_unregister_device() - with long
+	  msleep() so asterisk has a chance to get the message - Out of the
+	  registration_mutex so we actually context switch. * Also return
+	  more POLLERR variants (POLLRDHUP is not portable, should be
+	  tested). * Also improve printk(), fix rate_limit increment (was
+	  missing) Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xpp_dahdi.h,
+	  drivers/dahdi/xpp/xbus-core.c: xpp: Remove dahdi_autoreg
+	  parameter: * With pinned-spans all spans are registered to dahdi
+	  with the device (and assigned later) * So this parameter cannot
+	  function anymore * Also remove the (now) empty xpd_post_init()
+	  function. Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+
+	* drivers/dahdi/xpp/xpp_dahdi.c: xpp: more informative span
+	  description: * Contains the hardware_id and the local span number
+	  Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+
+	* drivers/dahdi/xpp/xbus-core.c: xpp: make unregistration safer
+	  (idempotent) * Otherwise, a failed unit initialization (e.g: when
+	  init_card_?_?? fails) causes a panic Signed-off-by: Oron Peled
+	  <oron.peled at xorcom.com>
+
+	* drivers/dahdi/xpp/xbus-sysfs.c: xpp: adapt to 'location'
+	  attribute removal: * Reparent astribanks below their USB
+	  transport * This way their location can be derived from their
+	  hardware hierarchy. * The tradeoff is that once USB hardware is
+	  disconnected, there is no sysfs visibility of the astribank
+	  object even if it cannot be release yet due to open channels by
+	  asterisk * Thus, we'll need to migrate to "surprise removal" of
+	  dahdi devices... Signed-off-by: Oron Peled
+	  <oron.peled at xorcom.com>
+
+	* drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/card_pri.c,
+	  drivers/dahdi/xpp/xpp_dahdi.h: xpp: PRI: use DAHDI new
+	  set_spantype() method * Implement pri_set_spantype() method *
+	  Refactor code from PRI_card_dahdi_preregistration() into a new
+	  apply_pri_protocol(). - It is now called from both
+	  PRI_card_dahdi_preregistration() and set_pri_proto() - It now
+	  also sets span name + description * Remove old
+	  pri_protocol_store() method (pri_protocol is now RO) * Added
+	  pri_protocol_bystr() method (maybe promote it to DAHDI?)
+	  Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Allow linemode (T1/E1/J1)
+	  to be changed via sysfs attribute. Allowing the linemode to be
+	  configured with sysfs before the spans are assigned opens the
+	  eventualy capability for line mode to be configured with the
+	  other physical layer settings per card. Currently linemode is set
+	  with either physical jumpers or with a module parameter to the
+	  wct4xxp driver that is global for all cards. Default behavior is
+	  not changed with this commit. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Allow linemode (T1/E1)
+	  to be changed via sysfs attribute. Allowing the linemode to be
+	  configured with sysfs before the spans are assigned opens the
+	  eventualy capability for line mode to be configured with the
+	  other physical layer settings per card. Currently linemode is set
+	  with either physical jumpers or with a module parameter to the
+	  wcte12xp driver that is global for all cards. Default behavior is
+	  not changed with this commit. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* include/dahdi/kernel.h, drivers/dahdi/dahdi-sysfs.c: dahdi: Allow
+	  'spantype' to be changed before span assignement via sysfs. For
+	  some boards, the linemode (E1/T1/J1) is software selectable but
+	  needs to be configured before the spans were historically
+	  registered since the line mode determines the channel count
+	  available on the span. This change exports a "spantype" attribute
+	  from the dahdi_device that can be used to set E1/T1/J1 before the
+	  spans are assigned. When userspace writes to this attribute (in a
+	  <span offset>:<span type string> format), and if the board driver
+	  has implemented a set_spantype function in it's dahdi_span_ops,
+	  then the board driver can optionally change it's mode before
+	  registration. Also part of this change is breaking out the raw
+	  data structure initialization of the spans / channels via the
+	  dahdi_init_device_spans function since the board drivers may need
+	  to reallocate channels / spans as part of this callback. For
+	  example, changing from T1 to E1 mode will require allocating 7
+	  new channels. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wcfxo.c, drivers/dahdi/wcte12xp/base.c,
+	  drivers/dahdi/wcb4xxp/base.c, include/dahdi/kernel.h,
+	  drivers/dahdi/wct4xxp/base.c, drivers/dahdi/wcte11xp.c,
+	  drivers/dahdi/dahdi-sysfs.c, drivers/dahdi/wct1xxp.c,
+	  drivers/dahdi/wctdm.c, drivers/dahdi/wctdm24xxp/base.c,
+	  drivers/dahdi/dahdi-base.c: dahdi: Remove dahdi_span.irq and move
+	  dahdi_span.irqmisses into dahdi_device. 'irqmisses' is more a
+	  function of the device and there are better ways to get to IRQ
+	  for a device than storing it in any DAHDI structures.
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wcte12xp/base.c, include/dahdi/kernel.h,
+	  drivers/dahdi/dahdi-sysfs.c, drivers/dahdi/dahdi.h,
+	  drivers/dahdi/xpp/xbus-core.c, drivers/dahdi/dahdi-base.c: dahdi:
+	  Expose dahdi devices in sysfs. This exposes dahdi devices in
+	  sysfs and also exposes attributes that will allow user space to
+	  control the registration order in spans. This facilitates loading
+	  drivers out of order yet keeping consistent span/channel
+	  numbering, which in turn will eventually allow the blacklist for
+	  DAHDI drivers to be removed. The default behavior, controlled
+	  with the auto_register module parameter on dahdi is to number the
+	  spans / channels in order like is currently done. So this change
+	  does not introduce any new behavior by default. * Writing
+	  (anything) to this attribute returns the span to its unassigned
+	  state * Fix dahdi_chan_unreg() echocan refcount * Add safeguard
+	  against duplicate unassignment to _dahdi_unregister_span() *
+	  Remove the span from device_node list, only in
+	  dahdi_unregister_device() and not in dahdi_unregister_span() *
+	  Free allocated span->span_device in span_sysfs_remove() [is it
+	  safe?, didn't cause problem so far...] Signed-off-by: Shaun
+	  Ruffell <sruffell at digium.com> Signed-off-by: Oron Peled
+	  <oron.peled at xorcom.com> Signed-off-by: Tzafrir Cohen
+	  <tzafrir.cohen at xorcom.com> dahdi: Add "hardware_id" dahdi_device
+	  attribute. - The "hardware_id" does not change with device
+	  location (e.g: when a PCI card is moved from one slot to
+	  another). - Not all devices have this attribute. It is legal for
+	  it to be NULL (that is the default for all low-level drivers that
+	  do not set it explicitly). - When "hardware_id" is NULL, the
+	  sysfs attribute value is "\n" Signed-off-by: Oron Peled
+	  <oron.peled at xorcom.com> Acked-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* include/dahdi/kernel.h, drivers/dahdi/dahdi-sysfs.c,
+	  drivers/dahdi/dahdi-base.c: dahdi: Expose spans in sysfs. This
+	  change will facilitate creating rules that will allow spans and
+	  channels to be accessed by named device files instead of by
+	  numbers. Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/tor2.c, drivers/dahdi/wcfxo.c,
+	  drivers/dahdi/wcte12xp/base.c, include/dahdi/kernel.h,
+	  drivers/dahdi/pciradio.c, drivers/dahdi/wct4xxp/base.c,
+	  drivers/dahdi/xpp/xbus-sysfs.c,
+	  drivers/dahdi/voicebus/voicebus.c,
+	  drivers/dahdi/wctdm24xxp/base.c,
+	  drivers/dahdi/wcte12xp/wcte12xp.h,
+	  drivers/dahdi/wcb4xxp/wcb4xxp.h, drivers/dahdi/xpp/xpp_dahdi.c,
+	  drivers/dahdi/wcb4xxp/base.c, drivers/dahdi/xpp/xpp_dahdi.h,
+	  drivers/dahdi/wcte11xp.c, drivers/dahdi/wctdm24xxp/wctdm24xxp.h,
+	  drivers/dahdi/dahdi_dynamic.c, drivers/dahdi/wctdm.c,
+	  drivers/dahdi/wct1xxp.c, drivers/dahdi/xpp/xbus-core.c,
+	  drivers/dahdi/dahdi-base.c, drivers/dahdi/xpp/xbus-core.h: dahdi:
+	  Register devices instead of individual spans. Increasingly, spans
+	  are implemented by devices that support more than a single span.
+	  Introduce a 'struct dahdi_device' object which explicitly
+	  contains multiple spans. This will allow a cleaner representation
+	  of spans and devices in sysfs since order of arrival will not
+	  determine the layout of the devices. This also gives the core of
+	  dahdi a way to know the relationship between spans. This
+	  generalizes similar concepts that were previously xpp specific.
+	  The conversion of the xpp code was almost entirely done by Oron
+	  and Tzafrir. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+	  Signed-off-by: Oron Peled <oron.peled at xorcom.com> Signed-off-by:
+	  Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+	* drivers/dahdi/dahdi-base.c: dahdi: dahdi_is_analog_span() ->
+	  dahdi_is_digital_span() * dahdi-base.c had a reverse
+	  is_analog_span() static function -- fixed. Signed-off-by: Oron
+	  Peled <oron.peled at xorcom.com> Acked-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+	* drivers/dahdi/dahdi-base.c: dahdi: Add error messages in
+	  dahdi_ioctl_chanconfig. Provide more context to trouble shoot
+	  failures. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+	  Acked-by: Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/dahdi-base.c: dahdi:
+	  start handling "surprise device removal". This patch contains
+	  interim results while trying to make device removal work
+	  correctly: * XPP has protections to prevent dahdi unregistration
+	  while channels are open -- they are now removed, so we can
+	  unregister immediately. * Handle processes in poll_wait(): - Wake
+	  them during dahdi_chan_unreg() after the channel is gone
+	  (chan->channo = -1 or chan->file->private_data == NULL) - Test in
+	  every wait_event_interruptible() that the channel was not gone
+	  (chan->file->private_data) - Return correct values (POLLERR |
+	  POLLHUP) instead of some errno (would be important in the future
+	  if we modify asterisk to respond correctly to this condition. *
+	  Other issues: - If unregistered channel is being polled, than
+	  call msleep() before returning, to give other processes a chance
+	  (normally, asterisk has RT priority) - Call close_channel() from
+	  dahdi_chan_unreg() so it releases related tonezone * There is
+	  still a horrible race hidden by msleep(20) in dahdi_chan_unreg()
+	  force close channels from dahdi_chan_unreg(): * Mark them via
+	  DAHDI_FLAGBIT_OPEN * Call low-level driver close() method if
+	  available * What about other closing activities? Signed-off-by:
+	  Oron Peled <oron.peled at xorcom.com> Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+2011-10-24 22:19 +0000 [r10269]  Shaun Ruffell <sruffell at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Deprecate 't1e1override'
+	  module parameter in favor of 'default_linemode'. 't1e1override'
+	  isn't immediately apparent what it is supposed to do by the name.
+	  Instead 'default_linemode' module parameter can be set to "auto",
+	  "t1", or "e1" to make it clear. This change was introduced
+	  earlier in the wcte12xp driver. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com>
+
+2011-10-21 19:32 +0000 [r10226-10252]  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>
+
+	* 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>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Refactor t4_serial_setup()
+	  to remove t4.globalconfig. Allows the globalconfig member to be
+	  removed from the struct t4 and not carried around for the life of
+	  the card. Also holds the reglock a little longer for all the
+	  framer writes but I realize the startup of the wct4xxp based
+	  cards does not need to be optimized. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com> Acked-by: Michael Spiceland
+	  <mspiceland at digium.com> Acked-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Trivial. Use ARRAY_SIZE in
+	  free_wc() and __handle_leds(). Reduces the amount of code to read
+	  in the two functions and fixes checkpatch.pl warnings.
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+	  Michael Spiceland <mspiceland at digium.com> Acked-by: Russ
+	  Meyerriecks <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Atomically perform some
+	  read/modify/write operations There are read/modify/write
+	  operations on the framer that were not protected by any locks.
+	  While I didn't notice any code paths that would result in
+	  simultaneous accesses to these registers, this change will
+	  hopefully save someone else some time in the future verifying
+	  that the accesses are safe. A side effect is that the reglock is
+	  acquired only once for each read/modify/write cycle as opposed to
+	  twice previously. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com> Acked-by: Michael Spiceland
+	  <mspiceland at digium.com> Acked-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Fix spelling Contains a
+	  minor spelling correction. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com> Acked-by: Michael Spiceland
+	  <mspiceland at digium.com> Acked-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Change t4_span.spantype to
+	  linemode. Since 'linemode' more accurately describes what
+	  spantype is specifying. We can also use an enumeration for the
+	  linemode to make it explicit that linemode is only set to one of
+	  three possible values. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com> Acked-by: Michael Spiceland
+	  <mspiceland at digium.com> Acked-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Trivial refactoring in
+	  t4_init_one(). Use some convenience pointers to make the function
+	  easier to read as opposed to indexing into the arrays.
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+	  Michael Spiceland <mspiceland at digium.com> Acked-by: Russ
+	  Meyerriecks <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Add has_e1_span() helper.
+	  All those checks for wc->t1e1 span appear to basically be there
+	  to determine if there are *any* E1 spans exported by the card. We
+	  can make that explicit by wrapping those tests with a
+	  has_e1_span() inline function to help with readability.
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+	  Michael Spiceland <mspiceland at digium.com> Acked-by: Russ
+	  Meyerriecks <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wcte12xp/base.c: wcte12xp: Deprecate 't1e1override'
+	  module parameter in favor of 'default_linemode'. 't1e1override'
+	  isn't immediately apparent what it is supposed to do by the name.
+	  Instead 'default_linemode' module parameter can be set to "auto",
+	  "t1", or "e1" to make it clear. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com> Acked-by: Michael Spiceland
+	  <mspiceland at digium.com> Acked-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Remove redundant 'vpm'
+	  from struct t4. Since removal of the VPM400 support the 'vpm'
+	  member of struct t4 is now redundant with the 'vpm450m' member.
+	  Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+	  Michael Spiceland <mspiceland at digium.com> Acked-by: Russ
+	  Meyerriecks <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Remove vpm400 support. The
+	  VPM400 module is no longer supported by the wct4xxp driver. The
+	  VPMOCT064 and VPMOCT128 are. Signed-off-by: Russ Meyerreicks
+	  <rmeyerriecks at digium.com> Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com> Acked-by: Michael Spiceland
+	  <mspiceland at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Remove unused debugging
+	  code Signed-off-by: Shaun Ruffell <sruffell at digium.com> Acked-by:
+	  Michael Spiceland <mspiceland at digium.com> Acked-by: Russ
+	  Meyerriecks <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Turn off the fancy alarm
+	  LEDS. Saves about a 1us on average from the interrupt handler on
+	  one test system. Signed-off-by: Shaun Ruffell
+	  <sruffell at digium.com> Acked-by: Michael Spiceland
+	  <mspiceland at digium.com> Acked-by: Russ Meyerriecks
+	  <rmeyerriecks at digium.com>
+
+	* drivers/dahdi/wct4xxp/base.c: wct4xxp: Hold a pointer to the
+	  devtype directly Eliminates the need to store a copy of the flags
+	  and variety from the global devtype. Signed-off-by: Shaun Ruffell

[... 5361 lines stripped ...]



More information about the svn-commits mailing list