<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/04/2014 00:02, Aleksander Morgado
wrote:<br>
</div>
<blockquote
cite="mid:CAAP7uc+3pGA_wJ4zoN0R6cH=35EphzyPE5CzHeDynORtW7cj+Q@mail.gmail.com"
type="cite">
<pre wrap="">On Thu, Apr 10, 2014 at 9:47 PM, Bjørn Mork <a class="moz-txt-link-rfc2396E" href="mailto:bjorn@mork.no"><bjorn@mork.no></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">For example, if you want to support NMEA over DSS using gpsd, then you
will create a userspace application which
- starts the appropriate DSS session
- creates the matching VLAN
- proxies the VLAN to a pty, adding and stripping ethernet headers
- adds the pty to the list of gpsd devices
I believe it would make sense for libmbim to provide utility functions
taking care of the first three.
</pre>
</blockquote>
<pre wrap="">
Yes, we should handle that case. As you say, the VLAN is just a
convenient interface, which may not be what user-space expects (e.g. a
character device). If possible libmbim/mbimcli should allow handling
those 3 first steps.
</pre>
</blockquote>
<font size="-1"> If we continue using VLAN we still depends on wwan
interface status to access DSS channels. So we have to link
NetworkManager to libmbim to avoid putting down wwan interface if
there is any DSS channel open.<br>
<br>
What about opening DSS channel when wwan interface is down?<br>
<br>
Arnaud<br>
</font>
</body>
</html>