Paul Alfille wrote: > The w1 kernel module is used by owfs like a physical bus master. The match > is not exact, so the workarounds are interesting. > > 1. w1 grabs all the bus masters it supports. They get no particular order, > and if disconnected, the bus master is re-announced with a new location. > > 2. Communication is via the netlink interface. Only root can read messages, > and all 1-wire data and communication (synchronous and asynchronous are sent > on the same channel. > > 3. The intent of w1 was system monitoring, so temperature is the main focus. > Certain chips are individually supported, we got generic codes added for raw > access. > > 4. Linklocator and DS2409 microhubs are not supported. > > 5. There is some intrinsic polling of the sensors that can interfere. > > ------ > > We added dynamically allocated bus masters, a main netlink interface thread > and then distribution via unix pipes to the correct thread. The polling, > timeouts and coordination is a little tricky and so that's why more testing > is needed.
Hm, yes. I seem to have a similar problem. See my other mail. Wolfgang. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
