[asterisk-dev] hotplug DAHDI - dahdi.init

[Russ Meyerriecks]

On Sun, Oct 20, 2013 at 1:19 PM, Tzafrir Cohen <tzafrir.cohen at xorcom.com>wrote:

> Stop
> ====
> The "stop" action of dahdi.init does just one thing: unloads the DAHDI
> kernel modules. dahdi.init includes there a function called
> "unload_module" to unload a module after first recursively downloading
> all of its dependencies. This is something that should have been done in
> C, but is, sadly, still done in shell. It is useful on upgrades (and on
> development) to guarantee that the old modules have been unloaded. Maybe
> make this a separate script?
>
Definitely want to keep this around in some form. I use this constantly.


> That said, we should, at some point in the future, do away with the
> blacklisting of all DAHDI PCI cards modules.
>
+1


> fxotune
> -------
> fxotune could probably be adapted to run from the udev hook span_config
> after running dahdi_cfg for the span. It needs to grow a -C switch the
> same as dahdi_cfg (or use channel numbers from -b and -e). In that case
> the same comments for dahdi_cfg above would apply.
>
+1


> start_hpec
> ----------
> Is there any problem with moving it as well to span_config? Any problem
> with running it twice on a span? On the system?
>
Not sure about this one ...

-- 
Russ Meyerriecks
Digium, Inc. | Linux Kernel Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
direct: +1 256-428-6025
Check us out at: www.digium.com & www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20131021/d1405aeb/attachment.html>