From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>, Tanu Kaskinen <tanuk@iki.fi>,
General PulseAudio Discussion
<pulseaudio-discuss@lists.freedesktop.org>,
ofono@ofono.org, devkit-devel@lists.freedesktop.org,
Bastien Nocera <hadess@hadess.net>, Georg Chini <georg@chini.tk>,
Russell Treleaven <rtreleaven@bunnykick.ca>,
Arun Raghavan <arun@arunraghavan.net>,
Marcel Holtmann <marcel@holtmann.org>,
Sebastian Reichel <sre@ring0.de>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [pulseaudio-discuss] Proposal for a new API and usage of Bluetooth HSP and HFP profiles on Linux
Date: Mon, 16 Dec 2019 00:11:04 +0200 [thread overview]
Message-ID: <CABBYNZKi7UUg7kASKadGr7sDJH0-tfuuZr9rd4Xu8ZUA9LqTMA@mail.gmail.com> (raw)
In-Reply-To: <20191205093200.x47npi5sxtcphr2o@pali>
Hi Pali,
On Thu, Dec 5, 2019 at 11:32 AM Pali Rohár <pali.rohar@gmail.com> wrote:
>
> On Monday 02 December 2019 19:45:12 Pali Rohár wrote:
> > On Monday 02 December 2019 19:01:11 Tanu Kaskinen wrote:
> > > I think hsphfpd should be part of bluetoothd, but if that's not
> > > possible, then that's not possible.
> >
> > I do not know if bluez developers are interested in having this code as
> > part of bluez project, specially when in bluez4 HFP profile was there
> > and in bluez5 was HFP code completely removed.
>
> Hello, could someone from bluez developers comment this Tanu's point?
I would have to say no, we are definitely not interested in yet
another daemon for AT parsing, we actually have too many of these
around, either in a form of Modem Manager, oFono, etc. That said one
simpler way to resolve all of this is to maintain a plugin to
bluetoothd that way HSP/HFP becomes native again, that can either be
maintained in the tree or out of the tree.
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2019-12-15 22:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 18:57 Proposal for a new API and usage of Bluetooth HSP and HFP profiles on Linux Pali Rohár
2019-12-02 17:01 ` [pulseaudio-discuss] " Tanu Kaskinen
2019-12-02 18:45 ` Pali Rohár
2019-12-04 15:15 ` Arun Raghavan
2019-12-04 17:05 ` Pali Rohár
2019-12-05 9:32 ` Pali Rohár
2019-12-15 22:11 ` Luiz Augusto von Dentz [this message]
2019-12-16 9:15 ` Pali Rohár
2019-12-17 23:47 ` Luiz Augusto von Dentz
2019-12-18 8:30 ` Pali Rohár
2019-12-18 17:00 ` Denis Kenzior
2019-12-18 17:28 ` Pali Rohár
2019-12-18 17:36 ` Pali Rohár
2019-12-18 20:53 ` Denis Kenzior
2019-12-18 21:33 ` Pali Rohár
2019-12-19 1:03 ` Denis Kenzior
2019-12-19 9:51 ` Pali Rohár
2019-12-19 14:53 ` Denis Kenzior
2019-12-19 15:33 ` Pali Rohár
2019-12-20 21:19 ` Denis Kenzior
2019-12-20 22:46 ` Pali Rohár
2020-01-04 10:51 ` Pali Rohár
2020-01-07 17:35 ` Denis Kenzior
2020-01-07 19:01 ` Pali Rohár
2019-12-02 19:49 ` Sebastian Reichel
2019-12-07 20:09 ` Pali Rohár
2019-12-09 9:43 ` George Kiagiadakis
2019-12-09 11:07 ` Pali Rohár
2020-03-15 14:17 ` Pali Rohár
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=CABBYNZKi7UUg7kASKadGr7sDJH0-tfuuZr9rd4Xu8ZUA9LqTMA@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=arun@arunraghavan.net \
--cc=devkit-devel@lists.freedesktop.org \
--cc=georg@chini.tk \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=ofono@ofono.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=pulseaudio-discuss@lists.freedesktop.org \
--cc=rtreleaven@bunnykick.ca \
--cc=sre@ring0.de \
--cc=tanuk@iki.fi \
/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).