From e8413f9f3646c5b6708e1e5107cc5c8e41362626 Mon Sep 17 00:00:00 2001 From: Shaun Ruffell Date: Fri, 13 Aug 2010 18:36:12 +0000 Subject: dahdi: Make it clear that 'linecompat' can be used to identify analog spans. The linecompat member can be used by a span to identify the global-to-the-span signalling types supported. Analog spans do not support any span-global signalling and therefore linecompat should always be 0. Signed-off-by: Shaun Ruffell git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/trunk@9130 a0bf4364-ded3-4de4-8d8a-66a801d63aff --- include/dahdi/user.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'include/dahdi/user.h') diff --git a/include/dahdi/user.h b/include/dahdi/user.h index 4cdabc4..420b75f 100644 --- a/include/dahdi/user.h +++ b/include/dahdi/user.h @@ -571,7 +571,8 @@ struct dahdi_spaninfo { char manufacturer[40]; /* manufacturer of span's device */ char devicetype[40]; /* span's device type */ int irq; /* span's device IRQ */ - int linecompat; /* signaling modes possible on this span */ + int linecompat; /* span global signaling or 0 for + analog spans.*/ char spantype[6]; /* type of span in text form */ } __attribute__((packed)); -- cgit v1.2.3