From: Max Krasnyansky <maxk@qualcomm.com>
To: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>,
James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: bluez Dev <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Bluetooth headset with Bluetooth usb dongle status.
Date: Mon, 21 Jul 2003 16:53:41 -0700 [thread overview]
Message-ID: <5.1.0.14.2.20030721165032.09709700@unixmail.qualcomm.com> (raw)
In-Reply-To: <1058533496.25379.237.camel@pegasus>
At 06:04 AM 7/18/2003, Marcel Holtmann wrote:
>> So, there is going to be quite a lot of manipulation of the sound
>> samples as they pass from alsa to the bluetooth device.
>> The questions I am still trying to decide are: -
>> 1) When should the conversion from alsa ring buffer to packets take
>> place. So far the only workable solution I have come up with is that the
>> "hci_usb_tx_complete" makes a callback all the way to the sco layer, and
>> the sco layer grabs 24 bytes form the alsa ring buffer, adds it's header
>> and returns from the callback.
>> 2) interface to alsa. I think this should happen just above the SCO
>> layer, but also ensuring that the SCO layer has enought api links with
>> the hci-usb.c layer to be able to service all the alsa-driver api
>> requirements.
>> 3) Once that all works, modify the other low level hardware drivers to
>> work with it. e.g. bluecard_cs.c etc.
>
>The native integration of Bluetooth audio within Linux is one of the
>most wanted things. But we can't use ALSA for the 2.4 kernel, because it
>is not a part of the kernel. For the 2.6 this is no problem, but I also
>want to have support for OSS, because there will some people (like me)
>which still uses OSS.
Those people will have to upgrade :). New stuff like this audio support
should be developed in 2.6.
>The integration of audio is not part of the Bluetooth drivers, because
>every Bluetooth HCI driver is only a transport driver which have to
>transport the HCI command, event, ACL and SCO data between the hardware
>and the HCI core layer. The SCO data would send from the HCI core
>through the hdev->send() callback and the driver can send the SCO data
>it gets from the hardware back with hci_recv_frame(). This means that
>all needed modifications for ALSA and OSS integration have to done in
>the HCI core or the SCO layer. And all other HCI drivers will still work
>with SCO like they do now.
150% agree.
Max
next prev parent reply other threads:[~2003-07-21 23:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19a5DI-0002jL-00@sc8-sf-list2.sourceforge.net>
[not found] ` <3F1752C5.5020701@dsto.defence.gov.au>
2003-07-18 12:15 ` [Bluez-devel] Re: Bluetooth headset with Bluetooth usb dongle status James Courtier-Dutton
2003-07-18 13:04 ` Marcel Holtmann
2003-07-18 13:58 ` James Courtier-Dutton
2003-07-20 14:33 ` [Bluez-devel] " Jonathan Paisley
2003-07-22 0:23 ` Max Krasnyansky
2003-07-22 1:10 ` James Courtier-Dutton
2003-07-22 17:46 ` Max Krasnyansky
2003-07-22 17:56 ` jp-www
2003-07-22 13:35 ` jp-www
2003-07-22 0:18 ` [Bluez-devel] " Max Krasnyansky
2003-07-21 23:53 ` Max Krasnyansky [this message]
2003-07-21 23:49 ` Max Krasnyansky
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=5.1.0.14.2.20030721165032.09709700@unixmail.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=James@superbug.demon.co.uk \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.de \
/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