summaryrefslogtreecommitdiff
path: root/ztdummy.c
AgeCommit message (Collapse)Author
2007-12-04use a buffer for the span's device type instead of a string pointer, so each ↵kpfleming
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
2007-12-04add a new Zaptel scanning tool, primarily for use by the Asterisk GUI, ↵kpfleming
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
2007-10-26If you depend on anything that is not in /usr/include/zaptel , you must tzafrir
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
2007-09-21Sort out print messages in ztdummy:tzafrir
* Proper priority to every message. * Remove a useless global. git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3073 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2007-09-16* Document ztdummy changes. tzafrir
* It's a (ztdummy) clock source, not ztdummy type. git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3044 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2007-09-15Include support for high-resolution timers for linux >= 2.6.22 (#10314).tzafrir
Changes from the patch: * Only support kernels >= 2.6.22, as hrtimer_forward is only exported as of that version. * Adapted to my recent changes in ztdummy.c . * Use ZAPTEL_TIME_NS instead of ZAPTEL_RATE * Simplified ticks debug statement. Will only be used if debug=2 or debug=3 . git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3038 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2007-09-15Include the type of the ztdummy module in the desc (span description)tzafrir
filed. To check what type of module you built, use: strings ztdummy.ko | grep type tr '%' '\n' <ztdummy.ko | grep -a type: Or look at the span title line in /proc/zaptel . git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3035 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2007-09-15ZAPTEL_RATE is not a time period.tzafrir
git-svn-id: http://svn.digium.com/svn/zaptel/branches/1.4@3032 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2007-07-19Merged revisions 2756 via svnmerge from kpfleming
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
2006-07-05yet another header file installation location change... Zaptel headers are ↵kpfleming
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
2006-06-24install zaptel.h and tonezone.h into /usr/include, not /usr/include/linux, ↵kpfleming
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
2006-06-22Bug 6631 - Implement PLL-based technique for RTC-based ztdummy to minimize ↵tilghman
jitter (pcadach and softins) git-svn-id: http://svn.digium.com/svn/zaptel/trunk@1158 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2006-01-19Merged revisions 909 via svnmerge from russell
https://origsvn.digium.com/svn/zaptel/branches/1.2 ........ r909 | russell | 2006-01-18 23:33:13 -0500 (Wed, 18 Jan 2006) | 2 lines fix symbol conflict with the kernel's rtc_interrupt function (issue #6287) ........ git-svn-id: http://svn.digium.com/svn/zaptel/trunk@910 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2006-01-10commiting change for allowing x86_64 to use rtc mogorman
in 2.6 kernel. git-svn-id: http://svn.digium.com/svn/zaptel/trunk@883 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-11-29remove extraneous svn:executable propertieskpfleming
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@837 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-11-05don't fail the entire build process when HZ is not 1000, since the user may ↵kpfleming
not be intending to use ztdummy anyway if ztdummy is compiled with HZ != 1000, make the module load fail with an appropriate error message git-svn-id: http://svn.digium.com/svn/zaptel/trunk@808 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-10-21Error out on ztdummy if 1000hz is not used (bug #5492)markster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@796 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-08-31make spinlock definitions compatible with -RT kernel patches (and future ↵kpfleming
syntax in mainline kernel, probably) (issue #5080) git-svn-id: http://svn.digium.com/svn/zaptel/trunk@751 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-07-11enable USE_RTC by default for 2.6.13+ kernels, since they have a ↵kpfleming
configure-time selectable HZ setting that does _not_ default to 1000Hz git-svn-id: http://svn.digium.com/svn/zaptel/trunk@690 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-05-25Turn off USE_RTC by default (bug #4301)markster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@656 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-05-25ztdummy fixes (bug #4301)markster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@655 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-01-21Fix ztdummy build on 2.6 (bug #3391)markster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@568 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-01-15Correct order of includesmarkster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@560 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-01-15Fix build for 2.4 kernel (bug #3343)markster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@558 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-01-14Fix compile on older 2.6 kernels (bug #3334)markster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@555 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2005-01-13Fix for 2.6 module parm (bug #3321)markster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@546 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2004-06-26Merge 2.6 and 2.4 versions of ztdummy (no longer needs UHCI for kernel > 2.6.0)markster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@424 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2003-10-27Fix interrupt unload issuemarkster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@259 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2002-10-26Version 0.3.2 from FTPmarkster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@123 5390a7c7-147a-4af0-8ec9-7488f05a26cb
2002-07-17Version 0.3.0 from FTPmarkster
git-svn-id: http://svn.digium.com/svn/zaptel/trunk@93 5390a7c7-147a-4af0-8ec9-7488f05a26cb