On Mon, Mar 13, 2006 at 11:05:04PM +0100, Jan Kandziora ([EMAIL PROTECTED])
wrote:
> Am Montag, 13. März 2006 21:56 schrieb Evgeniy Polyakov:
> > > > 1. w1 supports on-demans searching in the following way:
> > > > search is performed on $w1_timeout interval basis, which is provided as
> > > > mod
Am Dienstag, 14. März 2006 09:15 schrieb Evgeniy Polyakov:
> > >
> >
> > For such applications as mine, it would be better to have more control
> > over which chips are "interesting" in some situation, and should be
> > updated more often and which are not. Maybe you (or we) can put some
> > "ratin
Evgeniy,
I hope I represented w1 correctly. I am excited about being able to use it with
OWFS.
My note was more to point out the current state of w1 and OWFS, and to point out
some of the areas where the two use different approaches.
For many complex applications, the 1-wire bus utilization is v
On Tue, Mar 14, 2006 at 04:52:07PM +0100, Jan Kandziora ([EMAIL PROTECTED])
wrote:
> Am Dienstag, 14. März 2006 09:15 schrieb Evgeniy Polyakov:
> > > >
> > >
> > > For such applications as mine, it would be better to have more control
> > > over which chips are "interesting" in some situation, and
On Tue, Mar 14, 2006 at 11:04:37AM -0500, Alfille, Paul H.,M.D. ([EMAIL
PROTECTED]) wrote:
> Evgeniy,
>
> I hope I represented w1 correctly. I am excited about being able to use it
> with
> OWFS.
>
> My note was more to point out the current state of w1 and OWFS, and to point
> out
> some of t
> > Is the netlink socket interface the prefered method? I'm just starting the
> > design phase and can use netlink or sysfs.
>
> Netlink is definitely the way to go.
> Sysfs was designed for simple one-shot events, like turn on/turn off.
> As we saw - simple data reading requires a lot of racy ma
Am Dienstag, 14. März 2006 17:07 schrieb Evgeniy Polyakov:
> > That's why I came up with the idea of having an application-controlled
> > update scheme. The update frequency could be determined by the kernel
> > automatically, too - chips which are read out more often by an
> > application are upda
Clearly there are many approaches to design, including mirroring the entire OWFS
function in w1.
If I had to design the optimal w1 design to work with OWFS, it would do the
following:
1. list all recognized adapters
2. list 1-wire bus contents on demand.
3. list 1-wire bus alarm contents on deman
On Tue, Mar 14, 2006 at 05:41:14PM +0100, Christoph Scheurer ([EMAIL
PROTECTED]) wrote:
> > > Is the netlink socket interface the prefered method? I'm just starting the
> > > design phase and can use netlink or sysfs.
> >
> > Netlink is definitely the way to go.
> > Sysfs was designed for simple
