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 should be
> > > updated more often and which are not. Maybe you (or we) can put some
> > > "rating" on each chip, and an interface for the application program.
> > >
> > >
> > > Or did I misunderstood your wohle concept?
> >
> > Repeated search is needed for authentification cases and ibuttons.
> > It also helps to detect bad lines.
> >
> > Current design allows to setup w1_master_search per bus master device,
> > so in case of auth checks and big number of devices it would be better
> > to setup two masters for each kind of usage case.
...
> 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 updated more
> often. I can't measure the effort needed to implement this, though.
w1 still allows to turn automatic updates off and turn them on on your own
preferred interval or make them one-shot.
> Kind regards
>
> Jan Kandziora
>
> --
> "...Deep Hack Mode -- that mysterious and frightening state of
> consciousness where mortal users fear to tread.
> -- Matt Welsh
--
Evgeniy Polyakov
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
