On Sun, 24 Dec 2017 10:26:49 +0100, R.Wieser wrote:

> Andrew,
>
>> You might try writev(2)
>
> Thank you.  Its a good starting point to do some googeling and testing.
>
>> A target port is something related to your I2C device and not I2C
>> itself,
>
> Just regard it as a second address byte - which is actually a thing -
> indicating one outof 65536 devices.  Hmmm ... Is there a possibility to
> set a two-byte device adddress ?
>
>> and you didn't say what that was, so no one is going to be able to
>> answer.
>
> My question was aimed at I2C (or rather, the API talking to it), not
> a(ny) specific slave device using it.  That I mentioned the target port
> was just ment as an example, something to relate to.
>
> In my case the device I'm working with does not use a "target port",
> just a single bit in the first "databyte" to indicate a read or write
> action - which is rather indistinguishable from a "target port" though.
> :-)
>
> Though if you need to think of one you can pick any which accepts a(ny)
> number of databytes preceeded by a single target port byte.  Any I2C
> EPROM,
> I2C to RS232 or SPI convertor, I2C display, bluetooth, etc. will do.
>
> Regards,
> Rudy Wieser

here is a silly idea
why don't you identify the "Target device" so that someone can provide
you with an example of how to access that specific item
you will find you resolve your problem much faster if you provide all
information.



--
Four fifths of the perjury in the world is expended on tombstones, women
and competitors.
  -- Lord Thomas Dewar

--- SoupGate-Win32 v1.05