MBIM-Proxy

Greg Suarez gpsuarez2512 at gmail.com
Fri Jan 24 14:08:46 PST 2014


On Fri, Jan 24, 2014 at 1:35 PM, Greg Suarez <gpsuarez2512 at gmail.com> wrote:

>
> On Fri, Jan 24, 2014 at 1:24 PM, Aleksander Morgado <
> aleksander at aleksander.es> wrote:
>
>> On 24/01/14 22:20, Greg Suarez wrote:
>> > It looks like I'm going to need to either modify mbim_device_open() to
>> > accept a flags parameter to specify whether to use the proxy.  Would it
>> be
>> > better to create a new function mbim_device_proxy_open() or should we
>> force
>> > the change on existing clients?
>>
>> A new method is better. What I'm not sure is what it should look like.
>> Is it better a method explicitly specifying that the proxy will be used,
>> or otherwise a more generic method (e.g. mbim_device_proxy_open_full())
>> where we just start accepting a set of flags, like libqmi does?
>>
>>
> It might be better to explicitly specify that the proxy will be used since
> when using the proxy
> the client would have to send the proxy the file to open, since there is
> no MBIM equivalent to
> QMI_CTL_SERVICE message.
>
>
I take it back, the file path provided from the mbim_device_new() could be
used.  My mind got lost jumping
back and forth between proxy and client.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libmbim-devel/attachments/20140124/16d9ad5f/attachment.html>


More information about the libmbim-devel mailing list