List Info

Thread: reference to real device from sysfs




reference to real device from sysfs
country flaguser name
Israel
2007-09-22 01:38:55
Hi

I'm working on adding proper device-model support to Zaptel
. Zaptel
currently uses sysfs classes, which are generally considered
obsolete.
It also uses them in a way that does not allow adding
porperties to
devices. And first and formost, there is no representation
of spans, 
where much of the more interesting information lies.

I started working on a branch in
h
ttp://svn.digium.com/svn/zaptel/team/tzafrir/sysfs .

One thing I'm currently stuck with is how to provide
information about
what span the device is connected through
("physical" device in my
terminology, as the word "device is already overly used
there).

There could be two possible ways:
1. Each span provides standard properties regarding the
physical device
2. The span provides a kobject which is a reference to the
device. And
instead of a set of properties, we use a symlink.

However, what happens when that information becomes invalid
or when the
driver needs to disconnect the physical connection and hence
release the
kobject? 

Does it mean that Zaptel needs a separate notification for
"physical
device released"? Or: "Physical device
changed"?

Or does this hint that the information about the physical
device better
be left out of Zaptel?

See also http://bugs.
digium.com/view.php?id=10353

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrirjabber.org
+972-50-7952406           mailto:tzafrir.cohenxorcom.com       
http://www.xorcom.com 
iax:guestlocal.xorcom.com/tzafrir

_______________________________________________

Sign up now for AstriCon 2007!  September 25-28th.  http://www.astricon.net/


--Bandwidth and Colocation Provided by http://www.api-digital.c
om--

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

[1]

about | contact  Other archives ( Real Estate discussion Medical topics )