Hi Aleksander,
I have backported the driver and loaded it into my target. I could see the
following interfaces in the target/
# ls -l /dev/mhi0_QMI
# ifconfig mhi_hw0
I have executed the qmicli and was able to reach the modem. However, the
ModemManager is up but the modem is not getting detected. Is that because
of libgudev as I built the ModemManager with --without-udev ?
*# qmicli -d /dev/mhi0_QMI --dms-get-manufacturer*
[01 Jan 1970, 00:06:32] -Warning ** [/dev/mhi0_QMI] couldn't detect
transport type of port: unexpected port subsystem
[01 Jan 1970, 00:06:32] -Warning ** [/dev/mhi0_QMI] requested QMI mode but
unexpected transport type found
[/dev/mhi0_QMI] Device manufacturer retrieved:
Manufacturer: 'QUALCOMM INCORPORATED'
Note : I am also trying to backport the diver from the 5.15 kernel.
Thanks,
SK
On Fri, Feb 4, 2022 at 5:37 PM Senthil Kumaresan <sekumarej...@gmail.com>
wrote:
> Ok got it. Thanks for your explanation and it is really helpful. I have
> taken 4.14 back ported driver. I will try and get back. Thanks for your
> support.
>
>
>
> Sent from myMail for iOS
>
>
> Friday, February 4, 2022, 5:33 PM -0500 from Aleksander Morgado <
> aleksan...@aleksander.es>:
>
> On Fri, Feb 4, 2022 at 11:19 PM Senthil Kumaresan
> <sekumarej...@gmail.com> wrote:
> >
> > Ok, thanks for the clarification.
> >
> > So in our case, we need to write a new plugin as others (ex: Foxconn,
> quectel etc). right?
> >
>
> If your device is exposed with the Qualcomm vendor vid; you can rely
> on the generic plugin to support it.
>
> If your device is really from a different manufacturer but they didn't
> change the vid (e.g. Sierra EM91xx if I recall correctly), that's a
> different thing. I need to add the custom Sierra PCIe module handling
> in the Sierra plugin some of these days, matching the subsystem vid
> instead, which is the one Sierra specific (something like that)
>
> --
> Aleksander
> https://aleksander.es
>
>
