From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-omap@vger.kernel.org, sre@kernel.org, nekit1000@gmail.com,
mpartap@gmx.net, merlijn@wizzup.org, martin_rysavy@centrum.cz
Subject: ofono for d4: less hcked and more working version was Re: USB networking news, ofono for d4: less hacked version
Date: Fri, 8 May 2020 12:02:12 +0200 [thread overview]
Message-ID: <20200508100211.GA19646@amd> (raw)
In-Reply-To: <20200507140732.GU37466@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 2109 bytes --]
Hi!
> > But I might be confused. I recall some audio patches were needed for
> > basic phone calls (setting up mixers to connect gsm<->audio), but
> > those worked before gsmux support was enabled. (Maybe some hardcoded
> > commands were needed to be sent to gsmmux somewhere).
>
> We're currently reconfiguring the TDM transport that based on the
> unsolicited messages on dlci1. I still need to figure out how to add
> that back while keeping the serdev-ngsm driver generic.
Is it really neccessary? I believe I was simply configuring codecs for
voice call and left them like that.
> > I assume neither gsmmux audio parts nor mixer parts are available in
> > -next at the moment?
>
> Sorry not yet, will post as soon as I have the audio notifiers part
> working, so it will be some days away still with time permitting.
Thanks... feel free to cc me.
I pushed new version of ofono: I'm still not sure about those incoming
sms (but _some_ sms are received). Rest should be better.
Best regards,
Pavel
user@devuan:/my/ofono$ git push
Counting objects: 5, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 479 bytes | 0 bytes/s, done.
Total 5 (delta 4), reused 0 (delta 0)
remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
To github.com:pavelmachek/ofono.git
606faf92..f6f43041 mux-v1.29-3 -> mux-v1.29-3
commit f6f43041ab33e2b811b73d4009ecfa0692d192aa
Author: Pavel <pavel@ucw.cz>
Date: Fri May 8 11:57:04 2020 +0200
Trivial fix for incoming calls. Now basic functionality should
work.
commit 606faf92c289166a5577963f1f987bc321edd226
Author: Pavel <pavel@ucw.cz>
Date: Fri May 8 11:45:32 2020 +0200
Got enough of netreg to work for ofone to talk to us.
Incoming calls do NOT seem to work.
Outgoing calls seem ok.
Incoming SMS seem ok.
Outgoing SMS seem ok.
--
(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 prev parent reply other threads:[~2020-05-08 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 10:11 USB networking news, ofono for d4: less hacked version Pavel Machek
2020-05-06 14:43 ` Tony Lindgren
2020-05-06 23:05 ` Pavel Machek
2020-05-07 14:07 ` Tony Lindgren
2020-05-08 10:02 ` Pavel Machek [this message]
2020-05-09 13:57 ` ofono for d4: less hcked and more working version was " Tony Lindgren
2020-05-09 14:31 ` Tony Lindgren
2020-05-09 19:36 ` 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=20200508100211.GA19646@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=martin_rysavy@centrum.cz \
--cc=merlijn@wizzup.org \
--cc=mpartap@gmx.net \
--cc=nekit1000@gmail.com \
--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).