Age | Commit message (Collapse) | Author |
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@9031 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8994 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8993 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8992 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8991 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
Hmm... how badly congested can the startup of Centos be?
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8964 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8954 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
For newer kernels there's no need to sleep at all. For Centos5 systems
there seems to be a need for a large sleep for firmware load at boot time.
So let's make it a loop.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8951 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8948 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8924 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
Allow using CONNECTOR/LABEL in addition to SPAN and NUM for pri_termtype
in genconf_parameters
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8923 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8854 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
If your window was larger than 80X25, you got a main "window" in the
center and the span one in the corner. This puts the span one in the
center as well.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8827 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
Various values in system.conf were parsed using %i. This means that a
value with a leading 0x was considered hexadecimal and a value with a
leading 0 would be considered octal ('030' == '24' == '0x1E').
This was never documented and seems a potential cause for confusion in
case a leading zero sneaks in. It is thus removed.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8777 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
flagged and
what is displayed.
Still runs with the old usage: patlooptest <dahdi device> [<timeout>]
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8746 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8741 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8670 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8638 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8630 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
rad_apply_channels() was the same as apply_channels()
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8615 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
When the DAHDI configuration file does not configure every single span in the system,
but leaves spans unconfigured, the verbose output from dahdi_cfg would show incorrect
span numbers when reporting the line configuration, as it printed the index into the
array of configured spans, instead of their actual span numbers.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8606 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8589 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
Move loading the the xpp firmwares (when called from udev) to a background
sub-process. This helps with:
* Don't block udev
* It seems that with older systems (e.g. CentOS 5) we need to wait a bit
for the device file to appear (in one of the upcoming udev events). If we
keep blocking udev, we won't have the device file.
The 'sleep' does not seem to be required for newer systems (e.g. Debian Lenny).
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8580 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8547 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8535 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
Groff considers '-' a hyphen. If we want a minus (or a dash) we need to use
'\-'.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8529 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8520 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8508 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8503 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8451 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8444 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
(issue #16493)
Reported by: nic_bellamy
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8430 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
(issue #15446)
(issue #16447)
Reported by: lpistone
Tested by: okrief
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8422 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8306 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
kpflemming suggested modifying the error messages due to the fact
that some spans may not have a physical card associated with it.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8299 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
Added handling for -1 returns by the driver. This indicates
that the specific hardware doesn't support a particular
feature.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8290 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
DAHDI-559
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8280 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8270 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
If you try building dahdi-tools vs. older dahdi-linux headers, dahdi_cfg
fails to build due to missing DAHDI_CONFIG_TERN and DAHDI_CONFIG_NTTE.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8266 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
Use a more standard link command in the xpp Makefile.
(closes issue #16597)
Reported by: pprindeville
Patches:
dahdi-tools-bugid16597#3.patch uploaded by pprindeville (license 347)
Tested by: pprindeville, tzafrir
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8263 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
modes.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8260 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
If the user set DAHDI_VIRT_TOP in the environment, consider it as a path
under which to look for ProcFS and SysFS files. This allows running the
DAHDI-perl tools on filesystem dumps generated by
build_tools/dump_sys_state .
To reduce the number of dependencies between various modules, the 'xpd'
member of a Dahdi::Span is removed. Dahdi::Xpp::xpd_of_span() can be
used if needed.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8215 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8211 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
The init script would fail on SuSE without this change, since it would look for
the redhat init script functions. DAHDI-437.
(closes issue #16761)
Reported by: oej
Patch by: jparker
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8194 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
Latest versions of udev at some distributions (e.g.: Debian Unstable/Testing)
complain about the files /etc/modprobe.d/dahdi and
/etc/modprobe.d/dahdi-blacklist . This is because some upcoming version of udev
will ignore files in modprobe.d that are not of the pattern *.conf.
(closes issue #15454)
Reported by: tzafrir
Patches:
modprobe_warn.diff uploaded by tzafrir (license 46)
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8161 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8148 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8125 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8075 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
This button's functinality (if/when it ever worked) now resides in dahdi_maint.
This resolves jsmith's dahdi-189 issue.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8070 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|
|
* Created a new tool "dahdi_maint" which is used for manipulating the different
maintenance and performance modes for drivers which support it. It supports:
Dual/Quad Span Card (TE4xx):
- Setting a local loopback (virtual loopback plug)
- Setting a network and network payload loopback
- Sending loopup, loopdown, and loopstop codes down the line
- Reporting the current status of the hardware based error counters :
- Framing Errors
- CRC4 Errors
- Code Violation Errors
- Errored Seconds
- Bipolar Violations
- Ebit Errors
- Fas Errors
Single Span Card (TE12x):
- Setting a local loopback (virtual loopback plug)
- Setting a network and network payload loopback
- Sending loopup, loopdown, and loopstop codes down the line
* Modified dahdi_tool to support the new counter substructure.
git-svn-id: http://svn.asterisk.org/svn/dahdi/tools/trunk@8069 a0bf4364-ded3-4de4-8d8a-66a801d63aff
|