- 19 Dec, 2021 1 commit
-
-
caela akari authored
-
- 08 May, 2019 15 commits
-
-
Shaun Ruffell authored
Ideally we want to standardize on storing all timestamps derivied from the system clock as ktime_t values. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
`struct timeval` has been removed from the kernel interface in 5.0 as part of fixing the 2038 problem. ktime_t is the preferred kernel time interface now. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
Older kernels (2.6.32) are unable to do a direct comparison of ktime values, while kernels post 4.10 have removed the comparison function. Therefore we need to make our own compatibility interface for comparing the ktime values. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
Use the new ktime_t based interface for dahdi_dummy as well. dahdi_dummy is still useful to keep around for testing purposes. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
It looked like the recent change to add support for timer_setup was not completely implemented / tested with dahdi_dummy. I was using it to check some changes to the timekeeping API when I noticed this. This does not really affect anyone since, by default, dahdi_dummy is no longer built and even if it was built, it would not use the standard timer interface by default on newer kernels. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
Since this is only used internally, and ktime is the basis for timekeeping in the kernel, this allows this interface to be validated, before converting the other internal timekeeping to it. This is part of the changes necessary to remove the use of 'struct timeval' from the driver suite for compatibility with Linux 5.0, which is updating the internal timekeeping interfaces to fix the 2038 problem. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
The timeval structure is removed in Linux kernel 5.0 since it is not year 2038 safe. Standardize on the ktime values. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
This function will return the number of milliseconds between two ktime values, but it was only introduced in kernel version 4.0 Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
The SUBDIRS environment variable is scheduled to be removed in version 5.0 of the Linux Kernel. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
All supported kernel versions use the same signature for device_create / device_destroy so we no longer need these macros. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
ENABLE_WORKQUEUE was only defined for kernels that were older than the currently supported kernels. Instead of forward porting support for workqueues in the wct4xxp driver, I think it better just to remove support for them since they are not longer used. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
All supported kernel variations support the same signature for registering a PCI module, so we can eliminate the macro. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
All supported kernels now use the same signature for the IRQ handler. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
There are not any major distributions that are still supporting kernels older than 2.6.27 so we can remove many typedefs. The primary motivator for this change is that kernel 5.0 is dropping support for timeval and it would be ideal if the in-kernel time representation can standardize on ktime_t, but 2.6.18 did not support the ktime interface that was needed. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
Shaun Ruffell authored
Since Red Hat Linux backported the new timer_setup definition in 7.6, we need to make sure to not define it ourselves when building against this kernel. Signed-off-by:
Shaun Ruffell <sruffell@sruffell.net>
-
- 27 Nov, 2018 1 commit
-
-
Keith Morgan authored
-
- 05 Oct, 2018 1 commit
-
-
Keith Morgan authored
-
- 04 Oct, 2018 3 commits
-
-
Keith Morgan authored
-
Keith Morgan authored
add them back. This reverts commit a36d2662.
-
Keith Morgan authored
-
- 03 Oct, 2018 9 commits
-
-
Keith Morgan authored
-
Keith Morgan authored
-
Keith Morgan authored
-
Keith Morgan authored
-
Keith Morgan authored
-
Keith Morgan authored
-
Keith Morgan authored
-
Keith Morgan authored
-
Keith Morgan authored
-
- 01 Oct, 2018 1 commit
-
-
Keith Morgan authored
Author: Tzafrir Cohen <tzafrir.cohen@xorcom.com> Bug: https://issues.asterisk.org/jira/browse/DAHLIN-364
-
- 03 Sep, 2018 4 commits
-
-
Shaun Ruffell authored
Upstream kernel 4.14, in commit (686fef928bba6b "timer: Prepare to change timer callback argument type") [1], introduced the timer_setup interface to replace the init_timer/setup_timer interfaces. The primary change is that the timer callback functions now follow the standard kernel pattern where the structure the callback sits in is passed to the callback instead of storing a pointer to an unassociated data type. The setup_timer functions were removed in upstream kernel v4.15, and therefore this change is needed in order to compile DAHDI for kernels >= 4.15. This change follows the same strategy that was done in the kernel to while the existing users of setup_timer were migrated to the new interface. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=686fef928bba6b
-
Shaun Ruffell authored
GCC 7.3.0 complained about the potential to overflow the fixed size span and channel names and descriptions. It also flagged potential truncations of the strings. The sprintf calls are now changed to snprintf to prevent the potential overflows, but the warning about truncations are now disabled globally.
-
Shaun Ruffell authored
Quiets the following (valid) warning from gcc 7.3.0: drivers/dahdi/voicebus/GpakApi.c:1648:22: warning: ‘MsgBuffer[1]’ may be used uninitialized in this function [-Wmaybe-uninitialized] MsgBuffer[1] |= DTMF_UPDATE_MASK;
-
Shaun Ruffell authored
This quiets the following warning from gcc 7.3.0: drivers/dahdi/xpp/card_fxs.c:1344:17: warning: increment of a boolean expression [-Wbool-operation]
-
- 09 Aug, 2018 1 commit
-
-
Shaun Ruffell authored
This fixes an error and quiets the following warning pointed out by gcc 7.3.0: warning: ‘memset’ used with length equal to number of elements without multiplication by element size [-Wmemset-elt-size] memset(chan->conflast, 0, DAHDI_MAX_CHUNKSIZE); Previously only the first half of the conference buffers were cleared out.
-
- 10 May, 2018 1 commit
-
-
Oron Peled authored
Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
- 20 Feb, 2018 1 commit
-
-
Tzafrir Cohen authored
* The variable eeprom_release_201 was added in the initialization script of the FXS module to add a case where it is different from 101 mains. * However, it tests for "201" and it should apply for any 20x. * Remove the variable from the init script of module type 6 (new FXS) as it was not used. Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
- 11 Jan, 2018 1 commit
-
-
Tzafrir Cohen authored
Debian packaging uses quilt to manage patches. Book-keeping for them is done using quilt (either directly, or in a compatible format), and tracked in the directory .pc . Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-
- 01 Jan, 2018 1 commit
-
-
Jean-Denis Girard authored
dev_attrs was removed from struct bus_type on kernel 4.13, need to convert to dev_groups, see http://lkml.iu.edu/hypermail/linux/kernel/1706.0/04578.html . DAHLIN-356 #close Signed-off-by:
Tzafrir Cohen <tzafrir.cohen@xorcom.com>
-