I don't think w1 will work without -OW_MT (multiithreading). It's the
asynchronous nnature of tje w1 netlink interface. We have no place to accept
announcements of new bus masters, bus master's leaving, etc.
OWFS spends a lot of time waiting for IO from many different sources: serial
or USB ports, network interfaces, netlink, avahi/bonjour. I suppose it could
have been designed with one big 'select', but we didn't do it that way.
Instead there are threads created for each of those tasks.
Single threading works for the simpler case: Accept one request, talk to
each bus master in turn, then respond. The zero-conf and w1 interfaces break
that design without multithreading.
Paul Alfille
On Fri, Dec 4, 2009 at 2:37 AM, Wolfgang Grandegger <[email protected]>wrote:
>
> Does it make sense to test with --disable-mt? I got it compiled with
> some fixes (missing #if OW_MT) but it seems *not* to work.
>
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
