public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP btsco support
Date: Sun, 27 Mar 2005 17:47:19 +0200	[thread overview]
Message-ID: <1111938439.9195.232.camel@pegasus> (raw)
In-Reply-To: <20050327154013.GC26485@externe.net>

Hi Guylhem,

> > the goal will be to go for a direct ALSA plugin, but my Aiptek is not
> > really conforming to the A2DP specification. This means that I don't
> > have any headphone to really work with and thus I can't solve this
> > issue.
> 
> I recommand keeping standalone sbc encoder and a2play, at least for
> those who want to use such headphones with linux PDAs (I do !)

we will see, but the goal should be still an integration into the sound
system. And this is ALSA at the moment.

> BTW I did report somes bug and proposed fixes when I was compiling
> with gcc 2.95 for ARM. Did they make it in?

I haven't seen any. Resend them.

Regards

Marcel




-------------------------------------------------------
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

  reply	other threads:[~2005-03-27 15:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-26 18:56 [Bluez-devel] A2DP btsco support Manuel Harnisch
2005-03-27  3:39 ` Marcel Holtmann
2005-03-27  4:34   ` Manuel Harnisch
2005-03-27 15:40   ` Guylhem Aznar
2005-03-27 15:47     ` Marcel Holtmann [this message]
2005-03-27 16:28     ` Brad Midgley

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=1111938439.9195.232.camel@pegasus \
    --to=marcel@holtmann.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox