> output of zttest:
> Opened pseudo zap interface, measuring accuracy...
> 99.938965% 99.951172% 99.938965% 99.963379% 99.963379% 99.951172%
> 99.951172%
Ah. Don't be scared. This is actually -correct- when using RTC. Let me
demonstrate:
[EMAIL PROTECTED] zaptel]# ./zttest -v
Opened pseudo zap in
> I'm still having my (apparantly) timing problem, but I'll do some more
> testing and make a separate thread for that. I'm generating an
> outbound call through Asterisk. The inbound audio is good, but the
> outbound audio is sometimes staticy. This seems to happen only at the
> start of the ca
Hi Tony,
> You do need RTC support in the Kernel, because it is the hooks in the
> rtc.c driver that the new ztdummy requires.
That's what I thought. That was going to be my next step but I hate
messing with the kernel remotely. I just made it as a module like you
did and it worked. Thanks.
I'
> Also, I do not have RTC support in the kernel since the headers are
> included from ztdummy, I thought that Tony said that it is not
> required. Do I need RTC support compiled into the kernel?
I was going to reply to your first message, but then I thought I'd see
if you'd figured it out yoursel
In article <[EMAIL PROTECTED]>,
Kevin Bockman <[EMAIL PROTECTED]> wrote:
> > make -C /lib/modules/2.6.11.11/build SUBDIRS=/usr/src/zaptel modules
> > make[1]: Entering directory `/usr/src/linux-2.6.11.11'
> > Building modules, stage 2.
> > MODPOST
> > *** Warning: "rtc_unregister" [/usr/src/zap
> make -C /lib/modules/2.6.11.11/build SUBDIRS=/usr/src/zaptel modules
> make[1]: Entering directory `/usr/src/linux-2.6.11.11'
> Building modules, stage 2.
> MODPOST
> *** Warning: "rtc_unregister" [/usr/src/zaptel/ztdummy.ko] undefined!
> *** Warning: "rtc_control" [/usr/src/zaptel/ztdummy.ko
