Bjørn Mork <bjorn@xxxxxxx> writes: > However, I was unable to verify the mode. Can connect, but cannot see > any data. And now I cannot get anything through at all even after > switching back. Oh well... That's for experimenting. Don't think this > command is ready for inclusion anywhere yet. We need to understand it > better first. From your docs it seems obvious, but there are some finer > details here. It's pretty weird. I get the impression that I've successfully set protocol == 1 when sending the request while offline: QMUX Header: len: 0x0014 sender: 0x00 (client) svc: 0x00 (ctl) cid: 0x00 QMI Header: Flags: 0x00 (request) TXN: 0x000d Cmd: 0x0026 (SET_DATA_FORMAT) Size: 0x0009 TLV: 0x01 (CTL/Set Data Format Request/Format) Size: 0x0001 Data: 01 TLV: 0x10 (CTL/Set Data Format Request/Protocol) Size: 0x0002 Data: 01 00 read 24 bytes QMUX Header: len: 0x0017 sender: 0x80 (service) svc: 0x00 (ctl) cid: 0x00 QMI Header: Flags: 0x02 (response) TXN: 0x000d Cmd: 0x0026 (SET_DATA_FORMAT) Size: 0x000c TLV: 0x02 (CTL/Set Data Format Response/Result Code) Size: 0x0004 Status: 0 (SUCCESS) Error: 0 TLV: 0x10 (CTL/Set Data Format Response/Protocol) Size: 0x0002 Data: 01 00 Then I connect and send the same request again: read 21 bytes QMUX Header: len: 0x0014 sender: 0x00 (client) svc: 0x00 (ctl) cid: 0x00 QMI Header: Flags: 0x00 (request) TXN: 0x000d Cmd: 0x0026 (SET_DATA_FORMAT) Size: 0x0009 TLV: 0x01 (CTL/Set Data Format Request/Format) Size: 0x0001 Data: 01 TLV: 0x10 (CTL/Set Data Format Request/Protocol) Size: 0x0002 Data: 01 00 read 24 bytes QMUX Header: len: 0x0017 sender: 0x80 (service) svc: 0x00 (ctl) cid: 0x00 QMI Header: Flags: 0x02 (response) TXN: 0x000d Cmd: 0x0026 (SET_DATA_FORMAT) Size: 0x000c TLV: 0x02 (CTL/Set Data Format Response/Result Code) Size: 0x0004 Status: 0 (SUCCESS) Error: 0 TLV: 0x10 (CTL/Set Data Format Response/Protocol) Size: 0x0002 Data: 02 00 I.e. getting protocol == 2 back. No wonder I cannot get things to work again. But this sure as hell isn't very user friendly. How about getting an error code if I'm unable to change settings? Or how about actually keeping the settings after confirming that they were set? Yes, I am still going to claim that this firmware is very, very, very buggy. But I am also sure that we have to live with that somehow. 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
