All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Comments about the Logitech/HP stereo headphones
Date: Sun, 24 Apr 2005 08:04:55 -0600	[thread overview]
Message-ID: <426BA787.9060202@xmission.com> (raw)
In-Reply-To: <1114345112.10706.64.camel@pegasus>

Marcel

This all sounds very good and I feel like a dope for getting rid of my 
bluetake headset when I had only ordered, but not received, a 
replacement. I'm still waiting for my itech. :(

> So what I have done so far is that I extended the pcm_a2dp ALSA plugin
> in the utils CVS repository with the ability to cache the connection.

btsco now fires up the connection on demand and drops it immediately 
after the close. we are going to need caching too. I noticed my phone 
holds the connection open for about 3-5 seconds after it uses it.

> To fully support all A2DP headphones (including Logitech/HP) this plugin
> needs a AVDTP implementation. I have a hacked one on my development
> system and it works fine with the GCT headphones. The code is a little
> bit messy, but in general it works. It is fully event driven and so it
> deprecates the idea of the AVDTP library. It is a lot easier to do it
> directly inside the plugin. I need to cleanup the code and submit it to
> the CVS when there is a little bit more time.

I am excited to see this!

> all about the timing. The perfect thing now would be if we can tell ALSA
> to time everything for us. Problem is that I am not an audio expert and
> also not an ALSA expert. Maybe the SBC encoder should return/store the
> time the SBC frame is encoded for.

I think alsa should help us out here. If I have to learn more about the 
alsa api to help, I will do it.

Doing a2dp inside an alsa plugin is clearly the right way. Thomas was 
saying that requiring alsa-lib was not good for embedded. I'm working on 
an xscale board now and I do have to use a precious 700k of limited 
flash for alsa-lib, but the alternative is to write something into the 
kernel that would never be accepted by Linus.

Brad


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2005-04-24 14:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24 12:18 [Bluez-devel] Comments about the Logitech/HP stereo headphones Marcel Holtmann
2005-04-24 13:47 ` Guylhem Aznar
2005-04-24 14:28   ` Brad Midgley
2005-04-24 15:23     ` Marcel Holtmann
2005-04-24 15:16   ` Marcel Holtmann
2005-04-24 17:11     ` Guylhem Aznar
2005-04-24 18:09       ` Marcel Holtmann
2005-04-24 20:28       ` Brad Midgley
2005-04-24 16:19   ` Henryk Plötz
2005-04-24 16:48     ` Guylhem Aznar
2005-04-24 18:15       ` Marcel Holtmann
2005-04-24 18:12     ` Marcel Holtmann
2005-04-24 14:04 ` Brad Midgley [this message]
2005-04-24 14:34   ` Brad Midgley
2005-04-24 15:30   ` Marcel Holtmann
2005-04-25 17:39     ` Brad Midgley
  -- strict thread matches above, loose matches on Subject: below --
2005-04-24 15:16 Mayank Batra
2005-04-24 15:35 ` Marcel Holtmann
2005-04-26 12:46 Mayank Batra
2005-04-26 13:28 ` Marcel Holtmann
2005-04-28 12:10 Mayank Batra
2005-04-29  9:51 ` 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=426BA787.9060202@xmission.com \
    --to=bmidgley@xmission.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.