From: soraberri <421246@posta.unizar.es>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: btsco and alsa driver interaction
Date: Wed, 09 Mar 2005 10:17:15 +0100 [thread overview]
Message-ID: <d0meub$s51$1@sea.gmane.org> (raw)
In-Reply-To: <422E59A9.2040408@xmission.com>
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!)
best regards
Luis_Peiro
Brad Midgley wrote:
> Luis
>
> It's good to see your interest... I think you have the right ideas on
> how things work.
>
>> I also imagine that when we poll data from the hwdep interface, we are
>> not polling SCO data type (which I assume it is being drived
>> automatically); instead, we are polling for volume-control data type
>> which is enigmatically (for me) generated at the core of the driver.
>> Is it right?
>
>
> if the volume change is initiated through a generic mixer, then yes.
> Think of a mixer application running on your computer. Run any
> alsa-aware mixer and it will let you choose the alsa mixer device to be
> the headset.
>
>> The question is, 'when does the following condition evaluate TRUE ?
>>
>> if (!snd_hwdep_poll_descriptors_revents(handle, &pfds[nfds - 1], 1,
>> revents) && revents & POLLIN) {
>
>
> It evaluates true when there are volume-change events to be examined
> that were initiated through a soft mixer.
>
> 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
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-03-09 9:17 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 ` soraberri [this message]
2005-03-10 8:26 ` [Bluez-devel] " suche.org
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='d0meub$s51$1@sea.gmane.org' \
--to=421246@posta.unizar.es \
--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.