[asterisk-bugs] [DAHDI-linux 0017959]: dahdi_dummy fails compile on Fedora 13 64-bit with kzalloc implicit declaration error

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17959 
====================================================================== 
Reported By:                glen201
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   17959
Category:                   dahdi_dummy
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2010-09-07 08:36 CDT
Last Modified:              2010-09-08 09:19 CDT
====================================================================== 
Summary:                    dahdi_dummy fails compile on Fedora 13 64-bit with
kzalloc implicit declaration error
Description: 
Debug below is from 2.4.0 but 2.3.0.1 has the same compile time error

====================================================================== 

---------------------------------------------------------------------- 
 (0126737) sruffell (administrator) - 2010-09-08 09:19
 https://issues.asterisk.org/view.php?id=17959#c126737 
---------------------------------------------------------------------- 
gen201:  dahdi_test *only* tests timing from DAHDI, it doesn't (and
shouldn't) know anything about the timing source Asterisk has selected.  

I can't speak about the real-time performance of the non DAHDI methods of
timing, but the core timer in DAHDI no longer requires "(near) real-time
linux".  Instead of depending on a timer (or interrupt) running at a fixed
periodic rate it is scheduled to run at a fixed periodic rate, but when it
runs it calculates how much time has really passed and adjusts
accordingly.

This was first added to dahdi_dummy in revision 6524
http://svn.asterisk.org/view/dahdi?view=revision&revision=6524 moved into
the core of DAHDI as an option in 6863
http://svn.asterisk.org/view/dahdi?view=revision&revision=6863 and made the
default behavior in 8053
http://svn.asterisk.org/view/dahdi?view=revision&revision=8053 .

Given that...it's still possible for there to be audio problems due to
system conditions outside of DAHDI's/Asterisk's control.  Two of the
biggest culprits are frame buffers and IDE drives that aren't using DMA. 
I've seen 50+ ms latencies due to IDE configurations. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-08 09:19 sruffell       Note Added: 0126737                          
======================================================================