Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Motorola motmdm support
Date: Sat, 29 Dec 2018 15:16:08 -0600	[thread overview]
Message-ID: <e959006f-5f8d-8d25-b9d2-dbbcb6a5b073@gmail.com> (raw)
In-Reply-To: <20181229094953.GA15358@amd>

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

Hi Pavel,

On 12/29/2018 03:49 AM, Pavel Machek wrote:
> Hi!
> 
> Motorola phones use "interesting" setup.
> 
> There's qmi and "normal" (but very buggy) AT interface on
> them. Unfortunately that uses USB and uses too much power (which is a
> problem on phone).
> 
> Plus there's /dev/motmdm1, motmdm3 and motmdm9, multiplexed over
> serial line.

Kernel 27.010 multiplexer or something else entirely?

> 
> It uses subset of AT commands (good) with slightly modified
> protocol... it says ":OK" instead of "OK" and puts ~ before
> unsolicited messages.

Funny

> 
> Other major difference is that commands need to be sent to the right
> device. It seems motmdm1 is for status and call control, and motmdm9
> is for incoming sms.
> 
> I guess that right way to do this is to introduce
> drivers/motorolamodem (or can we just have drivers/motorola?).
> 

For some weird historic reason we called the atom drivers and thus the 
subdirectory housing the relevant sources with the 'modem' suffix.  So I 
guess we should stick to that just to be consistent.

We can have a separate discussion on whether it makes sense to drop the 
'modem' suffix and what the implications are (probably none).  If we 
decide to drop the suffix, then we should/will do it for all drivers.

Regards,
-Denis

  reply	other threads:[~2018-12-29 21:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29  9:49 Motorola motmdm support Pavel Machek
2018-12-29 21:16 ` Denis Kenzior [this message]
2018-12-29 22:08   ` Pavel Machek
2018-12-30  0:14     ` Denis Kenzior
2018-12-30 22:39 ` Pavel Machek
     [not found] <20181230181419.GE6707@atomide.com>
2018-12-30 19:13 ` Denis Kenzior
     [not found] <20181230202454.GF6707@atomide.com>
2018-12-30 20:46 ` Denis Kenzior
     [not found] <20181230212253.GG6707@atomide.com>
2018-12-30 22:06 ` Denis Kenzior
2018-12-30 22:33   ` Pavel Machek
2018-12-31 21:54 ` Pavel Machek
     [not found] <20181231222329.GI6707@atomide.com>
2019-01-02 12:15 ` Pavel Machek
     [not found] <20190107152908.GD5544@atomide.com>
2019-01-07 17:41 ` Pavel Machek

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=e959006f-5f8d-8d25-b9d2-dbbcb6a5b073@gmail.com \
    --to=denkenz@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox