Hi,
Paul Alfille:
> 1. OWFS design, accessing the separate slaves.
> a. does the slave address need to be set before every access.
No
> b. do I need to share the same file-descriptor for the different slaves.
No
Source: kernel: Documentation/i2c/dev-interface
> 2. Command line interface
> One thought is to use the same strategy as the USB,
> --usb=1 --usb=all, ... => --i2c=all (although this could be the default,
> except it would be different from usb)
> Unlike USB, however, the i2c slaves can be distinguished by their address.
If you want to go all out:
--i2c=/dev/i2c-0:2
for the device on i2c bus zero with address 2.
--i2c=/dev/i2c-1
for the first device on bus 1 that you can find
--i2c=any:2
a device is on address 2, but you don't know which bus number
(bus numbers can change between reboots, so this is not just
idle
fanciness)
--i2c=all
scan for, and use, all devices.
Personally, though, I see no need for any but the last option, provided
that you can reliably identify 1wire adapters -- which I have no
experience with WRT i2c.
However, I do see a need for signalling owserver that it should re-scan
the i2c buses for new / missing adapters. (This BTW also applies to USB.)
--
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [EMAIL PROTECTED]
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
- -
The chat program is in public domain. This is not the GNU public license.
If it breaks then you get to keep both pieces.
-- Copyright notice for the chat program
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
