From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.org, kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, sre@kernel.org,
nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org
Subject: Motorola Droid 4 SMS sending
Date: Sun, 11 Aug 2019 01:14:04 +0200 [thread overview]
Message-ID: <20190810231404.GA26417@amd> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1006 bytes --]
Hi!
Motorola Droid 4 runs packet protocol over serial... and its kernel
driver requires explicit "write()" boundaries at places where packet
boundaries should be.
So I can send SMS using low level g_at... functions (that are not
normally accessible), but not using g_at_chat_send().
If anyone has good idea for clean (or clean enough) solution, let me
know.
Best regards,
Pavel
snprintf(buf, sizeof(buf), "AT+GCMGS=\r");
encode_hex_own_buf(pdu, pdu_len, 0, buf_pdu);
#if WANT_IT_BROKEN
strcat(buf, buf_pdu+2);
g_at_chat_send(data->send_chat, buf, none_prefix, NULL, data, NULL);
#else
g_at_io_write(data->send_chat->parent->io, buf, strlen(buf));
g_at_io_write(data->send_chat->parent->io, buf_pdu, strlen(buf_pdu));
g_io_channel_flush(data->send_chat->parent->io->channel, NULL);
#endif
--
(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: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2019-08-10 23:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190810231404.GA26417@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--cc=ofono@ofono.org \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).