Ok, I looked through the documentation.
You have multiple I2C slaves on a single bus. We currently cycle through the
available addresses and take the first responding one, ignoring the rest.
It looks quite doable to add support for more i2c adapters, but there are
some architectural issues.
1. OWFS design, accessing the separate slaves.
a. does the slave address need to be set before every access.
b. do I need to share the same file-descriptor for the different slaves.
2. Command line interface
a. automatic detection
b. specifying a specific address
c. more than one instance of OWFS assigned to different i2c slaves.
Basically a balance between convenience and precision.
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.
I need input on the best design.
Paul
On Tue, Aug 12, 2008 at 5:20 AM, Hans Detter <[EMAIL PROTECTED]> wrote:
> thanks for your reply.
> My I2C understanding is, that the number x of /dev/i2c-x specifies the
> adapter number only, not the addresses of the I2C devices I have. I my
> case I can only use /dev/i2c-0 since this is what I have on my HW board,
> all I2C devices are connected to it.
>
>
-------------------------------------------------------------------------
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
