|
From: Paul A. <pau...@gm...> - 2008-08-11 17:50:16
|
I'm no i2c expert, but can you try /dev/i2c-1 /dev/i2c-2 ... ?
owfs merely performs: open("/dev/i2c-0",O_RDWR) so the real answer is
whatever device name is linked to the correct major/minor device.
Perhaps dmesg or /proc can offer more information.
Paul Alfille
On Mon, Aug 11, 2008 at 11:56 AM, Hans Detter <han...@gm...> wrote:
> Hello,
>
> Thanks for the replies!
> However I can not see the first reply from Paul anymore, but hopefully
> it is still present in my memory.
>
> Some background to my problem:
>
> I was given an arm CPU based prototype HW used for a multi channel data
> acquisition purpose. The HW design has a single I2C bus connected to a
> bunch of I2C devices (GPIO multiplexer, EEPROM and the 5 DS2482-800).
> The reason for the quantity of 5 DS2482-800 is, that we need to know
> where a Dallas ID is connected to (The sensor connector in our case), so
> we need dedicated one-wire lines.
> All of our I2C devices run on different I2C addresses, so there is no
> address conflict on the one and only I2C bus I have.
> Now I tried to find a convenient way to talk to my DS2482-800. I came
> across the owfs project and tried the owhttpd first.
> Using the -d /dev/i2c-0 parameter I found out, that just one of my
> DS2482-800 was detected and used. I also read, that I can append further
> -d parameter to owhttpd, but I do not know how to specify the I2C
> addresses of my 5 DS2482-800 I have on my HW.
>
> Is my approach doable with owfs?
>
> Thanks again for your effort.
>
> Hans
>
|