Re: How frequently org.freedektop.ModemManager.Modem.Cdma.SignalQuality signals signal strength?

[satya gowtham kudupudi <satyagowtham k gmail com>]

hi, this is what i've done...

1. i found 3 endpoints on interface 0.

2. # echo 1-1.2:1.0 > /sys/bus/usbl/drivers/option/unbind

3. # modprobe qmi_wwan

4. echo "19d2 fff1" > /sys/bus/usb/drivers/qmi_wwan/new_id

5. installed libqmi-utils

i didnt find /dev/cdc-wdmX device !

what should i do now?

Thanks!

On Wed, Jul 3, 2013 at 7:39 PM, Bjørn Mork <bjorn mork no> wrote:

satya gowtham kudupudi <satyagowtham k gmail com> writes:

> /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/ttyUSB0/tty/ttyUSB0/dev
> /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/ttyUSB1/tty/ttyUSB1/dev
> /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.2/ttyUSB2/tty/ttyUSB2/dev
> /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/ttyUSB3/tty/ttyUSB3/dev
> /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.4/ttyUSB4/tty/ttyUSB4/dev
> /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.5/host5/target5:0:0/5:0:0:0/bsg/5:0:0:0/dev
> /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.5/host5/target5:0:0/5:0:0:0/block/sdb/dev
> /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.5/host5/target5:0:0/5:0:0:0/scsi_generic/sg1/dev
>
> this is sys tree i get when i plug in my modem. With this can u say whether
> my modem is QMI capable?

No, I cannot.  But I can say that it doesn't match the Gobi1k or Gobi2k
layouts.

> How to add VID/PID pair to the kernel driver and recompile it?

You don't need to do that just to test.  A QMI function needs 3
endpoints, so first try to find out if any of the unknown USB interfaces
have 3.    "lsusb -vd 19d1:fff1" will tell you this.

For example:

    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0

means that interface #3 has 3 endpoints and is a suspect.  Then unbind
this interface from the option driver and dynamically add the device ID
to qmi_wwan:

 echo 2-1.2:1.3 >/sys/bus/usb-serial/drivers/option1/unbind
 modprobe qmi_wwan
 echo 19d1 fff1 >/sys/bus/usb/drivers/qmi_wwan/new_id


This should make qmi_wwan bind to interface #3 instead of option.  You
can now use libqmi tools to probe the /dev/cdc-wdmX device.  Or let MM
probe it if you built MM with QMI support.

Repeat for every unknown (i.e not successfully probed by MM) interface
with 3 endpoints.


Bjørn

--
- Gowtham