public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <mzuny@0pointer.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Takashi Iwai" <tiwai@suse.de>,
	"BlueZ development" <bluez-devel@lists.sourceforge.net>,
	"Marc-André Lureau" <marcandre.lureau@gmail.com>,
	hal@lists.freedesktop.org
Subject: Re: [patch] spec: Update alsa namespace to include virtual device
Date: Mon, 27 Aug 2007 16:47:20 +0200	[thread overview]
Message-ID: <20070827144720.GA6448@tango.0pointer.de> (raw)
In-Reply-To: <1188225287.15402.324.camel@violet>

On Mon, 27.08.07 16:34, Marcel Holtmann (marcel@holtmann.org) wrote:

> At some point in the future we gonna integrate Bluetooth much deeper
> into HAL as currently done. Right now we only see the kernel side of
> Bluetooth represented in HAL. This needs some restructure to make it
> work smoothly and needs some extra time, but we are getting there.

If the bt devices are exported in sysfs in the kernel already it is no
longer hal that synthesizes them. Which makes these things much
cleaner I would say.

Synthesizing virtual devices at the HAL level doesn't look like such a
good idea to me, smells kludgy. But doing this on a lower level might
make sense.

But anyway, it's your call, you're the BT guru.

> > OTOH i must say that this would make it very easy for me to add bt
> > support to PA, so I am not inherently opposed. However, I don't really
> > think going through ALSA for bt audio makes too much sense for PA. It
> > is probably better to integrate bt and PA directly, without having
> > this unnecessary abstraction in between.
> 
> I am currently working on the GStreamer sink. If you provide an exported
> plugin API for PulseAudio, you can have that easily. Otherwise it might
> not happen.

A stable plugin API is not going to happen anytime soon, sorry. Also,
it is not really practical to develop plugins out-of-tree. I
acknowledge the demand for it, but the plugin API is just too quickly
moving.

Hmm, I'd love to add proper BT support to PA myself, but unfortunately
I lack the hardware for it. It would be much easier to keep it up to
date for me then.

Hmm, I will try to get myself a bt headset.

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

  reply	other threads:[~2007-08-27 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 16:22 [patch] spec: Update alsa namespace to include virtual device Marc-André Lureau
2007-08-23 17:06 ` [Bluez-devel] " Matthias Kretz
2007-08-23 18:20   ` Marcel Holtmann
2007-08-23 18:56     ` Matthias Kretz
2007-08-23 19:27       ` Marcel Holtmann
2007-08-27 14:11 ` Lennart Poettering
2007-08-27 14:34   ` Marcel Holtmann
2007-08-27 14:47     ` Lennart Poettering [this message]
2007-08-27 15:09       ` Marcel Holtmann
2007-08-27 15:15         ` Lennart Poettering
2007-08-27 15:24           ` Marcel Holtmann

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=20070827144720.GA6448@tango.0pointer.de \
    --to=mzuny@0pointer.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=hal@lists.freedesktop.org \
    --cc=marcandre.lureau@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=tiwai@suse.de \
    /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