On Sat, 5 Jul 2003, James Courtier-Dutton wrote:
> Hi,
>
> The current snd-usb-audio driver assumes that the audio device is
> attached to this computer, so it only talks to this endpoint.
> If I have an audio usb device with USB_CLASS = 0xe0, it will be a
> wireless device. I.E. A bluetooth headset.
> It uses isoc's just like the current snd-usb-audio driver but adds some
> extra requirements, in order to open a connection, one needs to also
> know the bd address of the destination device (Like a MAC address for
> ethernet) and keep tabs of connection number.
> The current bluetooth stack I am using is bluez, from the current 2.4.20
> kernel, and it uses network sockets for the audio. I would prefer to
> use alsa for sending and receiving audio to/from the headset, with all
> other control of the device going via the bluetooth stack.
> So the question is: -
> How do I get the bdaddr to alsa so that an application can use
> snd_pcm_open with the bluetooth headset, just as if it was a local audio
> card.
I think that there must be a way to determine new devices with the
bluetooth stack, so use the same mechanism as usb or pcmcia:
Register all found audio devices and create appropriate new cards in the
ALSA driver. The application does not know, if it communicates with usb,
bluetooth, PCI or ISA devices so passing some native information for the
transport layer is not our goal.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
