Hi Tomasz,
On Thu, 29 Jul 2021 at 15:49, Aleksander Morgado
<aleksan...@aleksander.es> wrote:
>
> Hey,
>
> > I have modified the plugin as suggested.
> > There's some progress but no success yet.
> >
> > I have started Modem Manager, then executed (we're running on openwrt with
> > no udev):
> > mmcli --report-kernel-event="action=add,subsystem=wwan,name=wwan0mbim0"
> >
> > And then observed that Modem Manager tried talking to modem using QMI first
> > and them MBIM but without success. The log is below.
> >
>
> Ok. I think you're the first ones I know of doing that testing :)
>
> > Thanks,
> > Tomasz
> >
> > root@OpenWrt:~# ls /dev/wwan*
> > /dev/wwan0at0 /dev/wwan0mbim0
> >
> > [7442]: <debug> [base-manager] kernel event reported:
> > [7442]: <debug> [base-manager] action: add
> > [7442]: <debug> [base-manager] subsystem: wwan
> > [7442]: <debug> [base-manager] name: wwan0mbim0
> > [7442]: <debug> [base-manager] uid: n/a
> > [7442]: <debug> [wwan0mbim0] preloading contents and properties...
> > [7442]: <debug> [wwan0mbim0] sysfs path:
> > /sys/devices/platform/soc@0/884057000000.pci/pci0002:57/0002:57:00.0/0002:58:00.0/mhi0/wwan/wwan0/wwan0mbim0
> > [7442]: <debug> [wwan0mbim0] port contents loaded:
> > [7442]: <debug> [wwan0mbim0] bus: pci
> > [7442]: <debug> [wwan0mbim0] device:
> > /sys/devices/platform/soc@0/884057000000.pci/pci0002:57/0002:57:00.0
> > [7442]: <debug> [wwan0mbim0] subsystems: wwan, mhi, pci
> > [7442]: <debug> [wwan0mbim0] drivers: mhi-pci-generic, pcieport
> > [7442]: <debug> [wwan0mbim0] vendor: 177d
> > [7442]: <debug> [wwan0mbim0] product: a22d
> > [7442]: <debug> [wwan0mbim0] revision: 0002
> > [7442]: <debug> [wwan0mbim0] ID_VENDOR_ID: 0x177d
> > [7442]: <debug> [wwan0mbim0] ID_MODEL_ID: 0xa22d
> > [7442]: <debug> [wwan0mbim0] ID_REVISION: 0x0002
> > [7442]: <debug> [wwan0mbim0] property added: ID_MM_CANDIDATE=1
> > [7442]: <warn> [wwan0mbim0] unknown match condition parameter: ATTR{type}
> > [7442]: <warn> [wwan0mbim0] unknown match condition parameter: ATTR{type}
> > [7442]: <warn> [wwan0mbim0] unknown match condition parameter: ATTR{type}
> > [7442]: <warn> [wwan0mbim0] unknown match condition parameter: ATTR{type}
> > [7442]: <warn> [wwan0mbim0] unknown match condition parameter: ATTR{type}
> > [7442]: <warn> [wwan0mbim0] invalid pattern in rule '*MBIM': Error while
> > compiling regular expression *MBIM at char 0: nothing to repeat
> > [7442]: <warn> [wwan0mbim0] invalid pattern in rule '*QMI': Error while
> > compiling regular expression *QMI at char 0: nothing to repeat
> > [7442]: <warn> [wwan0mbim0] invalid pattern in rule '*AT': Error while
> > compiling regular expression *AT at char 0: nothing to repeat
> > [7442]: <warn> [wwan0mbim0] invalid pattern in rule '*QCDM': Error while
> > compiling regular expression *QCDM at char 0: nothing to repeat
> > [7442]: <warn> [wwan0mbim0] invalid pattern in rule '*FIREHOSE': Error
> > while compiling regular expression *FIREHOSE at char 0: nothing to repeat
>
> Those warnings above show that the current available rules to flag
> port type hints based on either type or name are failing badly when
> using the limited built-in udev parser. I've opened this issue to
> track it:
> https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/410
I've submitted a patch:
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/593
It fixes the ATTR parsing issue, not the regular expression, but
should be enough to solve your 'qmi' probing issue.
Regards,
Loic
