From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: ofono-bdc2hr5oBkPYtjvyW6yDsg@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
nekit1000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
mpartap-hi6Y0CQ0nG0@public.gmane.org,
merlijn-tF0PIh4TN3odnm+yROfE0A@public.gmane.org
Subject: Motorola motmdm support
Date: Sat, 29 Dec 2018 10:49:54 +0100 [thread overview]
Message-ID: <20181229094953.GA15358@amd> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 883 bytes --]
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.
It uses subset of AT commands (good) with slightly modified
protocol... it says ":OK" instead of "OK" and puts ~ before
unsolicited messages.
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?).
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next reply other threads:[~2018-12-29 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 9:49 Pavel Machek [this message]
2018-12-29 21:16 ` Motorola motmdm support Denis Kenzior
[not found] ` <e959006f-5f8d-8d25-b9d2-dbbcb6a5b073-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-12-29 22:08 ` Pavel Machek
2018-12-30 0:14 ` Denis Kenzior
[not found] ` <20181230181419.GE6707@atomide.com>
[not found] ` <20181230181419.GE6707-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2018-12-30 19:13 ` Denis Kenzior
[not found] ` <20181230202454.GF6707@atomide.com>
[not found] ` <20181230202454.GF6707-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2018-12-30 20:46 ` Denis Kenzior
[not found] ` <20181230212253.GG6707@atomide.com>
[not found] ` <20181230212253.GG6707-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2018-12-30 22:06 ` Denis Kenzior
[not found] ` <5950f965-effa-25ca-3533-de1b95923aa5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-12-30 22:33 ` Pavel Machek
2018-12-31 21:54 ` Pavel Machek
[not found] ` <20181231222329.GI6707@atomide.com>
[not found] ` <20181231222329.GI6707-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2019-01-02 12:15 ` Pavel Machek
[not found] ` <20190107152908.GD5544@atomide.com>
[not found] ` <20190107152908.GD5544-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2019-01-07 17:41 ` Pavel Machek
2018-12-30 22:39 ` 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=20181229094953.GA15358@amd \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=merlijn-tF0PIh4TN3odnm+yROfE0A@public.gmane.org \
--cc=mpartap-hi6Y0CQ0nG0@public.gmane.org \
--cc=nekit1000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ofono-bdc2hr5oBkPYtjvyW6yDsg@public.gmane.org \
--cc=sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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