[Pkg-voip-commits] r1911 - in zaptel/trunk: . debian vzaphfc

[Kilian Krause]

Tzafrir,

> >    zaptel/trunk/vzaphfc/vzaphfc.h
> >    zaptel/trunk/vzaphfc/vzaphfc_main.c
> 
> The bristuff modules are currently "manually" added by me to the zaptel
> bristuff patch. Do you recon we should import them into our tree as
> well?

the bristuff patch comes as patch whereas the vzaphfc comes as tarball.
Therefore I found it easier to commit it as part of the SVN dirstructure
than to make it artificially become a dpatch.

> Or should we stick with a patch that only changes debian/ ?

I'd rather stick with it while it comes as a patch from upstream. Let's
just hope the vzaphfc fixes the problems that I had already tried to
solve with zaphfc-florz and which at some point remained there. Once
I'll have a new setup up and running stable, I think we can dump
zaphfc-florz and concentrate on vzaphfc and visdn for consumer cards.


[snip - 2.4 builds and 2.6.8]

Well, the decision was to support what debian-kernel is targetting at.
That's 2.6.16 at the least. Thus there should be no problem dropping the
legacy support. Unfortunately right now the makefiles seem to be
incomplete at some point as zaptel-modules won't build. That's still to
be verified and I'm hoping on waldi to give a helping hand here. I know
the version with the double makefile infrastructure eases things for a
larger set of possible kernels, yet the cost is surely much more code to
maintain. If you see a real demand for custom kernels that are not
covered by what's now in SVN, feel free to switch over to whatever you
see fit and drop me a note once you think I should give the
zaptel-modules another go.


> Speaking of other drivers: interested in the driver for a modified tor2
> card as sold in http://pbxhardware.com/ ? In this case I'll need actual
> users, as I kind of lost touch with the author. I can add the patch in
> just the same.

If there's a demand for it, why not. If there's no need, we shouldn't
bloat the package without having a proper testbed.

-- 
Best regards,
 Kilian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20060617/ff10294e/attachment.pgp