From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO connection timed out issue
Date: Wed, 17 Oct 2007 19:49:57 -0600 [thread overview]
Message-ID: <d89ddf300710171849p3cd9da02kb7488387e095b534@mail.gmail.com> (raw)
In-Reply-To: <BAY117-W36EE4B29F3D4550A7C9847C09E0@phx.gbl>
semiyd
> Later i found something.I checked out the website "
> http://wiki.bluez.org/wiki/Audio" and found that the
> /bluez-utils-3.20/audio/gateway.c implements the
> org.bluez.audio.gateway interface.But when i looked into the
> gateway.c, there's nothing in there.And /bluez-
> utils-3.20/audio-api.txt also says that the audio gateway service is
> not yet implemented in the current bluez. Is that true? If it is so
> ,does this means that there's no way we can enable the SCO/A2DP audio
> connection to the headset right now?
for now the files there are named backward. gateway.c would contain
code for talking to a gateway device, not for being a gateway. You can
experiment now with sco/a2dp to a headset just fine.
> I'm really confused cause i read about an
> article:http://bluetooth-alsa.sourceforge.net/build.html ,which
> teaches the reader how to enable bluez audio without mentioning
> anything about the org.bluez.audio.gateway implementation.
the bluetooth-alsa stuff is all old. that's why there's a banner
across the top of the page directing people to the new stuff.
brad
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-18 1:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 1:36 [Bluez-devel] SCO connection timed out issue \x11
2007-10-18 1:49 ` Brad Midgley [this message]
2007-10-18 2:46 ` \x11
2007-10-18 3:14 ` \x11
2007-10-18 13:24 ` Brad Midgley
2007-10-18 13:46 ` \x11
2007-10-18 17:26 ` Brad Midgley
2007-10-19 2:24 ` dong yan
2007-10-18 10:31 ` Fabien Chevalier
2007-10-18 12:13 ` \x11
2007-10-18 12:33 ` \x11
2007-10-18 13:08 ` Fabien Chevalier
2007-10-19 3:16 ` \x11
2007-10-19 5:55 ` \x11
2007-10-20 8:05 ` \x11
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=d89ddf300710171849p3cd9da02kb7488387e095b534@mail.gmail.com \
--to=bmidgley@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox