From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: ofono-bdc2hr5oBkPYtjvyW6yDsg@public.gmane.org,
kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-arm-kernel
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@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 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: 0 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.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: 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 #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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
WARNING: multiple messages have this Message-ID (diff)
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: 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 #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next reply other threads:[~2019-08-10 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 23:14 Pavel Machek [this message]
2019-08-10 23:14 ` Motorola Droid 4 SMS sending Pavel Machek
2019-08-10 23:14 ` Pavel Machek
2019-08-10 23:14 ` Pavel Machek
2019-08-11 14:25 ` Denis Kenzior
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-+zi9xunit7i@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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 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.