Bug#431724: Situation regarding mISDN

[Faidon Liambotis]

Simon Richter wrote:
>> Note that qozap, zaphfc and vzaphfc from zaptel-modules also combat with 
>> misdn in the fight to be the default for the device IDs.
> 
> Okay, so it may be a good idea to have some sort of framework where 
> these could be integrated as well.
> 
> I think it would be a common configuration to have multiple HFC based 
> cards in one box and run the TE side with zaphfc and the NT side with 
> mISDN (that way, you get a zaptel timer for MoH and Meetme).
I don't think that this would be that common, since both zaphfc and
mISDN are capable for both of TE and NT.

This very difficult to support since when one of the drivers is loaded
it will claim all of the cards (since they have matching PCI IDs).
AFAIK the only way to do this would be to use driver (un)binding after
the card has been already.
Far from ideal, IMHO.

I think that a debconf question on one (or both) of the packages asking
the user what to use which writes blacklist entries in modprobe.d.

Regards,
Faidon