dahdi_dynamic: Since dynamic devices are 'parentless' we must name them.
This in conjunction with r10449 "A parent-less device should not crash dahdi", this allows dahdi_dynamic spans to work post the dahdi_devices changes in 2.6.0. The full address of the device is not used since kernels prior to 2.6.31 limit the length of a devicename to 20 characters. The full address of the device can be pulled out of the "hardware_id" and "type" fields of the span. This patch is just to get things working again. dahdi_dynamic devices *may* still have issues if the auto_assign_spans module parameter is 0. Internal-Issue-ID: DAHLIN-280 Reported-by: Pavel Selivanov Signed-off-by: Shaun Ruffell <sruffell@digium.com> git-svn-id: http://svn.asterisk.org/svn/dahdi/linux/trunk@10563 a0bf4364-ded3-4de4-8d8a-66a801d63aff
This commit is contained in:
@@ -1096,6 +1096,9 @@ struct dahdi_dynamic_driver {
|
||||
|
||||
struct list_head list;
|
||||
struct module *owner;
|
||||
|
||||
/*! Numberic id of next device created by this driver. */
|
||||
unsigned int id;
|
||||
};
|
||||
|
||||
/*! \brief Receive a dynamic span message */
|
||||
|
||||
Reference in New Issue
Block a user