From: Tony Lindgren <tony@atomide.com>
To: Pavel Machek <pavel@ucw.cz>
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: Re: USB networking news, ofono for d4: less hacked version
Date: Wed, 6 May 2020 07:43:38 -0700 [thread overview]
Message-ID: <20200506144338.GT37466@atomide.com> (raw)
In-Reply-To: <20200506101125.GA7490@amd>
* Pavel Machek <pavel@ucw.cz> [200506 10:12]:
> Hi!
>
> So... I found out that USB networking works way better when I don't
> attempt to charge the phone at the same. Yes, green light was
> blinking.
OK yes we don't have much of a charger detection currently and the
charger tries to reconnect with the LED blinking rapidly with an
empty battery.
> To github.com:pavelmachek/ofono.git
> e7b58fdd..1e7e5ce3 mux-v1.19-2 -> mux-v1.19-2
>
> which creates copy of atchat, so I don't damage existing
> functionality. It still seems to somehow work. Lot more work is still
> needed. Designed to work with latest kernel patches from Tony, using
> gsmmux interfaces.
OK, sounds like that should work :)
I still need to figure update audio notifications for the current set of
gsmmux patches. Eventually maybe ofono can just set the voice call audio
routing using alsa. But let's get the kernel notifications working first
as we also need to fix up the audio parts for the earlier comments from
Peter and Sebastian.
Regards,
Tony
next prev parent reply other threads:[~2020-05-06 14:43 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 [this message]
2020-05-06 23:05 ` Pavel Machek
2020-05-07 14:07 ` Tony Lindgren
2020-05-08 10:02 ` ofono for d4: less hcked and more working version was " Pavel Machek
2020-05-09 13:57 ` 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=20200506144338.GT37466@atomide.com \
--to=tony@atomide.com \
--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=pavel@ucw.cz \
--cc=sre@kernel.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 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).