Re: [Asterisk-Dev] Zaptel development question

Steven Sokol Wed, 13 Oct 2004 07:48:35 -0700

I saw that in my code review (as well as in the card initialization) but the problem is: that takes place in the driver its self -- in kernel space. The driver certainly knows what the modules are, but I can't see an ioctl call that returns that information to the user space (where my application would live). I certainly don't want to go hacking about in the Zaptel source. I'm dangerous enough on the user side...

Does anybody else see what I am missing -- an ioctl call to the control interface (/dev/zap/ctl) that will return card-specific information? The generic ZT_GET_PARAMS doesn't seem to pass that bit of data back, and I don't see any other driver calls that would return structures with module (driver) specific data.

Anybody else have thoughts?

Thanks,

Steve


Sam Bingner wrote:

Zapata Telephony Interface Registered on major 196
Zaptel watchdog on duty!
Freshmaker version: 63
Freshmaker passed register test
Module 0: Installed -- AUTO FXO (FCC mode)
Module 1: Installed -- AUTO FXS/DPO
Module 2: Installed -- AUTO FXS/DPO
Module 3: Installed -- AUTO FXS/DPO
Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules)

Why not look at the module and see how it does it, or use that output from
syslog if it's not needed somewhere else?

*shrug* just guessing

Sam

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Steven M. Sokol
Sent: Tuesday, October 12, 2004 5:23 PM
To: [EMAIL PROTECTED]
Subject: [Asterisk-Dev] Zaptel development question

Does anybody out there have any idea how to get the module types from the
wcfxs driver?  Mark indicated that /dev/zap/ctl could be, somehow, forced to
yeild up the module types but I can't seem to find any documentation and my
perusal of the code doesn't show any direct way to get the information from
the driver.

Anybody out there see what I don't?  The driver structure includes a modtype
param that seems to get set when the driver initializes the hardware. There
has to be some way to get at this, right?

Thanks,

Steve

_______________________________________________ Asterisk-Dev mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-dev To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev

------------------------------------------------------------------------

_______________________________________________
Asterisk-Dev mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-dev

begin:vcard
fn:Steven Sokol
n:Sokol;Steven
email;internet:[EMAIL PROTECTED]
tel;work:816.822.1807
x-mozilla-html:FALSE
url:http://www.sokol-associates.com
version:2.1
end:vcard

_______________________________________________
Asterisk-Dev mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-dev
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Re: [Asterisk-Dev] Zaptel development question

Reply via email to