[asterisk-bugs] [DAHDI-linux 0015877]: [patch] FreeBSD port

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15877 
====================================================================== 
Reported By:                Max Khon
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   15877
Category:                   dahdi (the module)
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     acknowledged
====================================================================== 
Date Submitted:             2009-09-10 16:53 CDT
Last Modified:              2009-09-16 01:48 CDT
====================================================================== 
Summary:                    [patch] FreeBSD port
Description: 
zaptel-bsd was maintained in a separate SVN repository and syncing with
main zaptel tree always was a pain.

I would like to submit dahdi FreeBSD port back to Digium for inclusion
into main SVN tree, if possible.
====================================================================== 

---------------------------------------------------------------------- 
 (0110762) Max Khon (reporter) - 2009-09-16 01:48
 https://issues.asterisk.org/view.php?id=15877#c110762 
---------------------------------------------------------------------- 
tzafrir: can you let me know why the consensus is to have separate
dahdi-freebsd branch?

1) If you are worried about a number of #ifdefs:

- the number of #ifdefs in echo cancellation and hw drivers can be
minimized to just one #ifdef (which headers to include). init/probe/attach
code can be moved to the appropriate *-linux.c and *-freebsd.c parts. This
is purely mechanical job, because currently there are two #ifdefs in these
drivers: one for headers and one for init/probe/attach.

- the number of #ifdefs in main DAHDI driver can be minimized further. I
can add more compat schemes (OS abstraction) so that the number of #ifdefs
will be minimized to one or two.

2) If you are worried that FreeBSD driver can slow down Linux driver
development:

We can always consider FreeBSD driver as a Tier-2 driver. This means that
it can be broken from time to time when active development is in progress.
Moreover, FreeBSD users will most likely not use the driver directly from
Digium distribution, but via FreeBSD port, which can be a staging area for
FreeBSD patches (patches will be added to FreeBSD port first, then pushed
down to Digium SVN)

3) If you are worried that FreeBSD driver will require resources to
maintain:

I am willing to contribute and maintain FreeBSD port. There are also other
developers out there (those that were active in FreeBSD zaptel-bsd and
dahdi-bsd projects).

My opinion still is that single source tree is better because 99% of code
is not OS-specific. There is a successful example: NVIDIA maintains
FreeBSD/Linux drivers in a single source tree (with OS abstraction layer). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-16 01:48 Max Khon       Note Added: 0110762                          
======================================================================