On Wed, 2014-07-23 at 14:33 +0000, Stanescu Victor wrote:
> /dev/cdc-wdm2 doesn't work. Further more, instead of freezing at cat, it
> freezes from echo.
>
> Ctrl-c doesn't stop the frozen echo.
I'm pretty sure this device does not expose QMI at all, from looking at
through the drivers. The driver package from HP *does* have QMI
drivers, but only for the lt4112/lt4124/lt4126. The hs3110/hs3114 are
assigned to the "Jungo"-type driver for Win < 8. For example:
<DeviceInfo>
<item module="MU736" VID="03F0" PID="521D" Baseline="JUNGO" Remark="HP"/>
<item module="MU736" VID="03F0" PID="541D" Baseline="JUNGO" Remark="HP"/>
<item module="ME906" VID="03F0" PID="581D" Baseline="QUALCOMM" Remark="HP"/>
<item module="ME906" VID="03F0" PID="561D" Baseline="QUALCOMM" Remark="HP"/>
<item module="ME906" VID="03F0" PID="591D" Baseline="QUALCOMM" Remark="HP"/>
</DeviceInfo>
In any case, if the devices have MBIM descriptors, then we should try to
drive them via MBIM, since that appears to be what happens with these
devices on Windows 8. Otherwise, it should be AT+ECM I think, but not
QMI for the 3110/3114.
Dan
> On 07/23/2014 12:45 PM, Bjørn Mork wrote:
> > Stanescu Victor <Victor.Stanescu@xxxxxxxxx> writes:
> >
> >> root@victor-laptop:~# modprobe qmi_wwan
> >> root@victor-laptop:~# dmesg
> >> [ 6005.900671] usbcore: registered new interface driver cdc_wdm
> >> [ 6005.902682] usbcore: registered new interface driver qmi_wwan
> >> root@victor-laptop:~# echo "03f0 521d" >
> >> /sys/bus/usb/drivers/qmi_wwan/new_id
> >> root@victor-laptop:~# dmesg
> >> [ 6005.900671] usbcore: registered new interface driver cdc_wdm
> >> [ 6005.902682] usbcore: registered new interface driver qmi_wwan
> >> [ 6023.507185] qmi_wwan 2-6:1.0: cdc-wdm0: USB WDM device
> >> [ 6023.507419] qmi_wwan 2-6:1.0 wwan0: register 'qmi_wwan' at
> >> usb-0000:00:14.0-6, WWAN/QMI device, 02:b2:8c:7a:5d:55
> > Right. I was hoping you would have the usb-serial driver bound to this
> > and the other serial functions so you avoided this. But it's not really
> > a problem, just a bit confusing. You have to adjust the tests a bit.
> >
> >
> >> [ 6023.508210] qmi_wwan: probe of 2-6:1.1 failed with error -22
> >> [ 6023.509177] qmi_wwan: probe of 2-6:1.2 failed with error -22
> >> [ 6023.509871] qmi_wwan 2-6:1.3: cdc-wdm1: USB WDM device
> >> [ 6023.510099] qmi_wwan 2-6:1.3 wwan1: register 'qmi_wwan' at
> >> usb-0000:00:14.0-6, WWAN/QMI device, 02:b2:8c:7a:5d:55
> >> [ 6023.511420] qmi_wwan 2-6:1.4: cdc-wdm2: USB WDM device
> >> [ 6023.511604] qmi_wwan 2-6:1.4 wwan2: register 'qmi_wwan' at
> >> usb-0000:00:14.0-6, WWAN/QMI device, 58:2c:80:13:92:63
> >
> > This is the only possible candidate. So you should do all testing on
> > the wwan2 and /dev/cdc-wdm2 devices.
> >
> >> root@victor-laptop:~# qmicli -d /dev/cdc-wdm0 --device-open-version-info
> >> --wds-noop
> >> error: couldn't open the QmiDevice: Transaction timed out
> >> root@victor-laptop:~# echo -e "ATI\r" > /dev/cdc-wdm0
> >> root@victor-laptop:~# cat /dev/cdc-wdm0
> >> [frozen]
> > Please repeat this using the /dev/cdc-wdm2 instead. The frozen output
> > can be cancelled by ctrl+C
> >
> >
> >
> > Bjørn
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
