From: "Pali Rohár" <pali.rohar@gmail.com>
To: Denis Kenzior <denkenz@gmail.com>
Cc: ofono@ofono.org, linux-bluetooth@vger.kernel.org
Subject: Re: HSP/HFP ofono bluetooth support for Linux desktop
Date: Thu, 13 Feb 2020 20:15:34 +0100 [thread overview]
Message-ID: <20200213191534.vz2mzxhkhr6i73r4@pali> (raw)
In-Reply-To: <77397684-1c15-854e-b88b-4adff6f73ada@gmail.com>
On Thursday 13 February 2020 13:08:56 Denis Kenzior wrote:
> > So, why should I even consider to use ofono at all? It does not support
> > none of above desktop feature, it does not support extended codecs, it
> > does not support HSP profile and also it does not support HFP profile
> > without physical modem (majority of desktops and laptops).
>
> Your initial proposal wanted to use oFono as some sort of helper for your
> daemon, and that is just not going to be accepted by oFono upstream. I gave
> you a few alternatives, including how to extend oFono to do what you want.
> If you want to roll your own, go for it.
You have said that ofono is not going to accept usage of hsphfpd for
telephony and also you said that ofono does not have plans to implement
needed HSP and HFP features for desktop users.
So conclusion from all these facts is that ofono is fully unusable for
desktop / latop usage of bluetooth HSP and HFP profiles.
--
Pali Rohár
pali.rohar@gmail.com
prev parent reply other threads:[~2020-02-13 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200107192311.efit6zftt27encdc@pali>
2020-01-08 11:40 ` HSP/HFP ofono bluetooth support for Linux desktop Pali Rohár
[not found] ` <721332d3-336a-b9d2-f8cd-72da785fb9dc@gmail.com>
2020-01-08 21:25 ` Pali Rohár
2020-02-09 13:15 ` Pali Rohár
2020-02-12 21:29 ` Denis Kenzior
2020-02-13 17:46 ` Pali Rohár
2020-02-13 18:14 ` Denis Kenzior
2020-02-13 18:32 ` Pali Rohár
2020-02-13 19:08 ` Denis Kenzior
2020-02-13 19:15 ` Pali Rohár [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=20200213191534.vz2mzxhkhr6i73r4@pali \
--to=pali.rohar@gmail.com \
--cc=denkenz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--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 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).