On 03/01/2016 12:44, Lars-Peter Clausen wrote:
> Hi,
>
> On 12/31/2015 02:53 PM, Marc Titinger wrote:
>>
>> On behalf of Hubert Chaumette (author)
>>
>>
>> Clarification on usage:
>>
>> 'conn' was used for the IP in previous iterations, but the current code
>> uses libiio's IIOD_REMOTE variable for that. Instead, conn is now used
>> to choose a device, on branch generic-iio. This example should be:
>>
>> $ IIOD_REMOTE=$IP_OF_IIOD sigrok-cli --driver
>> generic-iio:conn=$IIO_DEVICE_ID_OR_NAME --samples 3
something like 'conn=${hostip},${device_name_or_id}' ?
example: conn=192.168.1.69,device0
IDK if this is legit in terms of parameter parsing in Sigrok,:I assume,
the common parsing code will provide a parameter value like "ip,device"
for us to re-parse, which is fine.
>
> I think it is better if we can specify the target as part of the connection
> string. IIOD_REMOTE can be used to provide a system wide default and it can
> also be used to overwrite things when invoking a single application. But
> this really only works if the application is started from the command line
> and the application only wants to talk to devices from the same host.
>
> With a library like sigrok neither of the last two is necessarily the case.
> E.g. lets take pulseview which uses libsigrok, you'd have to launch the
> application from the command line to specify the target, you'd have to
> restart the application if you want to change hosts and you could only talk
> to devices from the same host at the same time. Same is true for other
> similar applications that try to use libsigrok.
>
> - Lars
>
------------------------------------------------------------------------------
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
