[Asterisk-Dev] asterisk (less hardware) ported to FreeBSD
Mark Spencer
markster at digium.com
Sat Aug 2 19:47:04 MST 2003
> apparently digium will release the specs for their hardware under NDA,
> so i'll try to encourage some BSD-like hardware/kernel people to poke at
> more substantial support of hardware.
With fully Open Source drivers already available, I'm not sure what other
information you would need on our hardware to port the drivers to *BSD,
but we'll obviously be happy to work with you.
> i dunno, the compiler is pretty picky about that stuff.
> the places i found had the variables init'd inside an if.
> it is possible that the variable was not used outside that if, but in any
> case, -Wall should be listened too, because it says good and useful things.
The codecs were greatly merged "as-is". I tried cleaning up LPC10 a long
time ago and it actually broke. I think it's held together with spider
webs and duct tape and relies on some strange side effects of some
variables being initialized by whatever the last function called happened
to place on the stack. It's nasty -- kinda like the sound quality you
get, but hey, for 2.4kbps you can't be picky.
I actually did a calculation and in theory you should be able to fit about
300 calls of LPC10 on a single T1 using IAX2...
> i managed to tweak and compile 99% of the code with -Wall -Werror.
> (this is a standard porting method i use).
Yes, I am definitely a HUGE fan of -Wall, although I"ve gotten burned by
-Werror unfortunately, so against my own personal desires, I took it out
of Asterisk's build.
> the problem here is that asterisk is a "live" system. a FreeBSD port
> (in my opinion) should only be based on release tarballs. there are already
> enough hairy ports in the FreeBSD tree.
Absolutely. I'm all for merging your portability changes into Asterisk so
long as there isn't any performance hit on Linux :)
> that should work well enough. how active are the core on picking up on
> bugs submitted that way? ie. what's a "normal" turnaround?
The bug tracker is very new. We're making an effort at Digium to try to
focus on getting bugs to come through there in order to make our efforts
more scalable. To some degree, the "squeaky wheel" gets the grease, so
it's best to follow up with your patches, preferably on Freenode IRC in
#asterisk, where you can find me (kram).
Mark
More information about the asterisk-dev
mailing list