Age | Commit message (Collapse) | Author |
|
(merged branch /zaptel/team/tzafrir/move )
Closes issue #7117.
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3793 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
handling ZT_SPANCONFIG
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3343 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
none of the drivers for digital cards actually populate that field... this is now corrected
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3317 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
spans can have dynamically set device types instead of constant strings
also fix up some string creation and copying to be safe against buffer overflows
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3281 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
called 'ztscan'. this tool outputs an Asterisk-style
configuration file containing one context for each Zaptel span with all the details that can be learned about that span. to
enable this tool, the ZT_SPANSTAT ioctl gained a number of new elements to report information about the spans:
- linecompat (available signaling modes for digital spans)
- spantype (T1, E1 or J1 for digital spans)
- location (PCI/PCI-Express location)
- manufacturer
- devicetype
Along the way I also found that the digital span drivers always set T1-style signaling bits in 'linecompat' even for E1 spans,
and that the ZT_SPANCONFIG ioctl did not properly check these bits when configuring E1 spans. The result of this is that it was
possible to configure T1-only coding/framing (AMI/B8Zs, D4/ESF) on E1 spans (but not the reverse); this has been corrected and
any attempt to use T1-only coding/framing on E1 spans will now result in an error from ztcfg.
Also did some minor simplification of the Makefile rules that build the userspace tools.
(the basics of ztscan were written by Brandon Kruse then reworked and fleshed out by me)
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3278 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
build with the local zaptel.h . Otherwise you may mix two versions of
Zaptel .
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3190 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
https://origsvn.digium.com/svn/zaptel/branches/1.2
........
r2756 | kpfleming | 2007-07-18 21:05:03 -0500 (Wed, 18 Jul 2007) | 2 lines
update to 2.6.22 request_irq() flags
........
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@2757 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@2334 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
https://origsvn.digium.com/svn/zaptel/branches/1.2
........
r2043 | kpfleming | 2007-01-31 08:06:34 -0600 (Wed, 31 Jan 2007) | 4 lines
fix up author email addresses
use the kernel's built-in support for module aliases instead of manually doing it in modprobe.conf or equivalent
add wctdm8xxp alias for wctdm24xxp
........
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@2044 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
https://origsvn.digium.com/svn/zaptel/branches/1.2
........
r1697 | kpfleming | 2006-12-11 12:27:15 -0600 (Mon, 11 Dec 2006) | 2 lines
kernel 2.6.19 API changes compatibility
........
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@1698 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
now installed into /usr/include/zaptel, not /usr/include
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@1200 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
sinc e they are used much more by userspace apps than by kernel modules
remove any old copies of those headers
remove README.udev, since it no longer applies
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@1172 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@837 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
only, no functional difference)
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@791 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
syntax in mainline kernel, probably) (issue #5080)
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@751 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@718 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@560 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@558 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@555 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@546 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@497 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@402 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@366 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@299 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
DEC/INC usecount warnings need to be replaced
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@291 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@245 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
before). This affects other files, to changed the data structures, and provide
places to store the new values.
If only 1 to 3 of the spans were configured the cards could misbehave. The
driver now sets up interleaved bus operation for all four spans when any
span is configured. This seems to fix the problem.
SPANS_PER_CARD is now defined as 4, and used wherever appropriate. It made a
few things easier for me to follow when debugging.
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@218 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@155 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@152 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@151 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@150 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@138 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@130 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@118 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@114 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@98 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@90 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@62 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@42 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|
|
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@20 5390a7c7-147a-4af0-8ec9-7488f05a26cb
|