All the programs either link in the libow code or query owserver, so they
should all be able to use the bus.x entries, unless the particular
implementation adds a layer that filters out this function.
I don't know about owphp specifically.
Paul
On Tue, Sep 2, 2008 at 12:14 PM, Stuart Poulton <
Thanks Paul,
What a great explanation. Clearly I need to get more than one adaptor
onto the system to really test things out.
I can see some use in being able to find which bus a device is on,
however for the application I'm looking at I can do this in software.
More investigations to do.
Bus Topology
There's a picture at
http://owfs.org/index.php?page=divide-and-conquerorthat may help.
Basically, OWFS has a list (internally) of it's bus connections. They could
be a serial DS9097U, USB DS9490R, i2c DS2481-100 or a network connection to
owserver.
By default, all these bus connecti
Thanks Paul,
Any more details on how this works please ?
Cheers
Stuart
On Mon, 2008-09-01 at 22:27 -0400, Paul Alfille wrote:
> Yes, the "bus.0" entries can be used to explore the topology.
>
> On Mon, Sep 1, 2008 at 3:07 PM, Stuart Poulton
> <[EMAIL PROTECTED]> wrote:
> Hi.
>
