From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Other types of usb audio devices.
Date: Sat, 05 Jul 2003 12:23:30 +0100 [thread overview]
Message-ID: <3F06B532.5040207@superbug.demon.co.uk> (raw)
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 will probably be writing a new usb-audio.c file and probably call it
usb-wireless.c in order to handle all the bluetooth specific stuff.
Cheers
James
-------------------------------------------------------
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
next reply other threads:[~2003-07-05 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-05 11:23 James Courtier-Dutton [this message]
2003-07-05 13:58 ` Other types of usb audio devices Jaroslav Kysela
2003-07-05 14:27 ` James Courtier-Dutton
2003-07-07 10:39 ` Jaroslav Kysela
2003-07-07 11:15 ` Takashi Iwai
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=3F06B532.5040207@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-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.