[dahdi-commits] sruffell: tag linux/2.6.1-rc1 r10580 - /linux/tags/2.6.1-rc1/
SVN commits to the DAHDI project
dahdi-commits at lists.digium.com
Wed Mar 21 17:01:51 CDT 2012
Author: sruffell
Date: Wed Mar 21 17:01:47 2012
New Revision: 10580
URL: http://svnview.digium.com/svn/dahdi?view=rev&rev=10580
Log:
Importing files for 2.6.1-rc1 release.
Added:
linux/tags/2.6.1-rc1/.version (with props)
linux/tags/2.6.1-rc1/ChangeLog (with props)
Added: linux/tags/2.6.1-rc1/.version
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.6.1-rc1/.version?view=auto&rev=10580
==============================================================================
--- linux/tags/2.6.1-rc1/.version (added)
+++ linux/tags/2.6.1-rc1/.version Wed Mar 21 17:01:47 2012
@@ -1,0 +1,1 @@
+2.6.1-rc1
Propchange: linux/tags/2.6.1-rc1/.version
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: linux/tags/2.6.1-rc1/.version
------------------------------------------------------------------------------
svn:keywords = none
Propchange: linux/tags/2.6.1-rc1/.version
------------------------------------------------------------------------------
svn:mime-type = text/plain
Added: linux/tags/2.6.1-rc1/ChangeLog
URL: http://svnview.digium.com/svn/dahdi/linux/tags/2.6.1-rc1/ChangeLog?view=auto&rev=10580
==============================================================================
--- linux/tags/2.6.1-rc1/ChangeLog (added)
+++ linux/tags/2.6.1-rc1/ChangeLog Wed Mar 21 17:01:47 2012
@@ -1,0 +1,6410 @@
+2012-03-21 Shaun Ruffell <sruffell at digium.com>
+
+ * dahdi-linux 2.6.0-rc1 tagged.
+
+2012-03-21 20:35 +0000 [r10575-10576] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: FXS: added a
+ 'lower_ringing_noise' parameter * Adds a new parameter,
+ 'lower_ringing_noise', to module xpd_fxs. * Makes the
+ "power-down" behaviour that was added in upstream svn r10478,
+ switchable in runtime. * By default (false), makes the vbat_h
+ behave like it did before the power-down change. - I.e: vbat_h is
+ held throughout the ringing period (during both
+ ring-up/ring-down) - So this patch revert part of r10478 * When
+ switched to true, activate the "power-down" behaviour. - I.e:
+ vbat_h follows the ring-up/ring-down. - This behaviour lowers the
+ noise caused by group ringing of FXS channels in the same unit,
+ but causes problems with CallerID. Signed-off-by: Oron Peled
+ <oron.peled at xorcom.com> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10574
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: FXS: atomic vbat_h power
+ handling * In do_chan_power() make vbat_h changes atomic. * As a
+ result we can ignore duplicate requests. This will allow cleaner
+ logic in the next commit. * Added proper debug messages.
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10573
+
+2012-03-21 19:36 +0000 [r10564-10572] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi-sysfs.c: remove a duplicate dev_set_name()
+ Remove duplicate definition from dahdi-sysfs.c Signed-off-by:
+ Oron Peled <oron.peled at xorcom.com> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10447
+
+ * include/dahdi/kernel.h, drivers/dahdi/dahdi_dynamic.c:
+ dahdi_dynamic: Since dynamic devices are 'parentless' we must
+ name them. This in conjunction with r10449 "A parent-less device
+ should not crash dahdi", this allows dahdi_dynamic spans to work
+ post the dahdi_devices changes in 2.6.0. The full address of the
+ device is not used since kernels prior to 2.6.31 limit the length
+ of a devicename to 20 characters. The full address of the device
+ can be pulled out of the "hardware_id" and "type" fields of the
+ span. This patch is just to get things working again.
+ dahdi_dynamic devices *may* still have issues if the
+ auto_assign_spans module parameter is 0. Internal-Issue-ID:
+ DAHLIN-280 Reported-by: Pavel Selivanov Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10563
+
+ * drivers/dahdi/dahdi_dynamic_eth.c: dahdi_dynamic_eth: Move tx
+ packet flushing to process context. The masterspan can be, and
+ often is, called with interrupts disabled but dev_queue_xmit()
+ needs to be called with interrupts enabled. This potentially
+ fixes a deadlock. Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10562
+
+ * include/dahdi/kernel.h: dahdi: Update dev_set_name / dev_name for
+ RHEL 5.6+. This is needed because dev_name() is mapped to
+ kobject_name() in a backport, but the kobject name isn't set
+ until after device_add(). The result would be parentless devices
+ would fail since dahdi would not think a name was set for these
+ devices. For these systems, we'll set both the bus_id string and
+ the underlying kobject_name. 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=10561
+
+ * drivers/dahdi/dahdi-base.c, drivers/dahdi/dahdi-sysfs.c: A
+ parent-less device should not crash dahdi * A parent-less device
+ should not crash dahdi: - Access span->parent->dev instead of
+ span->parent-dev.parent in soem cases. - Access span->parent->dev
+ via new inline span_device() - Use span_device() in all
+ dahdi_dev_{dbg,info}() * Allow low-level drivers to set their
+ device name. - Drivers that don't use this feature get the
+ default name based on the parent device name - Parent-less
+ devices which don't set their name, fails to register with
+ -EINVAL Signed-off-by: Oron Peled <oron.peled at xorcom.com>
+ Acked-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10449
+
+ * drivers/dahdi/voicebus/voicebus.h, drivers/dahdi/wcte12xp/base.c,
+ drivers/dahdi/wctdm24xxp/base.c: wcte12xp, wctdm24xxp: Add
+ compile-time option to disable ASPM for PCIe devices. Certain
+ BIOSes appear to enable ASPM even though it is not fully
+ supported by the platform. Also, since the PCIe links for TDM
+ cards are always in use it does not make sense to allow them to
+ transition to the disabled state. Just turn off power management
+ on the PCIe links completely. For more information see
+ http://lwn.net/Articles/449448/. Internal-Issue-ID: DAHLIN-283
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10557
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: Add compile-time option to
+ disable ASPM for PCIe devices. Certain BIOSes appear to enable
+ ASPM even though it is not fully supported by the platform. Also,
+ since the PCIe links for TDM cards are always in use it does not
+ make sense to allow them to transition to the disabled state.
+ Just turn off power management on the PCIe links completely. For
+ more information see http://lwn.net/Articles/449448/.
+ Internal-Issue-ID: DAHLIN-283 Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10558
+
+ * drivers/dahdi/wct4xxp/base.c: wct4xxp: __t4_frame_in and
+ __t4_framer_out slowdowns. This is a partial revert of r10234
+ "wct4xxp: __t4_framer_in and __t4_framer_out speedups." There
+ were some platform + firmware version combinations that would
+ fail to properly configure the framer with the aforementioned
+ speedups. The originally reported sympton was that interrupts
+ would fail to start and while troubleshooting I also saw cases
+ where one of the spans would stay in alarm after starting. By
+ adding in additional reads to the version register, the overall
+ process of writing / reading from the framer control registers is
+ slowed down which increases reliability. This change does *not*
+ affect the main path of TDM data which is DMAed directly into
+ buffers in host memory and are not read / written to / from
+ framer registers directly. Reported-and-Tested-by: Vahan
+ Yerkanian <vahan at arminco.com> Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10559
+
+ * drivers/dahdi/dahdi-base.c, include/dahdi/kernel.h: dahdi: Add
+ dahdi_pci_disable_link_state for kernel < 2.6.25. Will allow the
+ ASPM (Active State Power Management) state to be disabled on PCIe
+ devices before kernel version 2.6.25. Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10556
+
+2012-03-20 11:20 +0000 [r10553] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/USB_RECOV.hex,
+ drivers/dahdi/xpp/firmwares/USB_FW.hex,
+ drivers/dahdi/xpp/firmwares/FPGA_1161.201.hex: xpp: firmwares:
+ useless 0x1A at EOF Remove a mostly harmless 0x1A (^Z) at the end
+ of the file. If you add a NL after it, it breaks the firmware
+ loading. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=10550
+
+2012-03-18 19:00 +0000 [r10537-10538] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/Makefile,
+ drivers/dahdi/xpp/firmwares/FPGA_1161.201.hex (added),
+ drivers/dahdi/xpp/firmwares/USB_FW.201.hex (added): xpp:
+ firmwares to support E-Main 4 USB firmware (USB_FW.201.hex 10402)
+ and FPGA firmware (FPGA_1161.201.hex 10480) with support of the
+ new E-Main 4 Astribank mainboard. (This was accidentally labeled
+ as 'E-Main 3' in some previous commit messages) Also includes
+ Makefile fixes from r10536. Signed-off-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10535
+
+ * drivers/dahdi/xpp/firmwares/USB_FW.hex: xpp: USB_FW rev 10401:
+ minor 6FXS/2FXO caps issue Fixes an issues with the 6FXS/2FXO
+ module: if an extra FXS or FXO module is added to a system with
+ such a module, an excessive number of port licenses was
+ accidentally required (as if the 6FXS/2FXO module required
+ 8FXS/8FXO licenses). Internal-Issue-ID: #1371 Signed-off-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10534
+
+2012-03-16 16:11 +0000 [r10524-10526] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/dahdi_dummy.c: dahdi_dummy: Fix compilation since
+ dahdi-linux 2.6.0. Even though dahdi_dummy is no longer built by
+ default, the adoption of dahdi_devices in 2.6 broke the ability
+ to compile. This was not intended as there are some packagers who
+ still patch the Kbuild file to enable dahdi_dummy.
+ Internal-Issue-ID: DAHLIN-274 Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10486
+
+ * drivers/dahdi/xpp/xproto.c: xpp: '%d' -> '%lu' when displaying
+ module_refcount on kernel versions >= 3.3 Upstream commit
+ bd77c047 "module: struct module_ref should contains long fields"
+ changed the return of module_refcount from int to unsigned long.
+ This change eliminates a warning from the string format
+ specifier. Signed-off-by: Shaun Ruffell <sruffell at digium.com>
+ Acked-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10485 Conflicts:
+ drivers/dahdi/xpp/xproto.c
+
+ * drivers/dahdi/xpp/xpd.h: xpp: Use 'bool' type for boolean module
+ parameters on kernel versions >= 2.6.31. Eliminates warnings that
+ are a result of upstream commit 72db395ffa "module_param: check
+ that bool parameters really are bool." Signed-off-by: Shaun
+ Ruffell <sruffell at digium.com> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10484 Conflicts:
+ drivers/dahdi/xpp/xpd.h
+
+2012-03-15 17:36 +0000 [r10489-10490] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/card_fxs.c: xpp: FXS: better power-down to
+ lower noise * Now every linefeed control command which is not
+ RING'ing powers-down the SLIC. This reduce audible noise when
+ several channels are ringing. * Simplify code by removing
+ redundant calls to do_chan_power() before linefeed_control() *
+ Manage vbat_h state so we skip do_chan_power() calls when there
+ isn't a state change * Export vbat_h state to /proc/.../fxs_info
+ Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10478
+
+ * drivers/dahdi/xpp/card_global.c, drivers/dahdi/xpp/card_global.h:
+ xpp: reset Astribank SPI busses * A driver reload should reset
+ Astribank hardware * This patch send an SPI reset after we get
+ AB_DESCRIPTION reply from Astribank Signed-off-by: Oron Peled
+ <oron.peled at xorcom.com> Acked-by: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10474
+
+2012-03-15 15:03 +0000 [r10481] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: Shorten RINGOFF
+ debounce interval from 512ms to 128ms. In commit r10168
+ "wctdm24xxp: Use time interval for debouncing FXO ring detect"
+ [1], I inadvertently changed the debounce interval of the RINGOFF
+ event from 128ms to 512ms. The result was a potential failure to
+ detect CID, depending on line conditions, since Asterisk would
+ bump the rx gains on the channel in the middle of the CID spill
+ as opposed to before the CID spill. This fixes a regression first
+ introduced in DAHDI-Linux 2.6.0. [1]
+ http://svnview.digium.com/svn/dahdi?view=revision&revision=10168
+ Internal-Issue-ID: DAHDI-951 Reported-and-Tested-by: Jack Wilson
+ <ljwilson at digitalav.com> Signed-off-by: Shaun Ruffell
+ <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10473
+
+2012-02-07 22:19 +0000 [r10457] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/USB_RECOV.hex (added),
+ drivers/dahdi/xpp/firmwares/Makefile: USB_RECOV.hex: recovering
+ from xpp hardware issues USB_RECOV.hex, rev. 9760. It may be used
+ to recover from certain issues of the USB controller of the
+ Astribank (when an Astribank is not detected as such) by Support
+ staff. Signed-off-by: Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+ Origin: http://svnview.digium.com/svn/dahdi?view=rev&rev=10455
+
+2012-01-25 20:51 +0000 [r10445] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * drivers/dahdi/xpp/firmwares/FPGA_FXS.hex,
+ drivers/dahdi/xpp/firmwares/FPGA_1141.hex,
+ drivers/dahdi/xpp/firmwares/FPGA_1151.hex: Astribank I firmwares
+ rev. 7107 A slightly newer firmware (Xorcom rev. 7107) for older
+ (non Astribank II) Astribank modules. Was accidentally left
+ uncommited. Includes minor bug fixes. No change for any
+ relatively recent (Astribank II) Astribank. Signed-off-by:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10443
+
+2012-01-17 14:50 +0000 [r10442] Tzafrir Cohen <tzafrir.cohen at xorcom.com>
+
+ * README, drivers/dahdi/Kbuild: Build OSLEC EC if in the tree Build
+ the OSLEC echo canceller (drivers/staging/echo and
+ dahdi_echocan_oslec) if the code of oslec is present in the tree.
+ Also closing another issue regarding documentation of building
+ OSLEC, as it is now even clearer than before. Patch has been used
+ in the Debian package for quite some time. Signed-off-by: Tzafrir
+ Cohen <tzafrir.cohen at xorcom.com> (closes issue DAHLIN-110)
+ Reported by: biohumanoid (Pavel Selivanov) Patches:
+ oslec_auto.diff uploaded by tzafrir (license 5035) (closes issue
+ DAHLIN-261) Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10440
+
+2012-01-10 22:09 +0000 [r10415-10419] Shaun Ruffell <sruffell at digium.com>
+
+ * drivers/dahdi/xpp/xbus-core.c: xpp: handle failures during
+ dahdi_register_device() * If dahdi_register_device() failed, not
+ all resources were freed. When dahdi_unregister_device() was
+ called later (during driver removal) a panic was caused. * Add
+ proper error handling for possible failures in
+ xbus_register_dahdi_device(): - new xbus_free_ddev() safely free
+ an xbus->ddev - This is called from all failures points. - It is
+ also called from xbus_unregister_dahdi_device() Signed-off-by:
+ Oron Peled <oron.peled at xorcom.com> Acked-By: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10410
+
+ * drivers/dahdi/xpp/xpp_dahdi.c, drivers/dahdi/xpp/xbus-core.c:
+ xpp: Don't deactivate XPDs on unregistration * A bug was
+ introduced during migration to dahdi_device code:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10273 * Marking
+ XPDs as non-functional (card_present=0, XPD_STATE_NOHW) was moved
+ from xbus_request_removal() into xpd_dahdi_preunregister() * As a
+ result, unregistering an Astribank, made it non-functional so
+ trying to re-register it later caused errors (e.g: "Cannot open"
+ error message from xpp_open()) * This fix move XPD deactivation
+ into the proper location (during xbus_deactivate() Signed-off-by:
+ Oron Peled <oron.peled at xorcom.com> Acked-By: Tzafrir Cohen
+ <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10409
+
+ * drivers/dahdi/xpp/xpp_dahdi.c: xpp: bugfix: fix bad refcount Code
+ path called in error condition contained an superflous put_xpd()
+ call Signed-off-by: Oron Peled <oron.peled at xorcom.com> Acked-By:
+ Tzafrir Cohen <tzafrir.cohen at xorcom.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10408
+
+ * drivers/dahdi/wct4xxp/vpm450m.c: wct4xxp: VPM module creates
+ noise on alternate channels on E1 spans. The VPMOCT128 module was
+ using the VPMOCT256 timeslots assigments which would mean that
+ channels that should be marked alaw were being set in ulaw. This
+ only affected E1 spans since by default all spans are configured
+ for ulaw by default. This fixes a regression introduced in r10290
+ [1] "wct4xxp: Add support for TE820 and VPMOCT256", first
+ released in 2.6.0, that only affects E1 spans on a quad and
+ dual-span card when used with the hardware echocanceler. [1]
+ http://svnview.digium.com/svn/dahdi?view=revision&revision=10290
+ Internal-Issue-ID: DAHDI-945, DAHLIN-275 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=10414
+
+ * drivers/dahdi/wctdm24xxp/base.c: wctdm24xxp: FXS on-hook
+ transmission timer incorrect. The DAHDI_ONHOOKTRANSFER ioctl was
+ incorrectly setting the ohttimer to 0. The result was that an FXS
+ port was leaving the on-hook transfer state before finishing the
+ transmission. This was discovered while looking at why ./fxstest
+ dtmfcid was not able to pass the DTMF callerid digits to an
+ attached FXO port properly. Fixes a regression introduced in
+ r10167 "wctdm24xxp: Use interval for checking FXS on hook
+ transfer timer." [1], first released in 2.6.0. [1]
+ http://svnview.digium.com/svn/dahdi?view=revision&revision=10167
+ Signed-off-by: Shaun Ruffell <sruffell at digium.com> Origin:
+ http://svnview.digium.com/svn/dahdi?view=rev&rev=10413
+
+2012-01-04 22:19 +0000 [r10406] Shaun Ruffell <sruffell at digium.com>
+
+ * / (added): Creating branch for 2.6.
+
+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()
[... 5693 lines stripped ...]
More information about the dahdi-commits
mailing list