diff options
author | kpfleming <kpfleming@5390a7c7-147a-4af0-8ec9-7488f05a26cb> | 2007-12-04 13:55:19 +0000 |
---|---|---|
committer | kpfleming <kpfleming@5390a7c7-147a-4af0-8ec9-7488f05a26cb> | 2007-12-04 13:55:19 +0000 |
commit | 62315ace88956c4456598eaf6b6d278d13c86a17 (patch) | |
tree | eea5aa85c604d11f62cc6ae376ff88f3edb7efb9 /Makefile | |
parent | fd130696615d48e186afb5def7e4b3a3b796bd7d (diff) |
add a new Zaptel scanning tool, primarily for use by the Asterisk GUI, 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
Diffstat (limited to 'Makefile')
-rw-r--r-- | Makefile | 34 |
1 files changed, 18 insertions, 16 deletions
@@ -235,7 +235,8 @@ MOD_DIR:=$(DESTDIR)/lib/modules/$(KVERS)/misc # Utilities we build with a standard build procedure: UTILS = zttool zttest ztmonitor ztspeed sethdlc-new ztcfg \ - ztcfg-dude usbfxstest fxstest fxotune ztdiag torisatool + ztcfg-dude usbfxstest fxstest fxotune ztdiag torisatool \ + ztscan # Makefile mentions them. Source is not included (anynore?) @@ -247,7 +248,7 @@ UTILS += patgen pattest patlooptest hdlcstress hdlctest hdlcgen \ UTILSO = $(UTILS:%=%.o) -BINS:=fxotune fxstest sethdlc-new ztcfg ztdiag ztmonitor ztspeed zttest zttool +BINS:=fxotune fxstest sethdlc-new ztcfg ztdiag ztmonitor ztspeed zttest zttool ztscan BINS:=$(filter-out $(MENUSELECT_UTILS),$(BINS)) MAN_PAGES:=$(wildcard $(BINS:%=doc/%.8)) @@ -320,17 +321,19 @@ gendigits: gendigits.c prereq: config.status tones.h tor2fw.h radfw.h version.h -zttool.o: zttool.c zaptel.h -zttool.o: CFLAGS+=$(NEWT_INCLUDE) +zttool: zaptel.h +zttool: CFLAGS+=$(NEWT_INCLUDE) +zttool: LDLIBS+=$(NEWT_LIB) + +ztscan: zaptel.h -ztprovision.o: ztprovision.c zaptel.h +ztprovision: zaptel.h -ztmonitor.o: ztmonitor.c zaptel.h +ztmonitor: zaptel.h ztspeed: CFLAGS= -ztspeed.o: CFLAGS= -zttool: LDLIBS+=$(NEWT_LIB) -sethdlc-new.o: CFLAGS+=-I$(KINCLUDES) + +sethdlc-new: CFLAGS+=-I$(KINCLUDES) $(LTZ_A): $(LTZ_A_OBJS) ar rcs $@ $^ @@ -339,20 +342,19 @@ $(LTZ_A): $(LTZ_A_OBJS) $(LTZ_SO): $(LTZ_SO_OBJS) $(CC) $(CFLAGS) -shared -Wl,-soname,$(LTZ_SO).$(LTZ_SO_MAJOR_VER).$(LTZ_SO_MINOR_VER) -o $@ $^ $(LDFLAGS) $(LDLIBS) -lm -ztcfg.c: ztcfg.h +ztcfg.o: ztcfg.h zaptel.h +ztcfg: ztcfg.o $(LTZ_A) +ztcfg: LDLIBS+=-lm ztcfg-shared: ztcfg.o $(LTZ_SO) $(CC) $(CFLAGS) -o $@ $^ $(LDFLAGS) $(LDLIBS) -lm -data: - $(MAKE) -C datamods datamods - -ztcfg: ztcfg.o $(LTZ_A) -ztcfg: LDLIBS+=-lm - ztcfg-dude: ztcfg-dude.o mknotch.o complex.o $(LTZ_SO) ztcfg-dude: LDLIBS+=-lm -lstdc++ +data: + $(MAKE) -C datamods datamods + # FIXME: we assume CC can build the C++ modules: complex.o mknotch.o: %.o: %.cc $(CC) $(CFLAGS) -o $@ -c $< |