Hey,
> > > It does mean that MM will have to instantiate net ports and
> > > then assign the mux ID to the QmiDevice, and then set it again in the
> > > Bind Mux Data Port message, which leaves room for those potentially
> > > getting out of sync.
> >
> > Why would this not be a problem in the
Thanks for taking a look, see responses inline.
On Thu, Oct 15, 2020 at 12:35 PM Aleksander Morgado
wrote:
>
> > However, delegating it to MM also works. I think that the conceptual
> > design is cleaner here as interacting with netlink to create
> > interfaces isn't really something that makes
Hey!
>
> As part of the QRTR integration into MM we're trying to figure out
> whose responsibility it is to make rmnet_data net interfaces for a
> QRTR/IPA-based modem. I had started an MR[1] that gave this
> responsibility to libqmi, but it's not clear this is the right place
> for this to go.
>
Hey all,
As part of the QRTR integration into MM we're trying to figure out
whose responsibility it is to make rmnet_data net interfaces for a
QRTR/IPA-based modem. I had started an MR[1] that gave this
responsibility to libqmi, but it's not clear this is the right place
for this to go.
If we
