public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: deker <deker@slackdot.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Continued SCO audio issues...
Date: Sun, 07 Dec 2008 11:08:24 -0500	[thread overview]
Message-ID: <493BF4F8.4050609@slackdot.org> (raw)
In-Reply-To: <1228616055.28839.51.camel@violet.holtmann.net>

I'd be happy to give it a shot. Could you direct me to some docs as to 
how do that?

Thanks,

-d

Marcel Holtmann wrote:
> Hi Rob,
>
>   
>>> you never thought that routing the SCO packets via the chips internal
>>> PCM (instead of HCI) might be a problem if you wanna use ALSA?
>>>       
>>  I'm not certain I'm understanding you correctly. Are you saying that 
>> audio SHOULD be routed through the HCI? We are currently routing the 
>> audio via the PCM via the "SCORouting=PCM"...I may have forgotten to put 
>> that into the message, but it is indeed in the config file.
>>     
>
> then why are you messing with the ALSA plugin? Just use D-Bus to
> establish the connection.
>
> Regards
>
> Marcel
>
>
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>   


------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-12-07 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-05 23:37 [Bluez-devel] Continued SCO audio issues Rob "Deker" Dekelbaum
2008-12-06 21:16 ` Marcel Holtmann
2008-12-07  1:34   ` Rob "Deker" Dekelbaum
2008-12-07  2:14     ` Marcel Holtmann
2008-12-07 16:08       ` deker [this message]
2008-12-08 18:36         ` Rob "Deker" Dekelbaum
2008-12-08 19:56           ` Marcel Holtmann
2008-12-08 20:46             ` Rob "Deker" Dekelbaum
2008-12-12  1:49               ` 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=493BF4F8.4050609@slackdot.org \
    --to=deker@slackdot.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