diff options
| author | Aleksander Morgado <aleksander@aleksander.es> | 2022-03-16 15:44:46 +0100 |
|---|---|---|
| committer | Aleksander Morgado <aleksander@aleksander.es> | 2022-03-18 10:19:23 +0100 |
| commit | 8fa701a945260dd716197f0d9ad5d2ac26d4d02e (patch) | |
| tree | 789f1fea1e1a54239f83401e9965184782c4f761 /data | |
| parent | 3cc7e7e31bd0c01d4177787dc2e0f13cb631c440 (diff) | |
| download | libqmi-8fa701a945260dd716197f0d9ad5d2ac26d4d02e.tar.gz | |
qmi-firmware-update: always validate type of TTY before using it
When listing TTYs or waiting for TTYs, always explicitly specify the
exact mode the modem should be in, so that we don't get the wrong
device.
E.g. after a reset request, always wait for a TTY with the device in
download mode.
The modem mode is automatically detected based on the amount of USB
interfaces the device exposes. If the device has a single USB
interface, then it's in download mode, otherwise it's in modem mode.
A vid:pid match could also be possible, but it would be harder to
maintain. Let's use this approach for now and see how it goes.
Diffstat (limited to 'data')
0 files changed, 0 insertions, 0 deletions