From: "suche.org" <admin@suche.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: btsco and alsa driver interaction
Date: Thu, 10 Mar 2005 09:26:04 +0100 [thread overview]
Message-ID: <4230049C.5040108@suche.org> (raw)
In-Reply-To: <d0meub$s51$1@sea.gmane.org>
soraberri wrote:
> Hi
>
> many thanks Brad! I didn't think in the mixer before... now I think I
> got it :O
> (by the way, I haven't forgotten about adding support in the audio
> gateway as you suggested one day, in order to let the headset intiate
> an audio connection. This would require the proper SDP record in the
> database with the proper RFCOMM channel number, and a RFCOMM socket
> listening in the application. I made some copy-paste for the first
> thing in sdptool code, but I haven't find the rigth place for the
> listening socket yet... I have much left to study I guess!)
Hi,
in btso2 the listen socket can be easyly integretet.
You aktivate hin in the main while loop. It should be no problem
since the programm is desinged to handle multiple connections.
But currently only supprt one since i do not know how to add an second
headset, and have none.
Cu Thomas
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-10 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 19:11 [Bluez-devel] btsco and alsa driver interaction soraberri
2005-03-09 2:04 ` Brad Midgley
2005-03-09 9:17 ` [Bluez-devel] " soraberri
2005-03-10 8:26 ` suche.org [this message]
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=4230049C.5040108@suche.org \
--to=admin@suche.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 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.