- 08 Jun, 2020 1 commit
-
-
seren akari authored
-
- 15 Feb, 2016 1 commit
-
-
Wendell Thompson authored
-
- 05 Nov, 2015 1 commit
-
-
Tzafrir Cohen authored
A script that performs the module loading / unloading instead of the init script. Other functionality of the init script is performed by udev hooks. But manual initiation of modules loading or unloading is still needed on several occasions. This script should help enable the removal of the init script from the DAHDI package. Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
- 02 Nov, 2015 1 commit
-
-
Oron Peled authored
* Drop PCM during sluggish events: - Drop both rx/tx (was only tx) - Drop almost all pcm until sluggishness stops (used to drop only single pcm each time). - Renamed: "drop_next_pcm" -> "drop_pcm" (to match new semantics) - Still allow "keep alive" PCM so Astribank will not reset FXS high-voltage. The "sluggish_pcm_keepalive" parameter set the rate (1/50 by default) - Added rx/tx drop statistics counters - Removed "pcm_tx_drops" (replaced by new statistics counters) * Also improved format of /proc/xpp/XBUS-*/xpp_usb: - Show cummulative number of sluggish events. - Clearly show range (in usec) of usb_tx_delay[] Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
- 27 Oct, 2015 2 commits
-
-
Russ Meyerriecks authored
Now prints the serial number of the card to the kernel log for cards which support this feature. This include the wcb23x and wcb43x series. Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Russ Meyerriecks authored
Adds support for Digium's new dual span wcb23x series cards. Also other minor improvements for the new generation cards including the wcb23x and wcb43x Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 23 Oct, 2015 3 commits
-
-
Russ Meyerriecks authored
A few of the indirect register writes to the A_ST_* indirect registers weren't being protected by any kind of sequence lock. This could lead to potential race conditions of two spans were configured simultaneously. Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Russ Meyerriecks authored
The hw init function gets called on a module remove in order to reset the hardware before shutdown. This was causing "Initializing zarlink echocan" to print on shutdown which could be confusing. Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Russ Meyerriecks authored
This logic was reading and printing the bri chips automatic selection of sync source. We always use manual sync selection in the driver so this doesn't need to exist. Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 14 Oct, 2015 2 commits
-
-
Russ Meyerriecks authored
Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Russ Meyerriecks authored
Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 04 Jun, 2015 1 commit
-
-
Shaun Ruffell authored
When the firmware is reloaded and reset, the packet error count is not. This can create a condition where the firmware could report an error like the following if a channel was closed without any new errors: wctc4xxp 0000:07:08.0: 18446744073709551597 errored receive packets wcdte.packet_errors is also renamed to wcdte.reported_packet_errors to not conflict with the packet_errors member of the descriptor lists. Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 13 May, 2015 4 commits
-
-
Russ Meyerriecks authored
In the case where two transcoders are loaded in a system and one transcoder experiences an errored receive packet condition, the logic would ping pong the error between the two cards, causing a runaway stream of errors in the kernel log. This fix moves the global error count var into the wcdte struct to allow for per-card logic. Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com> Acked-by:
Shaun Ruffell <sruffell@digium.com>
-
Shaun Ruffell authored
The IRQF_DISABLED flag was removed in 4.1 in commit "genirq: Remove the deprecated 'IRQF_DISABLED' request_irq() flag entirely" [1]. By default all interrupt handlers are now run with interrupts disabled and therefore should all be considered "fast interrupts". Any driver that was still using the flag will now lock interrupts directly in the handler in case running on an older kernel that is not disabling interrupts when running the handler. [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d8bf368d0631d4bc2612d8bf2e4e8e74e620d0ccSigned-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Shaun Ruffell authored
These flags are direct mappings to the IRQF_[SHARED|DISABLED] flags and no longer need to be kept separate. Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Shaun Ruffell authored
It has now been years since subversion has been used with this project. We can go ahead and simplify the version script now. Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 30 Mar, 2015 3 commits
-
-
Russ Meyerriecks authored
Introduces support for new series b43x cards which make use of the zarlink echo canceller. Made as few changes to the b410 operation as possible, but the critical region had some cleanups, so it may be a bit more performant. Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
John Sloan authored
The cards affected include the TE131/3, TE235/435, A4B, and A8B. Update all PCIe cards' firmware to increase the incoming and outgoing TDM FIFOs to 16ms. The FIFOs will only be filled to a depth equal to the driver's latency setting (ie. 3ms default). The total system latency is not effected. The firmware and driver now also report the maximum DMA transaction time when in DEBUG mode to aid in determining if the system is experiencing long PCIe transactions (ie. TLP completion timeouts). Decreased the maximum latency to from 20 to 12ms Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Tzafrir Cohen authored
New USB firmware that fix mis-reporting of the number of channels (or rather: licenses) in the Astribank when a 2FXS6FXO module is used in conjunction with another module. USB_FW.hex: rev. 11452 USB_FW.201.hex: rev. 11453 Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
- 02 Mar, 2015 4 commits
-
-
Tzafrir Cohen authored
https://bugs.debian.org/776622 asks to avoid using the build time in the generated result to help make the build reproducable. This fix uses the timestamp of README for generating the timestamp in the footer of README.html. Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
Tzafrir Cohen authored
Commit d5db139ab3764640e0882a1746e7b9fdee33fd87 "module: make module_refcount() a signed integer." included in 3.19 makes this condition slightly more complex. Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
Shaun Ruffell authored
With commit (af3cd13501 "lib/string.c: remove strnicmp()") [1] dahdi can no longer call strnicmp directly. strncasecmp was added into lib/string.c in kernel version 2.6.22 so we'll map calls to strncasecmp to strnicmp for any kernel before that. This is necessary to compile against kernels >= 4.0. [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=af3cd13501Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Acked-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
Shaun Ruffell authored
With commit (d1f1052c52 "device: Change dev_<level> logging functions to return void") [1] in kernel version 4.0, DAHDI would fail to compile with the following error: .../drivers/dahdi/dahdi-base.c:7150:2: error: void value not ignored as it ought to be dahdi_dev_dbg(ASSIGN, span_device(span), ^ Now ignore the dev_printk return value. [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d1f1052c5204524Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Acked-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
- 20 Jan, 2015 2 commits
-
-
Shaun Ruffell authored
This is necessary to build against kernel version 3.19 since commit (78d28e651f97866d608d9b41 "kill f_dentry macro") [1] [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=78d28e651Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Shaun Ruffell authored
It was reported that for VLAN interfaces, failing to release this reference count will prevent a system from rebooting properly, resulting in the need to power cycle. Reported-by: Assen Totin Internal-Issue-ID: DAHLIN-343 Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 17 Nov, 2014 2 commits
-
-
Tzafrir Cohen authored
-
Tzafrir Cohen authored
Latest Astribank firmware (as of Rev. 11426 also supports some newer hardware types, which will have the ID 203. Anyone installing this newer version will now have 203 as an alias, but older versions will not have it.
-
- 05 Nov, 2014 1 commit
-
-
Tzafrir Cohen authored
New firmware that includes a better way to identify hardware modules type that does not require multiplexers. This is firmware file FPGA_1161.201.hex rev. 11426. Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
- 20 Oct, 2014 2 commits
-
-
Shaun Ruffell authored
Looks like there are some bashims in the script. Make this explicit in the script until they can be taken out. This fixes failures to run this script on Ubuntu when dash is the default shell. Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Shaun Ruffell authored
This is needed to compile against upstream Linux 3.18 since commit "locking: Remove deprecated smp_mb__() barriers" [1]. [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2e39465abc4b7856a0ea6fcf4fSigned-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 17 Sep, 2014 1 commit
-
-
Shaun Ruffell authored
Kernel version 3.16+, since upstream commit (7f7f25e82d54870d "replace checking for ->read/->aio_read presence with check in ->f_mode" )[1], does not like it when dahdi changes the set of allowed file operations on a file descriptor outside of the context of an open() system call. DAHDI changes the available file operations when a channel is opened by first opening /dev/dahdi/channel and then calling the DAHDI_SPECIFY ioctl to bind it to a particular DAHDI channel. Until DAHDI_SPECIFY is called there weren't any read()/write() callbacks implemented and therefore after the initial open, the kernel was setting not setting FMODE_CAN_{WRITE,READ} on the file descriptor indicating that those operations were not allowed. Now define empty shell functions on the general dahdi_fops so the vfs layer will not mark a file descriptor as unwritteable or unreadable on open. [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7f7f25e82d54870df24d415a7007fbd327da027b Internal-Issue-ID: DAHLIN-340 Reported-and-tested-by: Thomas B. Clark Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 15 Aug, 2014 1 commit
-
-
Michael Walton authored
The logic on ENABLE_TASKELETS compiler flag was inverted causing an oops on normal dahdi_cfg of a dynamic span. Issue-id: https://issues.asterisk.org/jira/browse/DAHLIN-328Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com> Acked-by:
Shaun Ruffell <sruffell@digium.com>
-
- 11 Aug, 2014 1 commit
- 01 Aug, 2014 1 commit
-
-
Russ Meyerriecks authored
A fresh modprobe and dahdi_cfg would cause a temporary green alarm state on the spans for a second while the alarm debounced into RED. New logic keeps the spans alarm state as NONE during the unconfigured state, but sets the alarm state to RED after the framer reset in the startup logic. Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 23 Jul, 2014 1 commit
-
-
Russ Meyerriecks authored
A fresh modprobe and dahdi_cfg would cause a temporary green alarm state on the driver for a second while the alarm debounced into RED. New logic keeps the spans alarm state as NONE during the unconfigured state, but sets the alarm state to RED after the framer reset in the startup logic. Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com> Acked-by:
Shaun Ruffell <sruffell@digium.com>
-
- 18 Jul, 2014 1 commit
-
-
Shaun Ruffell authored
The firmware/Makefile missed a line that added the firmware for the TE436 to the download list. Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 17 Jul, 2014 1 commit
-
-
Russ Meyerriecks authored
Adds driver support for Digium's new te436 and te236 quad and dual span T1/E1 cards. [removed whitespace at end of line] Signed-off-by:
Shaun Ruffell <sruffell@digium.com>
-
- 11 Jul, 2014 2 commits
-
-
Shaun Ruffell authored
If dahdi_span_ops.spanconfig is called multiple times in a row (like when running dahdi_cfg; dahdi_cfg ) the tx signaling bits would go through a spurious state that some far side devices would respond to. Now, if the dahdi_span_ops.spanconfig callback is called, and the configuration matches the existing configuration, we will not touch the framer. Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
Shaun Ruffell authored
If dahdi_span_ops.spanconfig is called multiple times in a row (like when running dahdi_cfg; dahdi_cfg ) the tx signaling bits would go through a spurious state that some far side devices would respond to. Now, if the dahdi_span_ops.spanconfig callback is called, and the configuration matches the existing configuration, we will not touch the framer. Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-
- 07 Jul, 2014 1 commit
-
-
Shaun Ruffell authored
If a channel is currently playing a tone when the tone zone is updated, the existing tone zone could be freed while the channel keeps a reference to the current tone (curtone) that points into the freed zone. If the newly freed tone is then modified, there was a window where it was possible to corrupt 'struct dahdi_chan' (by overrunning swritechunk[]) resulting in a "BUG: unable to handle kernel paging request at virtual address" panic in the context of __dahdi_transmit_chunk(). Reported-and-Tested-by:
Matt Behrens <matt@zigg.com> Signed-off-by:
Shaun Ruffell <sruffell@digium.com> Signed-off-by:
Russ Meyerriecks <rmeyerriecks@digium.com>
-