All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.org
Subject: Manually packetizing data for motorola modem was Re: Test clients for ofono: rfone, Unicsy Demo
Date: Sun, 03 Mar 2019 23:49:27 +0100	[thread overview]
Message-ID: <20190303224927.GA12652@amd> (raw)
In-Reply-To: <20190214101117.GA6132@amd>

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

Hi!

I'm still fighting with SMS sending on Motorola Droid 4. Yes, its
kernel driver is somehow interesting... and work in progress.

If packets are split correctly, SMS sending works. 

ofonod[2900]: OutSMS: > AT+GCMGS=\r
ofonod[2900]: OutSMS: > 3100098106343401F30000A70A73F45B4E07D1CB733A<CtrlZ>
ofonod[2900]: OutSMS: < +GCMGS=10,"00/00/00,01:00:00+00"\r\n

But if data are sent in one write, it does not... (and even this
is not easy to do with ofono).

ofonod[3131]: OutSMS: > AT+GCMGS=\r3100098106343401F30000A70A73F45B4E07D1CB733A<CtrlZ>
ofonod[3131]: OutSMS: < :ERROR=18\r\n
Handle command response: :ERROR=18
Handle terminator list

Is there easy way to do the splitting? I can do

        g_at_io_write(data->send_chat->parent->io, buf, strlen(buf));
 	g_io_channel_flush(data->send_chat->parent->io->channel, NULL);
						   
But that needs exporting functions I guess you'd rather not have
exported.

Is there better way?

Best regards,
									Pavel
-- 
(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 --]

      reply	other threads:[~2019-03-03 22:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 10:11 Test clients for ofono: rfone, Unicsy Demo Pavel Machek
2019-03-03 22:49 ` Pavel Machek [this message]

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=20190303224927.GA12652@amd \
    --to=pavel@ucw.cz \
    --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.