I have seen cases were users run: # modprobe <driver>; dahdi_cfg -c <custom config file> and the spans end up misconfigured because dahdi_span_assignments ends up running, via udev, after the user configured the span the way it wanted. dahdi_span_assignments now looks at auto_assign_spans module parameter on dahdi.ko, like dahdi_handle_device already does, to determine if legacy or udev based configuration is being done. Signed-off-by: Shaun Ruffell <sruffell@digium.com> Acked-by: Oron Peled <oron.peled@xorcom.com>remotes/origin/2.9.y
parent
5e75fa48f4
commit
6ed0adc086
Loading…
Reference in new issue