From: Jonas Bonn <jonas@norrbonn.se>
To: ofono@ofono.org
Subject: Re: Unsalble cellular connection
Date: Mon, 19 Aug 2019 10:17:33 +0200 [thread overview]
Message-ID: <b7da36fc-0093-1b54-eb6a-4785c74521d2@norrbonn.se> (raw)
In-Reply-To: <CAOf5uw=fQe4cuTfdciqW3hmXHXv-tY2UYd4aLfMVxF5Lx65jbw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
Hi Michael,
Re-adding JH and mailing lists to conversation...
On 19/08/2019 10:00, Michael Nazzareno Trimarchi wrote:
> Hi
>
> On Mon, Aug 19, 2019 at 9:51 AM Jonas Bonn <jonas@norrbonn.se> wrote:
>>
>>
>>
>> On 19/08/2019 09:36, Michael Nazzareno Trimarchi wrote:
>>> Can be chattering and rush current? Even are you sure that you don't have
>>> some reset our of the ofono service that send an at command that
>>> restart the modem?
>>
>> Just to try to prevent us from going down the wrong rabbit hole here:
>> i) The modem is a QMI device so there are no AT commands being sent
>
> Ok, so the uart used as ttyUSB0 and ttyUSB1 they don't support any AT command?
> Is qmi part only the network interface?
ttyUSB0 and ttyUSB1 _do_ support AT commands, but are complementary to
the QMI interface which is a complete communication channel to the modem
in itself. The network interface is _only_ for the QMI channel: the
network packets are carried on a dedicated endpoint of the USB interface
supporting QMI.
I think the question of QMI vs AT is moot here. Internally the modem
does pretty much the same thing; it's just the interface that looks a
bit different.
In JH's case, only the 'qmimisc' device and the 'network' interface are
in play via ofono. These are separate endpoints on a single USB
interface, all managed by the qmi-wwan driver in the kernel.
/Jonas
next parent reply other threads:[~2019-08-19 8:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOf5uw=fQe4cuTfdciqW3hmXHXv-tY2UYd4aLfMVxF5Lx65jbw@mail.gmail.com>
2019-08-19 8:17 ` Jonas Bonn [this message]
[not found] <CAOf5uw=6hQkfhAt=OWH+mim30NyOHU6Z8GVMJ6yKCEf=1NFw8w@mail.gmail.com>
2019-08-19 7:50 ` Unsalble cellular connection Jonas Bonn
2019-08-19 7:56 ` Jonas Bonn
[not found] <CAOf5uw=2U6MkcKP8OzWNyzwvxjAvYLdXuDASFVEjnWvMQ0fjHw@mail.gmail.com>
2019-08-19 1:51 ` JH
2019-08-19 5:38 ` Jonas Bonn
2019-08-19 14:18 ` JH
[not found] <CAA=hcWSVcULFW4jo5q9RsxW4igozgM99oJN6KoZ8UaSLdLhD7g@mail.gmail.com>
2019-08-13 15:00 ` Jonas Bonn
2019-08-14 11:11 ` JH
2019-08-14 13:00 ` Jonas Bonn
2019-08-15 11:33 ` Daniel Wagner
2019-08-15 12:45 ` JH
2019-08-15 14:58 ` Daniel Wagner
2019-08-17 11:53 ` JH
2019-08-17 11:55 ` JH
2019-08-17 14:09 ` Jonas Bonn
2019-08-17 22:29 ` JH
2019-08-01 11:01 JH
2019-08-01 18:16 ` Giacinto Cifelli
2019-08-02 10:46 ` JH
2019-08-02 17:43 ` Giacinto Cifelli
2019-08-07 10:27 ` JH
2019-08-09 3:59 ` Giacinto Cifelli
2019-08-09 12:56 ` JH
2019-08-11 11:57 ` JH
2019-08-11 13:37 ` Giacinto Cifelli
2019-08-12 6:54 ` JH
2019-08-12 22:09 ` JH
2019-08-13 6:42 ` Jonas Bonn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7da36fc-0093-1b54-eb6a-4785c74521d2@norrbonn.se \
--to=jonas@norrbonn.se \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.