From: Pavel Machek <pavel@ucw.cz>
To: ofono@ofono.org
Subject: Re: Weird Droid 4 modem protocol and a way to support it
Date: Wed, 10 Jun 2020 18:24:30 +0200 [thread overview]
Message-ID: <20200610162430.GA4109@amd> (raw)
In-Reply-To: <bf3dfd8a-d192-0c6a-d0ee-6480bea81e13@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]
Hi!
> >I'd really like to get support for Droid 4 modem... unfortunately it
> >is quite special. Few words about Droid 4 modem protocol:
> >
>
> <snip>
>
> >
> >I'm not sure what is the best way to support it. I was not able to get
> >atchat.c to work with it (and I don't think it is quite suitable), so
> >I ended up copying it and modifying it for Droid 4 protocol.
> >
> >Is that acceptable? Can you see a better way?
>
> I don't think there's really another way. So the approach of duplicating
> GAtChat and everything inside drivers/atmodem is likely the way to go.
Ok, thanks for confirmation.
> But if you pursue this, we really should throw out as much of the legacy in
> gatchat as possible:
>
> - g_at_chat_suspend / resume is likely not needed (you're probably not
> running PPP over these, right)?
> - stuff like g_at_chat_set_wakeup is only relevant for some weird modems and
> probably isn't relevant here
> - add_terminator / blacklist_terminator might not be needed
> - Some other concepts might not be needed, like send_pdu_listing and
> send_and_expect_short_prompt. Those are really only for weird SMS commands.
> - It might also be possible to greatly simplify the GAtParser
> concept.
I believe I don't need GAtParser at all.
> - I'd also just put this all directly into drivers/motmodem/* instead of
> trying to extend gatchat library itself.
Yes.
> Most importantly though, we should stop using glib. oFono is (glacially
> slowly) being ported over to ell. So I don't really want to accept any new
> glib code.
So... this code started as copy of gatchat, with me removing the
obviously-unneeded stuff. I guess I can convert motchat easily when
atchat is converted... but I'm not sure I understand the code well
enough to do conversion on my own.
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 --]
next prev parent reply other threads:[~2020-06-10 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-08 23:59 Weird Droid 4 modem protocol and a way to support it Pavel Machek
2020-06-09 16:00 ` Denis Kenzior
2020-06-10 16:24 ` Pavel Machek [this message]
2020-07-11 12:10 ` Pavel Machek
[not found] <20200610140042.GW43721@atomide.com>
2020-06-10 19:30 ` 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=20200610162430.GA4109@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.