<div dir="ltr"><div class="gmail_default" style=""><font face="verdana, sans-serif">Hi Aleksander,</font></div><div class="gmail_default" style=""><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style=""><font face="verdana, sans-serif">I have backported the driver and loaded it into my target. I could see the following interfaces in the target/ </font></div><div class="gmail_default" style=""><font face="verdana, sans-serif"># ls -l /dev/mhi0_QMI </font></div><div class="gmail_default" style=""><font face="verdana, sans-serif"># ifconfig mhi_hw0 </font></div><div class="gmail_default" style=""><font face="verdana, sans-serif"><br></font></div><div class="gmail_default" style=""><font face="verdana, sans-serif">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 ? </font></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><b># qmicli -d /dev/mhi0_QMI --dms-get-manufacturer</b></p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">[01 Jan 1970, 00:06:32] -Warning ** [/dev/mhi0_QMI] couldn't
detect transport type of port: unexpected port subsystem</p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">[01 Jan 1970, 00:06:32] -Warning ** [/dev/mhi0_QMI]
requested QMI mode but unexpected transport type found</p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif">[/dev/mhi0_QMI] Device manufacturer retrieved:</p>
<p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"> <span style="background-color:rgb(255,255,0)"> Manufacturer:
'QUALCOMM INCORPORATED'</span></p><p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><span style="background-color:rgb(255,255,0)"><br></span></p><p class="MsoNormal" style="margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><span style="background-color:rgb(255,255,0)">Note : I am also trying to backport the diver from the 5.15 kernel. </span></p></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style=""><font face="verdana, sans-serif">Thanks,</font></div><div class="gmail_default" style=""><font face="verdana, sans-serif">SK</font></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 4, 2022 at 5:37 PM Senthil Kumaresan <<a href="mailto:sekumarejobs@gmail.com">sekumarejobs@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><div id="gmail-m_2673071167273580852composeWebView_editable_content" style="text-align:left"><div>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. </div><div><br></div><div id="gmail-m_2673071167273580852mail-app-auto-default-signature"><br><br>Sent from myMail for iOS<br></div><br><br>Friday, February 4, 2022, 5:33 PM -0500 from Aleksander Morgado <<a href="mailto:aleksander@aleksander.es" target="_blank">aleksander@aleksander.es</a>>:<br><div id="gmail-m_2673071167273580852composeWebView_previouse_content"><blockquote id="gmail-m_2673071167273580852mail-app-auto-quote" style="border-left:1px solid rgb(253,65,76);margin:10px 0px 10px 5px;padding:0px 0px 0px 10px;display:inherit"><div>
<div>
<div id="gmail-m_2673071167273580852style_16440139990000016406_BODY">On Fri, Feb 4, 2022 at 11:19 PM Senthil Kumaresan<br>
<<a href="mailto:sekumarejobs@gmail.com" target="_blank">sekumarejobs@gmail.com</a>> wrote:<br>
><br>
> Ok, thanks for the clarification.<br>
><br>
> So in our case, we need to write a new plugin as others (ex: Foxconn, quectel etc). right?<br>
><br>
<br>
If your device is exposed with the Qualcomm vendor vid; you can rely<br>
on the generic plugin to support it.<br>
<br>
If your device is really from a different manufacturer but they didn't<br>
change the vid (e.g. Sierra EM91xx if I recall correctly), that's a<br>
different thing. I need to add the custom Sierra PCIe module handling<br>
in the Sierra plugin some of these days, matching the subsystem vid<br>
instead, which is the one Sierra specific (something like that)<br>
<br>
-- <br>
Aleksander<br>
<a href="https://aleksander.es" target="_blank">https://aleksander.es</a><br>
</div>
</div>
</div></blockquote></div></div></div>
</blockquote></div>