Backport qmi wwan driver to linux 2.6.32 on ARM

Markus Gothe nietzsche at lysator.liu.se
Wed Aug 12 15:03:48 PDT 2015


Guess it might be related to: ‘QmiWdsGetCurrentSettingsRequestedSettings’ right?
But is this implemented in the Modem-manager?

//M


On 12 Aug 2015, at 22:25 , Markus Gothe <nietzsche at lysator.liu.se> wrote:

> Dan,
> do you have any example of how to retrieve the IP configuration using QMI?
> I’d prefer to implemented it in uqmi like the way umbim handles the IP configuration.
> 
> //M
> On 12 Aug 2015, at 18:19 , Dan Williams <dcbw at redhat.com> wrote:
> 
>> On Wed, 2015-08-12 at 09:10 +0000, 蒋品 wrote:
>>> Hi, Bjørn
>>> 
>>>      Thanks a lot for your kind help and reminding. The backport kernel compilation failed due to it's not a vanilla kernel, it already got some function backported from 3.x.  So we see some redefinition error.
>>> 
>>>       I commented out some lines in the file and got the compat.ko /usbnet.ko / cdc-wdm.ko/ qmi_wwan.ko
>>>       compiled and loaded on the target system.
>>> 
>>>       I am now playing with the modeswitch, /dev/cdc-wdm0 has appeared. Does it mean the device is ready and I can get a qmi-cli/uqmi talk to it ?  Do I have to get something like /dev/qmi_wwan appear in the system ?
>> 
>> /dev/cdc-wdmX (there can be more than one) is all you need.  You can
>> then use "qmicli -d /dev/cdc-wdm0 --dms-get-capabilities" to talk to the
>> QMI port and see if everything is working correctly.  There should also
>> be an ethernet interface exposed by the modem, separately from the
>> cdc-wdm interface.  The ethernet interface is what you would configure
>> the IP settings on through either DHCP (supported by many modems),
>> static IP (through settings returned by QMI), or possibly IPv6 RA.
>> 
>> Dan
>> 
>>> BRs, Jiang Pin ( Richard )
>>> 
>>> 2015年8月11日 上午12:31,Bjørn Mork <bjorn at mork.no> 写道:
>>>> 蒋品 <jiang.pin at icloud.com> writes:
>>>> 
>>>>> I wonder if it is possible to backport the qmi driver to linux 2.6.32?
>>>> 
>>>> It is. But the only remotely sane reason to use a kernel that old is
>>>> that it is supported by some hardware vendor. Use that support.
>>>> 
>>>>> wildc at wildc-HP-Pavilion-dv4-Notebook-PC:~/backports-3.14-1$ echo $KLIB_BUILD
>>>>> /home/wildc/ArDroine2.0_LinuxSource/kernel/
>>>>> 
>>>>> ARCH=arm CROSS_COMPILE=~/tool-chain/arm-2009q1/bin/arm-none-linux-gnueabi- make
>>>>> CC [M] /home/wildc/backports-3.14-1/compat/main.o
>>>>> In file included from /home/wildc/backports-3.14-1/compat/compat-2.6.34.h:8,
>>>>> from /home/wildc/backports-3.14-1/compat/main.c:5:
>>>>> /home/wildc/backports-3.14-1/backport-include/linux/mmc/sdio_func.h:21: error: redefinition of typedef 'mmc_pm_flag_t'
>>>>> include/linux/mmc/pm.h:25: error: previous declaration of 'mmc_pm_flag_t' was here
>>>> 
>>>> In what way is this supposed to be related to the qmi_wwan driver? Did
>>>> you even look at the code you are trying to build?
>>>> 
>>>> 
>>>> 
>>>> Bjørn
>>> _______________________________________________
>>> libqmi-devel mailing list
>>> libqmi-devel at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>> 
>> 
>> _______________________________________________
>> libqmi-devel mailing list
>> libqmi-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
> 
> //Markus - The panama-hat hacker
> 
> _______________________________________________
> libqmi-devel mailing list
> libqmi-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel

//Markus - The panama-hat hacker

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 186 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20150813/77cb40f9/attachment.sig>


More information about the libqmi-devel mailing list