[asterisk-dev] Sysfs udev /dev/dahdi/span-names/ population
Kevin P. Fleming
kpfleming at digium.com
Sat Jul 24 00:10:23 CDT 2010
On 07/24/2010 02:19 AM, Eric "ManxPower" Wieling wrote:
> What would happen when you move the card to a different slot?
>
> On 07/23/2010 05:01 PM, Russ Meyerriecks wrote:
>> Tzafrir,
>> What do you think about removing the "location" and using just
>> "span_id" as a global unique span identifier? This can be filled in by
>> the lower level drivers on a case-by-case basis. For an example, the
>> quad span driver would probably fill it in as
>> "<pci_bus_id>:<span_number>". Then the udev script could simply populate
>> a single level directory tree under /dev/dahdi/span-names/<span_id>
>>
>> eg:
>> /dev/dahdi/span-names/PCI_Bus_03_Slot02:1
It will change, but that is due to the fact those boards don't have any
sort of unique identifiers that can be relied upon. For the boards that
have ID switches, at least those could be used so that the span
identifier doesn't change if the board is moved to a different slot or
the bus enumeration order changes.
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming at digium.com
Check us out at www.digium.com & www.asterisk.org
More information about the asterisk-dev
mailing list