linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Connecting to a headset
Date: Sat, 11 Mar 2006 08:29:21 -0700	[thread overview]
Message-ID: <4412ECD1.4070007@xmission.com> (raw)
In-Reply-To: <fe0a97c20603090959r28afb671n79c0a432f4f6c0c2@mail.gmail.com>

Sowmya

> Iam a novice in linux and bluetooth....
> I have a very specific question regarding the headset and audio profile....
> Why is it that ALSA and Bluetooth can connect to a headset???
> I mean what ALSA can do which others can't do?
> 
> Can't it be on a lil lower kernel of 2.4.20 or something... or with
> downloaded ALSA libraries ... why only with an "integrated"  kernel with
> ALSA???? ( i,e a newer kernel.... )

Get the bluez cvs project and have a look at utils/test/scotest.c

You can write your app to do all the audio transfers itself and you
won't have to patch or upgrade the kernel.

Of course you're mostly on your own :) so good luck.

Brad


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-03-11 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-09 17:59 [Bluez-devel] Connecting to a headset Sowmya Gattupalli
2006-03-11 15:29 ` Brad Midgley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-13 10:15 Sowmya Gattupalli

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=4412ECD1.4070007@xmission.com \
    --to=bmidgley@xmission.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).